IBM Support

MustGather: JavaMail

Troubleshooting


Problem

Collecting data for problems with the IBM WebSphere Application Server JavaMail component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

Resolving The Problem

If you already contacted support, continue to the JavaMail MustGather information. Otherwise, click MustGather: Read First for all WebSphere Application Server Products.

The debugger must be run on the mail session in question to troubleshoot JavaMail problems. Use the following instructions to gather that information.



Engaging debug for your JavaMail session
  1. From the Application Server administrative console:
    select Resources > Mail Providers > Built-In Mail Provider > Mail Sessions.

  2. Select the JavaMail session that you want to debug.

  3. At the bottom of the pane, select Enable debug mode (see screenshot below).

  4. Click Apply.
  5. Set up trace using the following trace string com.ibm.ws.mail.*=all. Run this trace while you are set up in the debug mode

  6. Save the change to the master configuration.

  7. Stop the Application Server.

  8. While the Application Server is stopped, remove the present log files located in the logs directory under your WebSphere Install Home, or save these files in another location.

  9. Restart the Application Server.

  10. Run your mail application and note the exact time when the error occurs.





When you finish your debugging session, reverse the preceding process to disable the debugger. This avoids generating a larger file than normal.

Note: You must stop your Application Server again to remove the debug option.

Collect the SystemOut.log, the StandardOut.log and the SystemErr.log from the logs directory, then follow instructions in Submitting Diagnostic Information to IBM Technical Support for Problem Determination.


Note:
If using JavaMail and the information is hardcoded instead of creating a mail session in the administrative console, then this procedure is not supported. If the information is hardcoded, Application Server features are not being used, only the Application Server JRE is, and you are responsible for your own code. In this case there is no mail session on which to set the debugger.

If this is the case, go into the object you created that contains the JavaMail properties and set the property mail.debug = true. This produces a file containing the debug information. You can use this file to see what code you must change to correct your problem.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java Message Service (JMS)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21204196