Binod,
As discussed, I am sending an email on the query on the Resource Adapter. We use the Sun’s Generic Resource Adapter as the base and have created our custom package
on top of it to integrate our JMS provider into a Java EE application server.
I have a JMS Client program which takes part in a XA transaction in a container managed bean (Weblogic Application server is the Transaction Manager).
When the client closes the JMS Connection in the bean, I am seeing that the call to the javax.jms.Connection.close() actually closes the
the underlying jms connection well before the transaction commit is done. I understand that a javax.jms.Connection.close() operation in a XA Transaction should
be managed a Java EE JMS Resource Adapter wrapper code that will terminate the underlying connection upon completion of the transaction manager's work
But the problem is that our JMS Resource adapter built on top of Sun’s RA only provides JCA support to JBoss and Websphere but not to WebLogic application server.
We only have ASF support for web logic. Given that we only have support ASF for web logic and do not support JCA 1.5 for weblogic, how do we handle this scenario?
Please let me know what alternatives do I have.
The stack trace below explains what is happening.( WmConnectionImpl.java is the jms provider implementation of javax.jms.Connection)
at com.webmethods.jms.impl.WmConnectionImpl.close(Unknown Source)
at weblogic.deployment.jms.WrappedConnection.close(WrappedConnection.java:159)
at test.TestJMSBean.sendMessage(TestJMSBean.java:160)
