You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Timothy Bish <ta...@gmail.com> on 2016/12/01 16:35:15 UTC
Re: Qpid JMS client JmsConnection.close() hangs
Close timeout handling has been fixed up a fair bit with issue:
https://issues.apache.org/jira/browse/QPIDJMS-228
On 11/25/2016 11:04 AM, Robbie Gemmell wrote:
> "I also think I see an issue with the closeTimeout handling in that in
> one place it seems likely to be using the requestTimeout value
> instead. Need to investigate that further."
>
> Though in my attemps that didnt actually matter and the close
> completed fine if the network dropped and no response could be
> received (or was ever sent). As I say, needs more investigation.
>
> On 25 November 2016 at 15:49, DraCzech <dr...@gmail.com> wrote:
>> 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{error=null}
>>>
>>> on network lost vs.
>>>
>>> 2016-11-24 16:51:31.027968 [18734493:0] -> Close{error=null}
>>> 2016-11-24 16:51:31.977722 [18734493:0] <- Close{error=null}
>> Shouldn't some timeout throw an exception or so?
>>
>>
>>
>> --
>> View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7654872.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Robbie Gemmell <ro...@gmail.com>.
I've made some further changes to resolve an issue that might have
been something you hit in your scenario, where if you have the JMS 1.1
and JMS2 APIs both on the classpath it could fail during send, so I've
tweaked the client to tolerate that situation. Regarding the
thread/heap usage, thats likely related to something we are currently
looking into, but yes creating lots of connections would be needed for
it to come into play.
On 13 December 2016 at 16:19, Milano Nicolum <dr...@gmail.com> wrote:
> Unfortunately the latest update is not working for me either. Though it
> seems that connection is established to the IoT hub, the messages cannot be
> delivered. If I look at the AMQPS frames, I can see only Begin and Empty
> frames being exchanged.
> Also AmqpProvider and QpidJMS Connection Executor threads are somehow
> created in such extent that my JVM ran out of heap and my CPU is
> overloaded. Connection restarting policy might be responsible for this,
> because it is checking messages waiting for acknowledgement and tries to
> reconnect if any are detected.
>
> I decided I'll try different approach and discard ActiveMQ bridges entirely
> and try to pass all messages via single JmsConnection wrapped by my code.
> That way the whole process will be more likely under my control than under
> ActiveMQ's control. And while it surely requires some additional coding, I
> hope the result is worth it.
>
>
> 2016-12-13 15:15 GMT+01:00 Robbie Gemmell <ro...@gmail.com>:
>
>> I've made some changes to handle sending foreign messages from JMS 1.1
>> providers and published a new snapshot, you should be able to give
>> that a try now.
>>
>> Robbie
>>
>> On 13 December 2016 at 10:47, Robbie Gemmell <ro...@gmail.com>
>> wrote:
>> > Yes, that appears to be the client trying to call setJMSDeliveryTime
>> > on the Message, only to find the Message object impl doesnt support
>> > that due to being from a JMS 1.1 impl. Will need to have a think about
>> > how best to handle that. As a workaround currently you'd need to
>> > either modify the client not to make that call, or the ActiveMQ bridge
>> > to wrap the ActiveMQ Message and no-op the JMS 2 method before its
>> > passed to the client.
>> >
>> > To your previous question, there isnt a fixed date for the release, we
>> > will do it when we think its ready. If only because I'll be taking
>> > heading on vacation soon, some point in January is my current
>> > thinking.
>> >
>> > Robbie
>> >
>> > On 13 December 2016 at 08:18, Milano Nicolum <dr...@gmail.com> wrote:
>> >> Seems to me that Qpid JMS client is not compatible with my setup. I
>> tried
>> >> to use latest snapshot as dependency, but at the moment I'm getting:
>> >>
>> >> 2016-12-13 07:59:11,815 | ERROR | Error in thread 'ActiveMQ Session
>> Task-1'
>> >> | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ Session
>> Task-1
>> >> java.lang.AbstractMethodError:
>> >> org.apache.activemq.command.ActiveMQBytesMessage.setJMSDeliveryTime(J)V
>> >> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:772)
>> >> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:742)
>> >> at
>> >> org.apache.qpid.jms.JmsMessageProducer.sendMessage(
>> JmsMessageProducer.java:240)
>> >> at
>> >> org.apache.qpid.jms.JmsMessageProducer.send(
>> JmsMessageProducer.java:188)
>> >> at
>> >> org.apache.qpid.jms.JmsMessageProducer.send(
>> JmsMessageProducer.java:175)
>> >> at org.apache.qpid.jms.JmsQueueSender.send(JmsQueueSender.java:50)
>> >> at
>> >> org.apache.activemq.network.jms.QueueBridge.sendMessage(
>> QueueBridge.java:83)
>> >> at
>> >> org.apache.activemq.network.jms.DestinationBridge.
>> onMessage(DestinationBridge.java:135)
>> >> at
>> >> org.apache.activemq.ActiveMQMessageConsumer.dispatch(
>> ActiveMQMessageConsumer.java:1401)
>> >> at
>> >> org.apache.activemq.ActiveMQSessionExecutor.dispatch(
>> ActiveMQSessionExecutor.java:131)
>> >> at
>> >> org.apache.activemq.ActiveMQSessionExecutor.iterate(
>> ActiveMQSessionExecutor.java:202)
>> >> at
>> >> org.apache.activemq.thread.PooledTaskRunner.runTask(
>> PooledTaskRunner.java:133)
>> >> at
>> >> org.apache.activemq.thread.PooledTaskRunner$1.run(
>> PooledTaskRunner.java:48)
>> >> at
>> >> java.util.concurrent.ThreadPoolExecutor.runWorker(
>> ThreadPoolExecutor.java:1145)
>> >> at
>> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:615)
>> >> at java.lang.Thread.run(Thread.java:745)
>> >>
>> >>
>> >> So every time a message is to be sent, it fails on this error. I guess
>> it
>> >> is some kind of incompatibility between JMS 1.1 (used by ActiveMQ) and
>> JMS
>> >> 2.0 (used in latest Qpid JMS client). But it might as well be anything
>> else.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Milano Nicolum <dr...@gmail.com>.
Unfortunately the latest update is not working for me either. Though it
seems that connection is established to the IoT hub, the messages cannot be
delivered. If I look at the AMQPS frames, I can see only Begin and Empty
frames being exchanged.
Also AmqpProvider and QpidJMS Connection Executor threads are somehow
created in such extent that my JVM ran out of heap and my CPU is
overloaded. Connection restarting policy might be responsible for this,
because it is checking messages waiting for acknowledgement and tries to
reconnect if any are detected.
I decided I'll try different approach and discard ActiveMQ bridges entirely
and try to pass all messages via single JmsConnection wrapped by my code.
That way the whole process will be more likely under my control than under
ActiveMQ's control. And while it surely requires some additional coding, I
hope the result is worth it.
2016-12-13 15:15 GMT+01:00 Robbie Gemmell <ro...@gmail.com>:
> I've made some changes to handle sending foreign messages from JMS 1.1
> providers and published a new snapshot, you should be able to give
> that a try now.
>
> Robbie
>
> On 13 December 2016 at 10:47, Robbie Gemmell <ro...@gmail.com>
> wrote:
> > Yes, that appears to be the client trying to call setJMSDeliveryTime
> > on the Message, only to find the Message object impl doesnt support
> > that due to being from a JMS 1.1 impl. Will need to have a think about
> > how best to handle that. As a workaround currently you'd need to
> > either modify the client not to make that call, or the ActiveMQ bridge
> > to wrap the ActiveMQ Message and no-op the JMS 2 method before its
> > passed to the client.
> >
> > To your previous question, there isnt a fixed date for the release, we
> > will do it when we think its ready. If only because I'll be taking
> > heading on vacation soon, some point in January is my current
> > thinking.
> >
> > Robbie
> >
> > On 13 December 2016 at 08:18, Milano Nicolum <dr...@gmail.com> wrote:
> >> Seems to me that Qpid JMS client is not compatible with my setup. I
> tried
> >> to use latest snapshot as dependency, but at the moment I'm getting:
> >>
> >> 2016-12-13 07:59:11,815 | ERROR | Error in thread 'ActiveMQ Session
> Task-1'
> >> | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ Session
> Task-1
> >> java.lang.AbstractMethodError:
> >> org.apache.activemq.command.ActiveMQBytesMessage.setJMSDeliveryTime(J)V
> >> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:772)
> >> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:742)
> >> at
> >> org.apache.qpid.jms.JmsMessageProducer.sendMessage(
> JmsMessageProducer.java:240)
> >> at
> >> org.apache.qpid.jms.JmsMessageProducer.send(
> JmsMessageProducer.java:188)
> >> at
> >> org.apache.qpid.jms.JmsMessageProducer.send(
> JmsMessageProducer.java:175)
> >> at org.apache.qpid.jms.JmsQueueSender.send(JmsQueueSender.java:50)
> >> at
> >> org.apache.activemq.network.jms.QueueBridge.sendMessage(
> QueueBridge.java:83)
> >> at
> >> org.apache.activemq.network.jms.DestinationBridge.
> onMessage(DestinationBridge.java:135)
> >> at
> >> org.apache.activemq.ActiveMQMessageConsumer.dispatch(
> ActiveMQMessageConsumer.java:1401)
> >> at
> >> org.apache.activemq.ActiveMQSessionExecutor.dispatch(
> ActiveMQSessionExecutor.java:131)
> >> at
> >> org.apache.activemq.ActiveMQSessionExecutor.iterate(
> ActiveMQSessionExecutor.java:202)
> >> at
> >> org.apache.activemq.thread.PooledTaskRunner.runTask(
> PooledTaskRunner.java:133)
> >> at
> >> org.apache.activemq.thread.PooledTaskRunner$1.run(
> PooledTaskRunner.java:48)
> >> at
> >> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1145)
> >> at
> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:615)
> >> at java.lang.Thread.run(Thread.java:745)
> >>
> >>
> >> So every time a message is to be sent, it fails on this error. I guess
> it
> >> is some kind of incompatibility between JMS 1.1 (used by ActiveMQ) and
> JMS
> >> 2.0 (used in latest Qpid JMS client). But it might as well be anything
> else.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Robbie Gemmell <ro...@gmail.com>.
I've made some changes to handle sending foreign messages from JMS 1.1
providers and published a new snapshot, you should be able to give
that a try now.
Robbie
On 13 December 2016 at 10:47, Robbie Gemmell <ro...@gmail.com> wrote:
> Yes, that appears to be the client trying to call setJMSDeliveryTime
> on the Message, only to find the Message object impl doesnt support
> that due to being from a JMS 1.1 impl. Will need to have a think about
> how best to handle that. As a workaround currently you'd need to
> either modify the client not to make that call, or the ActiveMQ bridge
> to wrap the ActiveMQ Message and no-op the JMS 2 method before its
> passed to the client.
>
> To your previous question, there isnt a fixed date for the release, we
> will do it when we think its ready. If only because I'll be taking
> heading on vacation soon, some point in January is my current
> thinking.
>
> Robbie
>
> On 13 December 2016 at 08:18, Milano Nicolum <dr...@gmail.com> wrote:
>> Seems to me that Qpid JMS client is not compatible with my setup. I tried
>> to use latest snapshot as dependency, but at the moment I'm getting:
>>
>> 2016-12-13 07:59:11,815 | ERROR | Error in thread 'ActiveMQ Session Task-1'
>> | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ Session Task-1
>> java.lang.AbstractMethodError:
>> org.apache.activemq.command.ActiveMQBytesMessage.setJMSDeliveryTime(J)V
>> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:772)
>> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:742)
>> at
>> org.apache.qpid.jms.JmsMessageProducer.sendMessage(JmsMessageProducer.java:240)
>> at
>> org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:188)
>> at
>> org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:175)
>> at org.apache.qpid.jms.JmsQueueSender.send(JmsQueueSender.java:50)
>> at
>> org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:83)
>> at
>> org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:135)
>> at
>> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1401)
>> at
>> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
>> at
>> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
>> at
>> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
>> at
>> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> So every time a message is to be sent, it fails on this error. I guess it
>> is some kind of incompatibility between JMS 1.1 (used by ActiveMQ) and JMS
>> 2.0 (used in latest Qpid JMS client). But it might as well be anything else.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Robbie Gemmell <ro...@gmail.com>.
Yes, that appears to be the client trying to call setJMSDeliveryTime
on the Message, only to find the Message object impl doesnt support
that due to being from a JMS 1.1 impl. Will need to have a think about
how best to handle that. As a workaround currently you'd need to
either modify the client not to make that call, or the ActiveMQ bridge
to wrap the ActiveMQ Message and no-op the JMS 2 method before its
passed to the client.
To your previous question, there isnt a fixed date for the release, we
will do it when we think its ready. If only because I'll be taking
heading on vacation soon, some point in January is my current
thinking.
Robbie
On 13 December 2016 at 08:18, Milano Nicolum <dr...@gmail.com> wrote:
> Seems to me that Qpid JMS client is not compatible with my setup. I tried
> to use latest snapshot as dependency, but at the moment I'm getting:
>
> 2016-12-13 07:59:11,815 | ERROR | Error in thread 'ActiveMQ Session Task-1'
> | org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ Session Task-1
> java.lang.AbstractMethodError:
> org.apache.activemq.command.ActiveMQBytesMessage.setJMSDeliveryTime(J)V
> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:772)
> at org.apache.qpid.jms.JmsSession.send(JmsSession.java:742)
> at
> org.apache.qpid.jms.JmsMessageProducer.sendMessage(JmsMessageProducer.java:240)
> at
> org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:188)
> at
> org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:175)
> at org.apache.qpid.jms.JmsQueueSender.send(JmsQueueSender.java:50)
> at
> org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:83)
> at
> org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:135)
> at
> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1401)
> at
> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
> at
> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
> at
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
> at
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
>
> So every time a message is to be sent, it fails on this error. I guess it
> is some kind of incompatibility between JMS 1.1 (used by ActiveMQ) and JMS
> 2.0 (used in latest Qpid JMS client). But it might as well be anything else.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Milano Nicolum <dr...@gmail.com>.
Seems to me that Qpid JMS client is not compatible with my setup. I tried
to use latest snapshot as dependency, but at the moment I'm getting:
2016-12-13 07:59:11,815 | ERROR | Error in thread 'ActiveMQ Session Task-1'
| org.apache.activemq.thread.TaskRunnerFactory | ActiveMQ Session Task-1
java.lang.AbstractMethodError:
org.apache.activemq.command.ActiveMQBytesMessage.setJMSDeliveryTime(J)V
at org.apache.qpid.jms.JmsSession.send(JmsSession.java:772)
at org.apache.qpid.jms.JmsSession.send(JmsSession.java:742)
at
org.apache.qpid.jms.JmsMessageProducer.sendMessage(JmsMessageProducer.java:240)
at
org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:188)
at
org.apache.qpid.jms.JmsMessageProducer.send(JmsMessageProducer.java:175)
at org.apache.qpid.jms.JmsQueueSender.send(JmsQueueSender.java:50)
at
org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:83)
at
org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:135)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1401)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
So every time a message is to be sent, it fails on this error. I guess it
is some kind of incompatibility between JMS 1.1 (used by ActiveMQ) and JMS
2.0 (used in latest Qpid JMS client). But it might as well be anything else.
Re: Qpid JMS client JmsConnection.close() hangs
Posted by Milano Nicolum <dr...@gmail.com>.
Tomorow I plan to do some testing with 0.20.0-SNAPSHOT. The thing is I can
hardly use snapshots in my company's software (next release version of the
OSGi bundle I'm currently working on). So even if the fix made in
QPIDJMS-228 solves all my problems I have to wait for a release or find a
workaround. So I wanted to ask if there are any plans for 0.20.0 release at
the moment. Is it scheduled for January 2017, Q1 of next year or still not
decided at the moment?
Thanks for any information on this!
2016-12-01 17:35 GMT+01:00 Timothy Bish <ta...@gmail.com>:
> Close timeout handling has been fixed up a fair bit with issue:
> https://issues.apache.org/jira/browse/QPIDJMS-228
>
>
> On 11/25/2016 11:04 AM, Robbie Gemmell wrote:
>
>> "I also think I see an issue with the closeTimeout handling in that in
>> one place it seems likely to be using the requestTimeout value
>> instead. Need to investigate that further."
>>
>> Though in my attemps that didnt actually matter and the close
>> completed fine if the network dropped and no response could be
>> received (or was ever sent). As I say, needs more investigation.
>>
>> On 25 November 2016 at 15:49, DraCzech <dr...@gmail.com> wrote:
>>
>>> 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{error=null}
>>>>
>>>> on network lost vs.
>>>>
>>>> 2016-11-24 16:51:31.027968 [18734493:0] -> Close{error=null}
>>>> 2016-11-24 16:51:31.977722 [18734493:0] <- Close{error=null}
>>>>
>>> Shouldn't some timeout throw an exception or so?
>>>
>>>
>>>
>>> --
>>> View this message in context: http://qpid.2158936.n2.nabble.
>>> com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7654872.html
>>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
>>
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Qpid JMS client JmsConnection.close() hangs
Posted by DraCzech <dr...@gmail.com>.
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 case any QpidJMS Connection Executor
thread gets stuck (on lock, indefinite timeout etc.) it prevents the device
I'm using from clean shutdown. As I have no means of killing those threads
from my code.
Any chances this might become configurable with default value set to
nondaemon?
--
View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7655299.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org