InfoCenter Home >
8: Problem determination >
8.5: Problem determination quick reference >
8.5.1: Common plug-in problems
8.5.1: Common plug-in problems
Below is a list of common plug-in problems:
- If the native.log file is not created in the product_installation_root
directory, the plug-in might not be communicating with the application server
correctly. The plug-in lines that are added to the Web server's configuration
files need to be checked.
- If the native.log file logs contain the following message:
[Mon Mar 19 17:04:19 2001] ERROR: ws_common: websphereUpdateConfig:
Failed parsing the plug-in configuration file
[Mon Mar 19 17:04:19 2001] ERROR: ws_common: websphereBeginRequest:
Configuration reloading FAILED; using old configuration
Usual symptom is due to bad syntax in the
plugin-cfg.xml file. For example, invalid Virtual Host names and URI group
names. This usually happens when the plugin-cfg.xml file has been edited without
restarting the Web server.
- If the Web server does not start after the plugin-cfg.xml file has
been edited, the syntax in the file might
be incorrect. Similar symptom to number two above, just that in this
case, the Web server must not have been running while the plugin-cfg.xml
file was edited.
- In Advanced Edition, if the user has made changes to through the
administration console the plugin-cfg.xml file might need to be updated through
the GenPluginCfg script, located in the product_installation_root directory.
See the InfoCenter article 6.6.45.6: Regenerating the Web server plug-in configuration for more
information.
- The plugin-cfg.xml file is loaded dynamically in a 60 second cycle.
It might be necessary to restart the Web server in order to see the changes
to the plugin-cfg.xml being invoked immediately.
- If you see the following errors in the plug-in log file:
[Mon Jul 2 12:43:45 2001] 00001589 00000001 - ERROR: ws_common:
websphereGetStream: Failed to connect to application server, OS err=239
[Mon Jul 2 12:43:45 2001] 00001589 00000001 - ERROR: ws_common:
websphereExecute: Failed to create the stream
[Mon Jul 2 12:43:45 2001] 00001589 00000001 - ERROR: ws_server:
ws_server_group: Marking Default Server down
[Mon Jul 2 12:43:45 2001] 00001589 00000001 - ERROR: ws_common:
websphereHandleRequest: Failed to execute the transaction to 'Default Server';
will try another one
[Mon Jul 2 12:43:45 2001] 00001589 00000001 - ERROR: ws_common:
websphereHandleRequest: Failed to find an application server to handle this request
Do the following:
- Make sure the administrative and application servers are started
- Specify the full hostname and domain name for your server
for the transport instead of using localhost
For example:
<Transport Hostname="ihshp3.raleigh.ibm.com" Port="9081" Protocol="http"/>
- Make sure the correct ports are being used
|
|