[jira] Commented: (TUSCANY-2952) binding.jms does not function on Weblogic 10.x

["ant elder (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694567#action_12694567 ] 

ant elder commented on TUSCANY-2952:
------------------------------------

Thats a nuisance, its an expected exception that the code is trying to catch but I guess its being a bit too restrictive in the exception its catching, the spec does only specifically mention the JMSException so 10.3 isn't doing anything wrong and the Tuscany code should deal with it. We can fix it for the Tuscany 1.5 release but there's been no talk of when that might happen yet, how much of a problem is this going to be for you?



> binding.jms does not function on Weblogic 10.x
> ----------------------------------------------
>
>                 Key: TUSCANY-2952
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2952
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA JMS Binding Extension
>    Affects Versions: Java-SCA-1.4
>         Environment: Linux x86_64, Weblogic 10.3, Tuscany 1.4
>            Reporter: Dave Sowerby
>
> I've taken a webapp containing a binding.jms service which functioned on weblogic 9.2 and attempted to port to weblogic 10.3, however I get the following error on node/application startup:
> <01-Apr-2009 14:56:01 o'clock BST> <Warning> <Deployer> <BEA-149078>
> <Stack trace for message 149004
> weblogic.application.ModuleException:
>        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
>        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
>        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
>        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
>        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
>        Truncated. see log file for complete stacktrace
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.