All geek questions in one place

How to debug CMT transaction boundaries?

I studied jboss CMT and would like to know how a transaction works from top to bottom, the best way would be to print debugging information in a log file, I included org.hibernate.SQL, however, I only get SQL, the type “begin” does not exist in the log or The commit associated with the transaction remains unchanged when debugging from the org.hibernate level. *.

I searched a bit in googling, it seems that tweaking jbosstx-properties.xml, tried it, it didn't help either. Can someone help me with this?

+4
source share
1 answer

I followed the recommendations in the first section: http://i-proving.com/2010/05/28/enabling-debug-in-jboss-core/ which basically tells you:

Set "Com.arjuna.common.util.logging.DebugLevel" in the "general" section of / server // conf / jbossjta -properties.xml to 0xffffffff

and make sure your jboss-log4j configuration does not filter these messages.

And he began to receive such messages in magazines:

15:13:00,276 DEBUG [logger] BaseTransaction.commit 15:13:00,283 DEBUG [logger] BaseTransaction.getStatus 15:13:00,283 DEBUG [logger] BaseTransaction.begin

(and thousands of others, but that's a different story. It seems that Arjuna / JBoss transactions do not use the idea of ​​log categories)

Tested on JBoss 4.2.3.GA, but I think you have a completely different version of JBoss if you tried to edit jbosstx-properties.xml , which my JBoss does not have.

+3
source

Source: https://habr.com/ru/post/891805/

More articles:


All Articles