JMS-send operation not working in a SessionBean [OC4J10.1.3.1.0-standalone]

Question

Salut,
i am envisaged with a nasty problem calling a message-send operation from
a method (transaction-type="required") inside a session bean (transaction-type="container").
This problem occured in OC4J 10.1.3.1 and may fail also in 10.1.3.0. The same
code run under OC4J 10.1.2.x without any problems.
The adressed JMS type is a OEMS JMS and fails to work regardless if the JMS ressource
is using a file-persistence or is running in-memory. Anyway the factory is a
jms/XAQueueConnectionFactory, so the created queue must support XA transactions.
Another test with an advanced-queue JMS provider succeeded.
As a consequence of this, i believe that the OEMS provider shall cause the problem.
The original code is quite unspectaculary:
* The non-surprising thing is, that the QueueConnectionFactory
* is a XAQueueConnectionFactory.
QueueConnectionFactory qcf = (QueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
c = qcf.createQueueConnection() ;
QueueSession s = c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
[... create a message ]
QueueSender qs = s.createSender(q)
qs.send(m);
qs.close()
s.close();
c.close()
The funny thing is, that the queue-session behaves as it is working outside
of a transaction context. Inside the JMX-Console you will notice the
arrival of a message and ... a cancellation of it. This would not surprise
me, if this code sequence would have been called outside of
a Session bean, cause the absence of a queue-session.commit does not
fix the send message in the jms ressource.
As a matter of fact the code is executed inside a Session bean and
the connection.createQueueSession will notice this and forget both
given parameters, and let the covering transaction take over of the
JMS ressource. But this does not happen (completly).
The acknowledge-mode has been modified (SESSION_TRANSACTED)
but the code still does not work!
After i recognized that the enlist-ment did not work, i
decided to enfore the use of XA transaction by using the
XA classes and methods of JMS.
I startet to cast the jndi-references and:
XAQueueConnectionFactory qcf = (XAQueueConnectionFactory) (jndiContext.lookup(MY_QFAC));
Queue q = (Queue) (new InitialContext().lookup(MY_QUE));
XAQueueConnection c = qcf.createXAQueueConnection() ;
XAQueueSession s = c.createXAQueueSession();
[... create a message ]
QueueSender qs = s.createSender(q)
qs.send(m);
qs.close()
s.close();
c.close()
The funny thing is ... the code worked without any problem until
the send operation, where i received an JMSException, containing
the text:
Oc4jJMS.Session.hpcl057.4e9c06e4:1112674930d:-7fff.41,true,SESSION_TRANSACTED]: An attempt was made to perform work in a XA-backed session without being enlisted. Either the session must be enlisted (using the JMS Connector or JMS Adapter) to participate in the global transaction, or a non-XA connection and a non-XA session should be used to not participate in the global transaction.
How bizarre, i thought the enlistment has been taken place by invoking
the c.createXAQueueSession or c.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
How bizarre how bizarre
any clues ????

Answer 1

OC4J JMS was changed to not auto-enlist in XA transactions.
In releases prior to 10.1.3 XA usage was not actually supported. (It did not meet all of the XA requirements when used with OC4J.)
Auto-enlisting by the JMS provider was also a spec violation, which was causing trouble for people who needed to do out-of-transaction work and had no way to do it.
In 10.1.3 XA usage is fully supported, but only when you use the JMS Connector. You can find the JMS Connector ("Oracle's Generic JMS Resource Adapter") demos here:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html#JMS
The JMS Connector is documented in the OC4J Services Guide, OEMS/JMS chapter.
-Jeff