[
https://issues.apache.org/jira/browse/TUSCANY-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681494#action_12681494
]
Simon Laws commented on TUSCANY-2916:
-------------------------------------
Hi Dave
Part of the fix to Axis also involved separating the JMS transport and putting
it in ws commonf
http://mail-archives.apache.org/mod_mbox/ws-axis-user/200812.mbox/%[email protected]%3e
A bit more info here
http://adroitlogic.org/knowledge-base-axis2/9-the-enhanced-jms-transport.html
I don't know whether it's possible to use the new transports with 1.4.1 (which
is what we are based on at the moment) or whether we will have to move up to
1.5 (when it comes out) to get this function. A move to 1.5. may or may not be
straightforward for 1.x depending on what they have changed in Axis so I'll do
a bit of research into the new transport implementation and see what the story
it.
> 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
>
> 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.
