Atomikos Forum

1) Never use System.out or System.err

It is very ugly in enterprise applications and completly illegal in applications servers.

2) Tweak logging levels to reasonable values.

example :

No properties path set - looking for transactions.properties in classpath...
Must be DEBUG or INFO not ERROR.

Using init file: /X:/java/daisy/daisy/daisy/WEB-INF/classes/jta.properties
Must be INFO not ERROR.

USING com.atomikos.icatch.soap_commit_protocols = atomikos,wsat
USING com.atomikos.icatch.console_file_name = tm.out
Must be INFO not WARN.


This is not cosmetics! It is important to all messages ends in appliacation servers log files where are manageables - not console.

Hi,

We can change the USING level to INFO, but I think the System.err should stay: otherwise, there would be no way of detecting what jta.properties is being used - especially if there are multiple conflicting candidates in the classpath.

Detect if logging subsystem is avaliable and then send this message NOT to System.err but logger.info().

Sytem.err is unmanagable. Always endup in some file no one look in. Logger you can send to DB, web interface, server log, and so on ..