My Oracle Support Banner

Problems With JMS Spring Cluster Deployment on Weblogic (Doc ID 1498444.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


When deploying a spring jms application in cluster environment it is failing with below exception.

Caused By: javax.naming.NameNotFoundException: Unable to resolve , 'jms.test.topic'. Resolved 'jms'; remaining name 'topic'


which made to use lazy look up by below settings

Spring application to consume the messages from a topic using below configuration.

<jee:jndi-lookup id="connectionFactory" lookup-on-startup="false" cache="false" proxy-interface="javax.jms.ConnectionFactory" jndi-name="" />
<jee:jndi-lookup lookup-on-startup="false" cache="false" proxy-interface="javax.jms.Topic" id="testTopic" jndi-name="jms.test.topic" />

Once we configure we are not seeing any issue during deployment time but if we try to consume message from spring pojo class we are running in to below exception.




 Changed spring framework to lazy look up


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.