Hi,
I committed the log4j configuration change using the original format (no stdout logging).
I tried the change proposed by Marcel, but the unit tests still output a
couple of WARN and ERROR messages, including a lengthy transaction
exception.
I'm afraid, this lengthy stack trace is caused by an intentionally occurring XAException when committing a new REFERENCE property pointing to a node that has been deleted by another session. Since XAExceptions can simply contain an XA error code but not a root cause, I decided to log the actual exception that occurred inside the code section rethrowing an XAException. I just realized that I could have declared a derived XAException class that also has a constructor including the root exception which would then still be accessible by Throwable.getCause() on the calling side, which would remove the lengthy stack trace.
Cheers Dominique
