qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: Qpid JMS client JmsConnection.close() hangs
Date Tue, 13 Dec 2016 10:47:28 GMT
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


On 13 December 2016 at 08:18, Milano Nicolum <draczech@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

View raw message