[
https://issues.apache.org/jira/browse/AMQ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Butts updated AMQ-6362:
---------------------------
Comment: was deleted
(was: Should this option work with failover transports? I've set it
programmatically via ActiveMQConnectionFactory and passed in a failover
connection URI
{code}
javax.jms.JMSException: Could not create Transport. Reason:
java.lang.IllegalArgumentException: Invalid connect parameters:
{connectResponseTimeout=5000}
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:36)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:333)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:346)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:304)
at
org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:244)
at
com.x.jms.ActiveMQDemandForwardingBridgeTest.buildSession(ActiveMQDemandForwardingBridgeTest.java:248)
at
com.x.jms.ActiveMQDemandForwardingBridgeTest.runTest(ActiveMQDemandForwardingBridgeTest.java:153)
at
com.x.jms.ActiveMQDemandForwardingBridgeTest.testRestartConsumerBroker(ActiveMQDemandForwardingBridgeTest.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Invalid connect parameters:
{connectResponseTimeout=5000}
at
org.apache.activemq.transport.failover.FailoverTransportFactory.createTransport(FailoverTransportFactory.java:65)
at
org.apache.activemq.transport.failover.FailoverTransportFactory.doConnect(FailoverTransportFactory.java:38)
at
org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:69)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:331)
... 18 more
{code})
> Add an option to time out connection attempts when blocked in
> ensureConnectionInfoSent
> --------------------------------------------------------------------------------------
>
> Key: AMQ-6362
> URL: https://issues.apache.org/jira/browse/AMQ-6362
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMS client
> Affects Versions: 5.13.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.14.0
>
>
> In some rare cases client side stack traces show client can be stuck in
> ensureConnectionInfoSent wanting forever for a response from the broker. We
> will add an optional timeout to allow this operation to fail (defaults off).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
