Troubleshoot java.lang.NoClassDefFoundError error in a molecule

Document created by vreddy Employee on Nov 5, 2013
Version 1Show Document
  • View in full screen mode
For a molecule or private cloud, the jar files exist on a separate fileshare from the host running the atom nodes that are part of the molecule. The java class loader loads these classes dynamically. If it can not access the jar files on the fileshare it could cause issues and throw the 'java.lang.NoClassDefFoundError' error.

This error may also be caused by a corruption issue with the java installed in the fileshare. Restarting the atom nodes will refresh the java libraries and connections.

If you continue to observe this issue occur after restarting the atom nodes, you may want to install a network monitoring program between the atom node experiencing the issues and the fileshare host to see if there are stability issues.

If you see this error in the Dell Boomi Atom cloud please open a support case with the account id and the execution id.