JMS Connector Logging and Debugging Activities¶

Logging JMS Listening and Polling Activities¶

For debugging, it may be advantageous to change the log levels for listening and poling activities. Be aware that the DEBUG levels can result in large log files. To change the log levels when debugging, edit the Log4J (http://log4j.logger.org/) properties as described below. After updating the log4j.agent.properties or log4j.properties file, you must restart the Jitterbit services for the change to take effect.

Note

The information on this page applies to Private Agent version 10.34 and earlier.

JMS Listen Activity¶

The log file for the JMS Listen activity is located at ${JITTERBIT_HOME}/logs/jitterbit-component-listener.log
Edit the file ${JITTERBIT_HOME}/Resources/log4j.agent.properties
Change

log4j.logger.org.jitterbit.connector.jms = INFO, STDOUT, COMPONENTLISTENERFILE
log4j.logger.org.jitterbit.connector.listener = INFO, STDOUT, COMPONENTLISTENERFILE

to

log4j.logger.org.jitterbit.connector.jms = DEBUG, STDOUT, COMPONENTLISTENERFILE
log4j.logger.org.jitterbit.connector.listener = DEBUG, STDOUT, COMPONENTLISTENERFILE

JMS Poll, Browse, Send/Publish Activity¶

The log file for the JMS Poll, JMS Browse, and JMS Send/Publish activities is located at ${JITTERBIT_HOME}/logs/jitterbit-axis.log
Edit the file ${JITTERBIT_HOME}/tomcat/webapps/axis/WEB-INF/lib/log4j.properties
Change

log4j.rootLogger = INFO, STDOUT, FILE

to

log4j.rootLogger = DEBUG, STDOUT, FILE

Note

Debugging activities write additional information to disk and may consume a large volume of disk space over time. If such activities are needed on a consistent basis, we recommend that a process be put in place to archive such files over time so as not to run out of disk space.