MustGather: Problems using JAAS for WebSphere Application Server V5.0 and V5.1
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for JAAS problems with IBM® WebSphere® Application Server V5.0 and V5.1. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem
If you have already contacted support, continue on to the component specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.

Collecting JAAS specific MustGather information

It can be very difficult determining the root cause of a JAAS problem. In order to help problem determination, please collect the following:
  1. A clear, specific problem description, including specific usage information and error scenario.

  2. Specify if the problem is with JAAS login or whether JAAS login is successful.

  3. If the problem is with JAAS login, are you using your own JAAS login module? If so, request the Support team to send you a sample login module to test. Also, send your JAAS login module in to Support.

  4. Specific instructions on how to recreate the problem you encountered.

  5. If possible, include a minimal testcase.

  6. Open up the administrative console.

  7. Expand Servers > Application Servers > server_name.

  8. Select Diagnostic Trace Service.

  9. Increase the Maximum Number of Historical Files to 10, set the Maximum File Size to 20 MB and clear the trace string in the Trace Specification field and replace with the following trace string:

    com.ibm.ws.security.*=all=enabled

  10. Click Apply and then Save.

  11. Delete or rename the logs in the install_root/logs directory. If you are running the deployment manager (dmgr), also delete the logs in the dmgr_install_root/logs directory. This ensures that the logs are fresh.

  12. Recreate the problem. Make note of the time the problem occurs, the user ID, and the exact URL being invoked.

  13. Run the collector tool located in the install_root/bin directory on both Network Deployment (for federated environment only) and Base Application Server profiles. The collector tool must be run as root user. Do not run this file directly from the /bin directory or any other WebSphere Application Server directory. Do not use the -summary option.

  14. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Java™ Security component, search the WebSphere Application Server support site
 
Related information
Submitting information to IBM support
Steps to get support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Security
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1205253
IBM Group: Software Group
Modified date: Apr 30, 2005