[rabbitmq-discuss] JNDI / .bindings with RabbitMQ JMS Client?

[Steve Powell]

Hi, sorry I didn’t see this before today.

It looks to me as though the JNDI server is populated with an older com.rabbitmq.jms.admin.RMQConnectionFactory version.  In RJMS 1.1.0 some extensions were made to the JNDI for connection factories to allow for ssl connections and the AMQP interoperability feature.  This meant that previously serialised RMQConnectionFactory objects (for example in a JNDI server store) are not de-serializable under later versions of RJMS.

The solution to your problem would be to re-populate the JNDI server with RMQConnectionFactory objects created with the same level of RJMS as the application is expecting.

Please come back to me, if this doesn’t’ fix it.

Steve Powell  [Cell: +44-7815-838-558]
    Good design […] is as little design as possible.    Dieter Rams

On 20 May 2014, at 07:10, scguy <npetrace at gmail.com> wrote:

> Looks like this might be version related?  I "downgraded" to rabbitmq-server
> 3.1.5 and rabbitmq-jms-1.0.5 and everything worked.  Further suggestions or
> comments on this are appreciated.
> 
> 
> 
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/JNDI-bindings-with-RabbitMQ-JMS-Client-tp35631p35678.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140520/5e98f64f/attachment.html>