[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585636#action_12585636
]
George Marrows commented on AXIS2-3662:
---------------------------------------
Hi Asankha - thanks for looking at this.
I agree that the polling option does not seem sensible. Like Cathal (originator
of the mail used in the bug report), I'm developing a custom MDB-based
approach. You're right this will lose hot deployment of new services that need
to listen on a new queue/topic (because a new MDB will also need to be declared
to listen on that destination), but I hope to be able to maintain hot update of
changed services. Perhaps that's an acceptable compromise for running on a
wider range of app servers in a J2EE-compliant way?
Another option of course is to see how other ws stacks have handled this issue,
if any have.
-- George
> Can't use JMS transport from axis2.war on WebSphere Application Server 6.1
> --------------------------------------------------------------------------
>
> Key: AXIS2-3662
> URL: https://issues.apache.org/jira/browse/AXIS2-3662
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.3
> Environment: WebSphere Application Server 6.1, Axis2 war deployment
> Reporter: George Marrows
>
> From
> http://www.nabble.com/setMessageListener-not-permitted-in-Websphere-td15306747.html:
>
> > We are currently deploying axis2 in Websphere 6.1. We wish to
> > use the jms transport. However axis2 fails to start because
> > it uses forbidden api's.
> >
> > On startup axis2's JMSConnectionFactory class calls the
> > listenOnDestination(String destinationJndi) method. Here it
> > creates a MessageConsumer and calls the
> > MessageConsumer.setMessageListener(MessageListener listener)
> > method. This causes failure and the exception thrown is as follows:
> > javax.jms.IllegalStateException: Method setMessageListener
> > not permitted
> >
> > On looking through docs online it is clear that IBM have
> > stuck to the J2EE
> > 1.4 specification. This states that the
> > MessageConsumer.setMessageListener(MessageListener listener)
> > method can not be called in a Web or EJB container. See
> > http://www.ibm.com/developerworks/library/j-getmess/ for details.
> [See http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf, section 6.6 for the
> actual spec reference.]
> This means that the only way of deploying Axis2 with JMS transport on WAS is
> to use the standalone axis server. This works, but a deployment within the
> application server would be greatly preferable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
