[jira] Updated: (TUSCANY-2916) SOAP over JMS services do not function on Webspher e6.1

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

     [ https://issues.apache.org/jira/browse/TUSCANY-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ant elder updated TUSCANY-2916:
-------------------------------

    Fix Version/s: Java-SCA-1.5

> SOAP over JMS services do not function on Webspher e6.1
> -------------------------------------------------------
>
>                 Key: TUSCANY-2916
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2916
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.4
>         Environment: Websphere 6.1 on Linux x86_64
>            Reporter: Dave Sowerby
>             Fix For: Java-SCA-1.5
>
>
> I'm trying to get a SOAP/JMS service to function within Websphere 6.1 (FP 17), it's deployed as a webapp and functions normally on weblogic.
> When the filter is initialised, I get the following error:
> Caused by: javax.jms.IllegalStateException: CWSIA0084E: The method MessageConsumer.setMessageListener is not permitted in this container.
>         at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl._setMessageListener(JmsMsgConsumerImpl.java:659)
>         at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.setMessageListener(JmsMsgConsumerImpl.java:608)
>         at org.apache.axis2.transport.jms.JMSConnectionFactory.listenOnDestination(JMSConnectionFactory.java:458)
>         at org.apache.axis2.transport.jms.JMSConnectionFactory.listen(JMSConnectionFactory.java:421)
>         at org.apache.axis2.transport.jms.JMSListener.start(JMSListener.java:319)
>         ... 44 more
> Searching around the subject I find that this is because the JMS Message Listener should be implemented in an other (perhaps MDB) way.
> Also, it appears that Axis2 has resolved this issue and is covered by AXIS2-3662.

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