3 Replies Latest reply on Oct 2, 2014 1:46 PM by davidj

Avoid logging "com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning" messages

davidj Jul 15, 2013 1:14 PM

We have a legacy application running on JBoss 4.2.3 and the server log file is overrun with:

[com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning] [com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning] Multiple last resources have been added to the current transaction. This is transactionally unsafe and should not be relied upon. Current resource is org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@65a6bc76

messages. At this point, I don't care how or why this message is being logged; I JUST WANT IT GONE!

It is becoming a major problem due to the shear volume (we have several nodes).

Can someone please explain the steps to prevent this message from being logged?

Thanks.

1. Re: Avoid logging "com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning" messages

welle Jul 15, 2013 5:11 PM (in response to davidj)

Look for the "com.arjuna.ats.jta.allowMultipleLastResources" at: https://community.jboss.org/wiki/Multiple1PC
(I'm not sure but i think it is availabale in JBoss 4.2.3)

And when you do please read why you should care why this message are being logged

Another "solution" would be to filter it out in the logging setup...
Actions
2. Re: Avoid logging "com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning" messages

welle Jul 15, 2013 5:19 PM (in response to welle)

Opps... I guess you alread have found that flag...

The warning you have cannot be removed soo you have to tweak the logging setup to ignore it. (Look for the Log4j RegexFilter for an example)

(And you still should fix it!!!)
Actions
3. Re: Avoid logging "com.arjuna.ats.internal.jta.transaction.arjunacore.lastResource.multipleWarning" messages

davidj Oct 2, 2014 1:46 PM (in response to welle)

Not that anyone cares anymore, but this legacy project is now being upgrade to run on JBoss EAP 6.3 and that message has now disappeared. This is very good news because our server log files were littered with this statement; I'm talking about tens of thousands of lines.
Actions

Go to original post