Atomikos Forum

Allow to switch-off logging files (tm.out)

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. :-(
cesnek Send private email
Thursday, October 16, 2008
 
 
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...
Guy Pardon Send private email
Friday, October 17, 2008
 
 
I know, some write space we have. But not for duplicating logs messages. One in slf4j and same messages in tm.out.
cesnek Send private email
Friday, October 17, 2008
 
 
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?
Guy Pardon Send private email
Saturday, October 18, 2008
 
 
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!
cesnek Send private email
Monday, October 20, 2008
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics