Atomikos Forum

Even if org.slf4j.Logger class is detected, Atomikos always open and write to file "tm.out".

We working on read-only filesytem and files like tm.out and .epoch is blocker problem. :-(

Read-only filesystem? That would mean we can't log two-phase commit information either, so transactions won't work correctly. Merely switching off the tm.out will not solve this IMHO. You need a writable disk for correctness...

I know, some write space we have. But not for duplicating logs messages. One in slf4j and same messages in tm.out.

OK then why don't you limit the tm.out log volume by:

-setting the file count to 1
-setting the size limit to 1000 bytes of less

That should work no?

Anyway, it is very bad idea maintain own logging or write to system.out. In every J2EE novice book it is explicitly forbiden to do that. And Atomikos is (or should be) J2EE component.

Think of it once more. If you have five clustered mashines. Where you will look for logs? In some files in five location ? And more - for every used component in another log file with another format, and so on...

Never ever!