[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105467#comment-17105467
]
Timothy A. Bish commented on QPIDJMS-504:
-----------------------------------------
The client is stuck waiting for the remote to respond to an attach request.
For remote peers that misbehave you can configure the client request timeout to
some value that you are willing to accept as the remote not being response and
it will fail the create process. See the client documentation for [URI
configuration
option|http://qpid.apache.org/releases/qpid-jms-0.51.0/docs/index.html#jms-configuration-options]
'jms.requestTimeout'
> Connections hangs when trying to connect to a RabbitMQ persistent queue
> -----------------------------------------------------------------------
>
> Key: QPIDJMS-504
> URL: https://issues.apache.org/jira/browse/QPIDJMS-504
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.51.0
> Reporter: Stephan Siano
> Priority: Major
>
> When I try to connect to a persistent queue on a RabbitMQ broker with
> activated AMQP 1.0 plugin, the connection hangs for an infinite time (or at
> least for a very long time).
> There is no error, the connection just hangs. The tack trace in this
> situation for a producer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageProducer.<init>(JmsProducerId, JmsSession, JmsDestination) line: 73
> JmsQueueSession(JmsSession).createProducer(Destination) line: 664
> JmsQueueSession.createProducer(Destination) line: 97
> {noformat}
> The stack trace for a consumer is:
> {noformat}
> BalancedProviderFuture(Object).wait() line: 502
> BalancedProviderFuture.sync() line: 136
> JmsConnection.createResource(JmsResource, ProviderSynchronization) line: 693
> JmsMessageConsumer.<init>(JmsConsumerId, JmsSession, JmsDestination, String,
> String, boolean) line: 125
> JmsMessageConsumer.<init>(JmsConsumerId, JmsSession, JmsDestination, String,
> boolean) line: 82
> JmsQueueSession(JmsSession).createConsumer(Destination, String, boolean)
> line: 478
> JmsQueueSession.createConsumer(Destination, String, boolean) line: 70
> JmsQueueSession(JmsSession).createConsumer(Destination, String) line: 466
> JmsQueueSession.createConsumer(Destination, String) line: 59
> JmsQueueSession(JmsSession).createConsumer(Destination) line: 458
> JmsQueueSession.createConsumer(Destination) line: 48
> {noformat}
> I am aware that the AMQP 1.0 plugin in RabbitMQ is not very mature, but I
> don't think that the client threads should be blocked forever even when
> trying to communicate with misbehaving servers.
> The issue will not happen with transient queues on RabbitMQ (here everything
> works as expected).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
