Collecting information and data for problems with IBM WebSphere Application Server Contexts and Dependency Injection(CDI), like ambiguous or unsatisfiable dependency, passivating scope dependencies, producer and decorator errors, etc. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.
Resolving The Problem
Answers to the following questions and data collection are necessary for IBM Support to begin debugging the problem:
Answer these questions about your WebSphere environment:
- What kind of environment is this: production/test/development/etc.?
- What is the packaging of your WebSphere Application Server: Network Deployment/Base/Express/eWAS/etc.?
- Are you running the recommended or latest fix pack for WebSphere Application Server?
Answer the following questions about the problem:
- Was this working before without any issues and now something has changed or is this the first time you have attempted the failing scenario?
- What activities were taking place when the problem was noticed? (Application Deployment, interaction with other Java EE producers, etc.)
- Are you able to consistently make the problem happen or is there no apparent trigger or timing?
- Describe the steps you would take to try and recreate the issue.
- Are there messages you can point us to in the SystemOut.log, or something else like a screen shot that has a timestamp of the problem? If not, please provide your best estimate of the date/time and where (what JVM) the problem occurred.
- Have you used the WebSphere Application Server Support Portal to research this problem?
- Have you taken any steps to try and resolve this issue? If so what steps did you take?
- Are you sure the issue is related to CDI? Check the troubleshooting web applications section of the WebSphere Application Server Information center.
Steps to collect the needed materials:
In the WebSphere Application Server Administrative Console, navigate to TroubleShooting > Logs and Trace > server_name.
Select JVM Logs. Set the Maximum Size to 10 MB and Maximum Number of Historical Log Files to 5.
Click Apply, go back to TroubleShooting > Logs and Trace > server_name.
Select Diagnostic Trace. Set the Maximum File Size to 20 MB and Maximum Number of Historical Files to 5.
Click Apply, then select Change Log Detail Levels.
Record what is in the trace specification so you can restore it later, replace it with the following trace specification:
Note: If debugging interaction with Java EE injection and/or the EJB container add: EJBContainer=all:MetaData=all:Injection=all
Note: If debugging interaction with web-related scopes and/or life cycles add: all:com.ibm.ws.wswebcontainer*=all
Click Apply, and Save.
Stop the JVM (server), back up the logs in the following directory to a directory outside the WebSphere filesystem, then delete them.
Then restart the JVM. This ensures that the logs are fresh.
Recreate the issue you are working on and tell us the day and time that it was recreated.
When you run the collector tool, it creates a jar file with the information about that profile that it was run against, please send us the jar file(s) that the collector tool created. If you need help running the collector tool check out the WebSphere Application Server Information Center article about how to run the collector tool.
Follow instructions to send diagnostic information to IBM support.
Remember to "undo" the tracing.
15 June 2018