Atomikos Forum

I am new to Atomikos. I integrated Atomikos with Spring following the example under installation folder. My app is a web app running in Tomcat.


After the app is running, it print log into console periodically, every second. I Found the log is printed by BaseTransactionManager.createCompositeTransaction(), which hard-codes the logging lever to INFO. I’d like to know:

1,  is the log normal? Or something wrong with my configuration?
2, why it hard-codes the level to INFO, is there any why to disable this log.

--below are for reference--
--The log printed to console--------------
May 30, 2012 1:38:55 PM com.atomikos.diagnostics.Slf4jConsole println
INFO: createCompositeTransaction ( 300000 ): created new ROOT transaction with id 10.148.69.17.tm0129800041

...

May 30, 2012 1:39:15 PM com.atomikos.diagnostics.Slf4jConsole println
INFO: createCompositeTransaction ( 300000 ): created new ROOT transaction with id 10.148.69.17.tm0135500041



--The method that hard-codes logging level--------------

    /**
    * @see CompositeTransactionManager
    */
   
    public CompositeTransaction createCompositeTransaction ( long timeout ) throws SysException
    {
        Stack errors = new Stack ();
        CompositeTransaction ct = null , ret = null;
        Thread thread = Thread.currentThread ();

        ct = getCurrentTx ();
        if ( ct == null ) {

            ret = service_.createCompositeTransaction ( timeout );
            printMsg ( "createCompositeTransaction ( " + timeout + " ): "
                    + "created new ROOT transaction with id " + ret.getTid (),
                    Console.INFO );
        } else {         
           
            printMsg ( "createCompositeTransaction ( " + timeout + " )",
                    Console.INFO );
            // let CT implementation do the details of logging
            ret = ct.getTransactionControl ().createSubTransaction ();

        }
        setThreadMappings ( ret, thread );

        return ret;
    }

The proper solution should be that of disabling INFO messages; this document may be useful:
http://www.atomikos.com/Documentation/UnderstandingTheLogs

However I am having an hard time too to setup logging but I am using Log4J and it may be unrelated to the topic of this thread, but if you are interested have a look at my post to this forum with subject "Unable to setup Slf4j-->Log4J logging in ATE-3.8.0"

Regards,

Jacopo