Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Java-SCA-1.4
-
None
-
None
-
Linux x86_64, Weblogic 10.3, Java 1.6.0_05
Description
I've taken a functional binding.jms environment, which currently works on Weblogic 9.2 and attempted to port it to Weblogic 10.3, however it looks like the underlying support from Weblogic has now changed as I see the following stack:
javax.jms.JMSException: [JMSPool:169801]The JMS method setMessageListener may not be called inside an EJB or servlet
at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
at weblogic.deployment.jms.WrappedMessageConsumer.preInvocationHandler(WrappedMessageConsumer.java:116)
at weblogic.deployment.jms.WrappedMessageConsumer_weblogic_jms_client_WLConsumerImpl.setMessageListener(Unknown Source)
at org.apache.tuscany.sca.binding.jms.provider.JMSBindingServiceBindingProvider.registerListerner(JMSBindingServiceBindingProvider.java:196)
at org.apache.tuscany.sca.binding.jms.provider.JMSBindingServiceBindingProvider.start(JMSBindingServiceBindingProvider.java:149)
Truncated. see log file for complete stacktrace
Dave.