Problems With JMS Spring Cluster Deployment on Weblogic
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 126.96.36.199 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.
which made to use lazy look up by below settings
<jee:jndi-lookup id="connectionFactory" lookup-on-startup="false" cache="false" proxy-interface="javax.jms.ConnectionFactory" jndi-name="jms.com.sample.domain.XAConnectionFactory" />
<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
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 hundreds of Community platforms