Atomikos Forum

Slf4Jonsole - neverending logs

Hi,

I am using JMS Listener with AtomikosTE, and receive a neverending stream of log entries from Atomikos' Slf4Jconsole (see the snippet below). They look to belong to the JMS Listener's polling cycle.

As they fill up the log file (hopefully?) unnecessarily, I would like to get rid of them, with no success. Even if I turn off log4j logger for 'com.atomikos' they survive.

My jta.properties is:
com.atomikos.icatch.automatic_resource_registration=false
com.atomikos.icatch.console_log_level=WARN
com.atomikos.icatch.force_shutdown_on_vm_exit=true
com.atomikos.icatch.service=com.atomikos.icatch.standalone.UserTransactionServiceFactory

Spring JMS listener config:

  <jms:message-driven-channel-adapter
    id="jmsin"
    channel="mailIn"
    container="messageListenerContainer" />
   
  <bean id="messageListenerContainer"
          class="org.springframework.jms.listener.DefaultMessageListenerContainer">
        <property name="transactionManager" ref="transactionManager" />
        <property name="connectionFactory" ref="atomikosJmsConnectionFactory" />
        <property name="destinationName" value="incomingCustomerMailQueue" />
        <property name="concurrentConsumers" value="1" />
        <property name="receiveTimeout" value="3000" />
        <property name="sessionTransacted" value="true"/>
    </bean>

The only chance I saw, is to increase receiveTimout in Spring's DefaultMessageListener (in order to get less of them :)

Is there any way to turn these annoying logs off?

I am using AtomikosTE 3.7.0M4 + Spring 3.0.3.RELEASE + Spring integration 2.0.0.M7 + ActiveMQ 5.4.0 + slf4j 1.5.8 + log4j 1.2.14.

regards
Richi

INFO - Slf4jConsole.println(110) | createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.100.tm0000100031
INFO - Slf4jConsole.println(110) | registerSynchronization ( com.atomikos.jms.ConsumerProducerSupport$JmsRequeueSynchronization@f04a01af ) for transaction 192.168.1.100.tm0000100031
INFO - Slf4jConsole.println(110) | addParticipant ( XAResourceTransaction: 3139322E3136382E312E3130302E746D30303030313030303331:3139322E3136382E312E3130302E746D31 ) for transaction 192.168.1.100.tm0000100031
INFO - Slf4jConsole.println(110) | XAResource.start ( 3139322E3136382E312E3130302E746D30303030313030303331:3139322E3136382E312E3130302E746D31 , XAResource.TMNOFLAGS ) on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@16954e1
INFO - Slf4jConsole.println(110) | commit() done (by application) of transaction 192.168.1.100.tm0000100031
INFO - Slf4jConsole.println(110) | XAResource.end ( 3139322E3136382E312E3130302E746D30303030313030303331:3139322E3136382E312E3130302E746D31 , XAResource.TMSUCCESS ) on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@16954e1
INFO - Slf4jConsole.println(110) | XAResource.prepare ( 3139322E3136382E312E3130302E746D30303030313030303331:3139322E3136382E312E3130302E746D31 ) returning XAResource.XA_RDONLY on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@16954e1
INFO - Slf4jConsole.println(110) | createCompositeTransaction ( 300000 ): created new ROOT transaction with id 192.168.1.100.tm0000200031
INFO - Slf4jConsole.println(110) | registerSynchronization ( com.atomikos.jms.ConsumerProducerSupport$JmsRequeueSynchronization@f1feda4e ) for transaction 192.168.1.100.tm0000200031
INFO - Slf4jConsole.println(110) | addParticipant ( XAResourceTransaction: 3139322E3136382E312E3130302E746D30303030323030303331:3139322E3136382E312E3130302E746D32 ) for transaction 192.168.1.100.tm0000200031
INFO - Slf4jConsole.println(110) | XAResource.start ( 3139322E3136382E312E3130302E746D30303030323030303331:3139322E3136382E312E3130302E746D32 , XAResource.TMNOFLAGS ) on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@172290f
INFO - Slf4jConsole.println(110) | commit() done (by application) of transaction 192.168.1.100.tm0000200031
INFO - Slf4jConsole.println(110) | XAResource.end ( 3139322E3136382E312E3130302E746D30303030323030303331:3139322E3136382E312E3130302E746D32 , XAResource.TMSUCCESS ) on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@172290f
INFO - Slf4jConsole.println(110) | XAResource.prepare ( 3139322E3136382E312E3130302E746D30303030323030303331:3139322E3136382E312E3130302E746D32 ) returning XAResource.XA_RDONLY on resource amq1 represented by XAResource instance org.apache.activemq.TransactionContext@172290f
Firesign Send private email
Thursday, November 04, 2010
 
 
Hi,

If you set the log level to WARN they should be gone.

HTH
Guy Pardon Send private email
Thursday, November 04, 2010
 
 
Please make sure to set the Log4J level to WARN also for anything in com.atomikos...
Guy Pardon Send private email
Thursday, November 04, 2010
 
 
Yes, I've found the real reason looking into the sources.
The SlfJConsole class uses the "atomikos" log topic instead of the usual "com.atomikos" style.

So the correct log4j configuration is:

  <logger name="atomikos">
    <level value="WARN" />
  </logger>

one might also want to get rid of additional neverending logs from the Spring framework:

  <logger name="org.springframework.transaction.jta">
    <level value="INFO" />
  </logger>

thanks for the hint,
regards
R.
Firesign Send private email
Sunday, November 07, 2010
 
 

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

Other recent topics Other recent topics