How to enable debug mode in an atom

Document created by vreddy Employee on Nov 12, 2013Last modified by mike_aronson on Feb 28, 2017
Version 2Show Document
  • View in full screen mode
How to enable debug mode in an atom using atom.vmoptions.

There are two ways to enable debug mode in an atom.

 

Note: Debug mode should only be enabled to troubleshoot an issue and should be disabled when not necessary. Leaving debug mode on during general atom operation could impact the performance of the atom and also create very large log files potentially using up needed disk space.


1.)

The container.properties com.boomi.container.debug=true option is a Boomi option that is used to tell the container to output debugging statements that have been written into the code.

The recommended method is to set com.boomi.container.debug=true in the container.properties file. This is generally sufficient for troubleshooting most issues. It will provide the information we will typically be looking for when troubleshooting problems.


Edit the <atom directory>/conf/container.properties file. Add the following line to the end of the file:

com.boomi.container.debug=true

 

2.)
The javax.net.debug property is an property of the Oracle Java Secure Sockets Extension (JSSE) which turns on debugging for troubleshooting issues with secure contexts (SSL handshakes, SSL/TLS packet transmissions, etc.):

http://docs.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#Debug

The javax.net.debug option may be useful for troubleshooting particularly tricky SSL problems; however, enabling this option is not recommend setting it unless advised by a Boomi Support.


Edit the <atom directory>/bin/atom.vmoptions file. Add the following line to the end of the file:

-Djavax.net.debug=all


 


 
1 person found this helpful

Attachments

    Outcomes