Cannot conect while using ActiveMQ with Qpid JMS client

Hi, I'm trying to make work following components to work together: - Apache Active MQ 5.13.3 - Qpid JMS Client 0.10.0 (tested on 0.9.0 as well) The goal is to connect to MS Azure IoT Hub using the Qpid JMS client while running ActiveMQ for

Re: Cannot conect while using ActiveMQ with Qpid JMS client

One thing I found out is that activemq-amqp artifact has proton-j compile dependency: +- org.apache.activemq:activemq-amqp:jar:5.13.3:compile | \- org.apache.qpid:proton-j:jar:0.12.1:compile But that one was overridden by direct dependency when I used it (and the issue had occurred even at that

Re: Cannot conect while using ActiveMQ with Qpid JMS client

URI given to the client JmsConnectionFactory: amqps://boxmessagehub.azure-devices.net:5671 And it should work fine with qpid JMS client (tested separately and seems to be OK) I pass the amqp.idleTimeout=12 property straight to the JmsConnectionFactory properties as I had an exception thrown

Re: Cannot conect while using ActiveMQ with Qpid JMS client

I've noticed the issue just when I finished the question... I tried to use proton-j 0.13.1 (as direct dependency) and 0.13.0 (transitive dependency of qpid-jms-client 0.10.0) But it still hangs on the same spot no matter what version of the library I'm using. I'm not saying the problem is not

Re: Cannot conect while using ActiveMQ with Qpid JMS client

I don't think the problem could be caused by old slf4j dependency. Even if I try the newest version, the problem remains the same. If it helps I can paste complete dependency tree. Last time I just left out stuff made by our company and posted only 3rd party libraries. Now a complete tree: ---

Re: Cannot conect while using ActiveMQ with Qpid JMS client

I found a stupid error which I had not noticed before: java.lang.NoClassDefFoundError: javax/security/sasl/SaslException It was thrown somewhere in the qpid part so it was hard to catch. But still stupid me for not seeing it earlier. But I'm afraid this is only one of a few problems I have in

Re: Cannot conect while using ActiveMQ with Qpid JMS client

So now I have finer logs - you can clearly see that the connection is closed right after it is opened. No idea why the MS server closes it. In the log there is first the connection attempt, then the Exception formed based on the remote close. Then the connection should be closed in my part because

Re: Cannot conect while using ActiveMQ with Qpid JMS client

It was really tied to the *amqp.idleTimeout* property! Now I changed my connector.uri to amqps://boxmessagehub.azure-devices.net:5671?amqp.idleTimeout=12 and messages are beeing dispatched. Initially I removed this parameter as I received some Exceptions that the ActiveMQ couldn't resolve

Re: Qpid JMS client JmsConnection.close() hangs

I'll try to find a way of preventing this problem from happening. (Though I'm not sure how to do that properly at the moment.) But how do you explain unlimited waiting for Close frame response as shown in my previous post? DraCzech wrote > 2016-11-24 16:41:45.202589 [19105288:0] -> Close

Re: Qpid JMS client JmsConnection.close() hangs

When going through logs I also found this piece of thread dump. Which shows that my cleaning thread is waiting for a lock held by ActiveMQ thread. A state which is definitely not desired, but I'm not sure if can be prevented completely... 2016-11-24 17:46:10.016523 "JMS Connector cleaner" daemon

Re: Qpid JMS client JmsConnection.close() hangs

So I tried to turn on logging on qpid and this is what I found so far. In case I shut down the messaging bundle, it sends *Close*, receives *Close*, everything goes fine. But In case the device loses network connection it sends *Close* and waits for response which never comes. I'm using

Qpid JMS client JmsConnection.close() hangs

Hi, I'm currently using ActiveMQ 5.14.1 embedded broker connected from several local queues to MS Azure IoT Hub using JmsConnectionFactory as foreignConnectionFactory in SimpleJmsQueueConnector. (Using dependency to qpid jms client 0.11.1) Each queue is connected to the server via its respective

Re: Qpid JMS client JmsConnection.close() hangs

Thanks! I'll try that as soon as 0.20.0 is released! This might also help with another issue I'm experiencing - The ThreadPoolExecutor in JmsConnection is producing non-daemon threads intentionally (I can see the comment, but still don't get the reason why to do it in your code.) Which means in