Question & Answer
Question
What information,logs, and traces should I gather and send to IBM Support to troubleshoot a problem with the Intelligent Management P2P communication layer in WebSphere Application Server?
Cause
WebSphere Application Server 8.5.5 and above includes a rich set of operations capabilities called Intelligent Management. The P2P communication layer is a key component in ensuring these capabilities function correctly. Disruptions in the communication layer can cause certain Intelligent Management features to work incorrectly. Intelligent Management requires the following ports to communicate in a bi-directional manner.
OVERLAY_UDP_LISTENER_ADDRESS
OVERLAY_TCP_LISTENER_ADDRESS
XD_AGENT_PORT
OVERLAY_TCP_LISTENER_ADDRESS
XD_AGENT_PORT
Additional details can be found from this article for WAS 9.0 and above:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rwve_portnumbers.html
For WebSphere 8.5.5 view this link:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/rwve_portnumbers.html
Typical causes of the disruption can be attributed to incorrect network settings at the Operating System level or blockages caused by a network firewall. Other common causes are port conflicts or severe resource constraints that prevent normal network communications.
If you are encountering problems with the P2P layer, please gather this information and send it to IBM Support
Answer
- Ensure total trace size that is allowed to be captured is at least 1 GB by following these steps: https://www.ibm.com/support/pages/node/89123
- Set configuration trace specification below on the Deployment Manager, at least one Node Agent, and an application server under that Node Agent.
*=info:com.ibm.ws.p2p.*=all:com.ibm.son.*=all
If you have multiple network interfaces or multiple IP Addresses enable son.inetAddressDebug=true as a custom JVM property on each of the same servers above. See this link to set custom Java virtual machine properties - Save and synchronize the change
- Restart Deployment Manager and Node Agents and Application Server
- Allow trace to run at least 10 minutes
-
At the time of the problem, capture additional information:
Use the following command, on the Deployment Manager to capture the state of various Intelligent Management processes:
In the Deployment Manager profile, run the following command:
wsadmin.sh -lang jython -f [WAS_HOME]/bin/dumpIMPState.py --user=[WAS admin user] --password=[WAS admin user password] --auto > IMPState.txt
Where [WAS_HOME] is the installation directory of WebSphere Application Server, [WAS admin user] is the user name of the WebSphere administrative user and [WAS admin user password] is the password of the WAS admin user - Use the collector tool to gather logs from the Deployment Manager, Node Agent, and Server: https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/ttrb_runct.html
Also ensure the IMPState.txt produced in step 6 is included - Upload all the logs to IBM Support
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m0z0000004CniAAE","label":"Intelligent Management-\u003EP2P"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;9.0.0"}]
Was this topic helpful?
Document Information
Modified date:
19 October 2023
UID
ibm16348218