MustGather: JavaMail

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. Make sure to select the correct scope the JavaMail session is defined under. 
    

3. At this pane, select Enable debug mode:

    

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 configuration.
    

7. If the issue is related to the certificates, add the following custom property (below) and additional trace specification (Step 8).

   Navigate to Servers > Server Types > WebSphere application servers > server_name > Server Infrastructure > Java and Process Management > Process definition > Java Virtual Machine > Custom properties:

   Name: javax.net.debug
   Value: all 

   Define this property in all JVMs under the same scope as the JavaMail session. 
   As a suggestion, choose a scope that points to a unique JVM (for instance, Node:server9Node1,Server=server1), then define a new JavaMail session with the same configuration as the problematic one and use this JVM for the debug process.

   

8. Change the trace string to: *=info:com.ibm.ws.mail.*=all:SSL=all
    
9. Stop the Application Server.
    
10. While the Application Server is stopped, remove the present log files located in the logs directory under your WAS_HOME/logs or save these files in another location.
     
11. Restart the Application Server.
     
12. Run your mail application and note the exact time when the error occurs.
     
13. When you finish your debugging session, reverse the preceding process to disable the debugger. This avoids generating larger than normal files.
    
    Note: You must stop your Application Server again to remove the debug option.
     
14. Run the collector tool and send in the data.
    
    Note: If you are running in a Network Deployment environment, run on both Network Deployment and Node profiles. 
    For more information, see the following Information Center topics:

Gathering information with the collector tool - V9.0

Gathering information with the collector tool - V8.5

• In addition to the documents about the collector, IBM made available the following video which shows collector in Windows environment

"How to I gather the collector tool output for WebSphere Application Server Support?"

For Unix environments the video can still be used.  You just need to adapt the paths to Unix style, the extension from .bat to .sh and use root user ID instead of Administrator

• Then follow the instructions in Submitting Diagnostic Information to IBM Technical Support for Problem Determination.
  
  
  Note:
  If using JavaMail where the information is hard-coded instead of creating a mail session in the administrative console, then this procedure is not supported. If the information is hard-coded, Application Server features are not being used (only the Application Server JRE is being used), 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.