Troubleshooting
Problem
Collecting data for port management problems with WebSphere Application Server Version 6.x, 7.0, and 8.5. 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.
Port Management specific MustGather information
The following information is needed to better understand why a specific WebSphere Application Server could not properly create unique ports.
Note: The -startingPort option used for the creation scripts (wasprofile, manageprofiles and addNode) does not check the incremental ports used for the servers, so they can conflict with other WebSphere Application Servers.
- Note the server that has the problem and how it was created.
- Enable tracing.
- In the administrative console, expand the Troubleshooting section and click on Logs and Trace.
- Select the link for your server or dmgr where the command is running.
- Select on Change Log Detail Levels. Select the Runtime tab and change the setting to:
*=info:com.ibm.ws.management.configservice.*=all
- Click Apply.
- Run the collector tool on the problem profile.
- Gathering information with the collector tool - V8.5
- Gathering information with the collector tool - V8.0
- Gathering information with the collector tool - V7.0
- Gathering information with the collector tool - V6.1
- Gathering information with the collector tool - V6.0
For a listing of all technotes, downloads, and educational materials specific to port management, search the WebSphere Application Server support site.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21196226