]
Ovidiu Feodorov updated JBMESSAGING-410:
----------------------------------------
Priority: Critical (was: Major)
java:/JmsXA in no-tx context does not work the same way as JBossMQ
------------------------------------------------------------------
Key: JBMESSAGING-410
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-410
Project: JBoss Messaging
Issue Type: Bug
Components: Configuration and Management
Affects Versions: 1.0.1.CR2
Reporter: Elias Ross
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.0.1.CR5
The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ
does not work with JBoss Messaging. And actually the same code does work correctly with
SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory.
Why allow the use java:/JmsXA without transactions? It makes sense to use a cached
connection manager anyway, like you would with a database. And anyway, should be addressed
for compatibility.
The following code *should* successfully send a message to a queue running without a
transaction. Currently, it doesn't seem to do anything and no usage warnings are
produced.
QueueConnectionFactory queueCF = (QueueConnectionFactory)new
InitialContext.lookup("java:/JmsXA");
...
QueueConnection queueConnection = queueCF.createQueueConnection();
QueueSession queueSession =
queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
QueueSender queueSender = queueSession.createSender(queue);
ObjectMessage om = queueSession.createObjectMessage();
queueSender.send(om);
queueSender.close();
queueSession.close();
queueConnection.close();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: