Troubleshooting
Problem
To regenerate the plug-in configuration, you can either click Servers > Web Servers in the administrative console, select a Web server, and then click "Generate plug-in", or you can issue the following command: GenPluginCfg.sh|bat. If you have a problem with plug-in regeneration, gathering this information before to calling IBM® support helps familiarize you with the troubleshooting process and save you time.
Resolving The Problem
If specific components involved in the problem are unknown, click: MustGather: Read first for all WebSphere Application Server.
Plug-in generation-specific MustGather information
Collect the following information and logs:
- General information:
- Network topology
- Operating System
- Versions of products in question
- WebSphere Application Server topology
- Based on your environment, run the following command from the install_root/bin directory and collect the resulting plug-in regeneration log file (plugin-cfg.log):
- For V8.5 or higher, with Intelligent Management enabled:
- Intelligent Management generation script httpPluginManagement.py
- For V8.0, 8.5.5 with on-demand configuration or on-demand routing:
- Intelligent Management generation script httpPluginManagement.py, wsadmin or GUI.
- To generate a plug-in configuration for all of the clusters in a cell:
GenPluginCfg -cell.name <NetworkDeploymentCell> -debug yes
- To generate a plug-in configuration for a single server:
GenPluginCfg -cell.name <BaseApplicationServerCell> -node.name <appServerNode> -server.name <appServerName> -debug yes
- To generate a plug-in configuration file for a Web server:
GenPluginCfg -cell.name <BaseApplicationServerCell> -node.name <webserverNode> -webserver.name <webserverName> -debug yes
For topology centric (based on applications that are deployed on a node or cluster or server), the following is the location of the resulting log file:
PROFILE_HOME\logs
For application centric (based on applications that are deployed on to a web server), the following is the location of the resulting log file:
PROFILE_HOME\logs\%WEBSERVER_NAME%
Note: Regenerating the plug-in configuration can overwrite manual configuration changes that you might want to preserve. Understand the implications of this task as described in Communicating with Web servers found in the online Information Center.
- Traces:
- On the Application Server, set the following trace string
- For WebSphere Application Server V8.5 and V9.0
- In the administrative console, expand the "Troubleshooting" section and click "Logs and Trace"
- Select your server.
- Click "Change Log Detail Levels".
- In "Trace Specification", enter the following trace string: *=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all: HTTPChannel=all:com.ibm.websphere.plugincfg.*=all
- Note: Generation issues are often not a plug-in problem and depending on the nature of the problem, other trace specs can be added.
- Missing URI or performance delays *=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all MustGather: Web Services engine and tooling problems for WebSphere Application Server
- Propagation issue: com.ibm.websphere.management.filetransfer.*=all:com.ibm.ws.management.filetransfer.*=all:com.ibm.ws.management.fileservice.*=all TroubleShooting: plug-in generation and propagation for V6.1, V7, V8 and V8.5
- Osgi Applications issue: Aries.*=all:org.apache.aries.*=all MustGather: OSGi applications running in WebSphere Application Server
- Tracing for GenPluginCfg: a property needs to be added to the GenPluginCfg script and tracing property files needs to be created. Detailed instructions on enabling trace are available: "Setting up a trace in WebSphere Application Server".
- Note: Generation issues are often not a plug-in problem and depending on the nature of the problem, other trace specs can be added.
- For "Trace Output", choose File and type a filename.
- Click "Apply" and save your configuration.
- For WebSphere Application Server V7.0 and V8.0
- In the administrative console, expand the "Troubleshooting" section and click "Logs and Trace"
- Select your server.
- Click "Change Log Detail Levels".
- In "Trace Specification", enter the following trace string:*=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:com.ibm.websphere.plugincfg.*=all Note: There must NOT be any spaces or '.' between webcontainer and '*' for the trace strings.
- Note: Generation issues are often not a plug-in problem and depending on the nature of the problem, other trace specs can be added.
- Missing URI or performance delays *=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all MustGather: Web Services engine and tooling problems for WebSphere Application Server
- Propagation issue: com.ibm.websphere.management.filetransfer.*=all:com.ibm.ws.management.filetransfer.*=all:com.ibm.ws.management.fileservice.*=all TroubleShooting: plug-in generation and propagation for V6.1, V7, V8 and V8.5
- Osgi Applications issue: Aries.*=all:org.apache.aries.*=all MustGather: OSGi applications running in WebSphere Application Server
- Tracing for GenPluginCfg: a property needs to be added to the GenPluginCfg script and tracing property files needs to be created. For detailed instructions on enabling trace, see Setting up a trace in WebSphere Application Server.
- Note: Generation issues are often not a plug-in problem and depending on the nature of the problem, other trace specs can be added.
- For Trace Output, choose File and type a filename.
- Click Apply and save your configuration.
- For WebSphere Application Server V8.5 and V9.0
- Restart IBM HTTP Server and WebSphere Application Server.
- Re-create the failure.
- On the Application Server, set the following trace string
- Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the plug-in component, search the WebSphere Application Server support site.
Related Information
Was this topic helpful?
Document Information
Modified date:
10 February 2020
UID
swg21199421