[jira] [Commented] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105598#comment-17105598
]
Stephan Siano commented on QPIDJMS-504:
---
Oh, thanks. This parameter helps a lot. Nevertheless, it would be good if there
was a way to find out why the persistent queues in RabbitMQ don't work with
qpid-jms.
> 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.(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.(JmsConsumerId, JmsSession, JmsDestination, String,
> String, boolean) line: 125
> JmsMessageConsumer.(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
[jira] [Updated] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
[
https://issues.apache.org/jira/browse/QPIDJMS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Siano updated QPIDJMS-504:
--
Description:
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.(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.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(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).
was:
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.(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.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(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.
> 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.(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
[jira] [Created] (QPIDJMS-504) Connections hangs when trying to connect to a RabbitMQ persistent queue
Stephan Siano created QPIDJMS-504:
-
Summary: 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
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.(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.(JmsConsumerId, JmsSession, JmsDestination, String,
String, boolean) line: 125
JmsMessageConsumer.(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.
--
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
[jira] [Created] (QPIDJMS-480) Connection hangs for ws transport with wss server
Stephan Siano created QPIDJMS-480: - Summary: Connection hangs for ws transport with wss server Key: QPIDJMS-480 URL: https://issues.apache.org/jira/browse/QPIDJMS-480 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.47.0, 0.46.0 Reporter: Stephan Siano If you try to connect to a qpid-jms client with the amqpws (without TLS) transport to an SSL enabled server supporting the websocket protocol, the connection will hang (instead of failing with an error). You can reproduce the issue if you change line 60 of NettyWsTransportTest to return new NettyEchoServer(options, true, needClientAuth, true); and execute testConnectToServerUsingCorrectPath(). The test is expected to fail, but it fails only because the test times out after 60 seconds, not because the connection fails. Without that test timeout, the connection will hang indefinitely. If I try something similar with a TCP transport (connecting with amqp to an amqps) server, this fails after 10 seconds, which looks like a timeout to me (and is something I would consider ok). -- 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
[jira] [Commented] (QPIDJMS-441) Using QPID JMS behind a proxy
[ https://issues.apache.org/jira/browse/QPIDJMS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940680#comment-16940680 ] Stephan Siano commented on QPIDJMS-441: --- I have had a look into this: The implementation does not look too difficult to me, most effort is likely writing the tests. My idea would be to add a PROXY_HANDLER to the JmsConnectionExtensions enum, a setter for a ProxyHandler to the JmsConnectionFactory class, and another attribute (with getter and setter) to the TransportOptions (similar to the SSLContext). In the AMQPProvider class you could set the transport option if the JMS connection extension is set on the connectionInfo, and in the NettyTcpTransport one could finally set this proxy handler to the pipeline of the channel. Before I implement this for serious and invest time in testing this: Would you be interested in a contribution for this feature? How do you think should the tests for this look like, in particular, which additional test dependencies could I include in order to set up a test proxy? > Using QPID JMS behind a proxy > - > > Key: QPIDJMS-441 > URL: https://issues.apache.org/jira/browse/QPIDJMS-441 > Project: Qpid JMS > Issue Type: Wish > Components: qpid-jms-client >Affects Versions: 0.40.0 >Reporter: morten >Priority: Blocker > > I actually did not find a possibility to use the jms qpid client behind a > proxy. I guess there will be a lot of people who needs to run the library > behind a proxy. It would be nice to have the possibility to set a proxy > somehow. -- 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
