On 2003.06.04 18:23 Marek Lange wrote:
David Jencks schrieb:
I don't know what the Oracle error means, but you do not need an xa datasource for jbossmq xa. In fact the jbossmq xa jdbc connections are
set
to autocommit while in use by jbossmq, as it handles transactions independently of the database.
David,
thanks for the information! That helped a lot.
To test this, I have written a client which sends a message to a queue and writes an entry into a database table (one method with transaction attribute "Required"). When the insert of the database entry is not successful, the transaction is rolled back via context.setRollbackOnly(). This is only working with the usage of the "java:/JmsXA" connection factory and not with "(XA)ConnectionFactory". Is this expected (I believe: yes)?
yes
When I use the "java:/JmsXA" connection factory I get these logs. Is there a reason why they are there? I closed my connection.
Hmmm.. So far these messages have always been accurate, but there's always a first time. Are you sure you closed the java:/JmxXA connection? can you show your code?
Ok, I forgot to close the session (queueSession.close()), just executed queueConnection.close(). It was too late yesterday :-)
Thanks,
-marek
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
