158 lines
8.6 KiB
HTML
158 lines
8.6 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Troubleshoot: HTTP plug-in component</title>
|
||
|
|
</head>
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="trbplugincomp"></a>Troubleshoot: HTTP plug-in component</h3>
|
||
|
|
|
||
|
|
<p>If you are having problems with the HTTP plug-in component - the component
|
||
|
|
which sends requests from your HTTP server, such as IBM HTTP Server, Apache,
|
||
|
|
Domino, iPlanet, or IIS, to the WebSphere Application Server, perform the following steps:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Review the HTTP plugin log file. It is located at
|
||
|
|
<tt>/QIBM/UserData/WebAS51/<em>edition</em>/<em>instance</em>/logs/http_plugin.log</tt>
|
||
|
|
Look up any error or warning messages in the message table.</li>
|
||
|
|
<li>Review your HTTP server error and access logs to see if the HTTP server
|
||
|
|
is having a problem:
|
||
|
|
<ul>
|
||
|
|
<li>IBM HTTP Server and Apache: <tt>access.log</tt> and <tt>error.log</tt>.</li>
|
||
|
|
<li>Domino web server: <tt>httpd-log</tt> and <tt>httpd-error</tt>.</li>
|
||
|
|
<li>iPlanet: <tt>access</tt> and <tt>error</tt>.</li>
|
||
|
|
<li>IIS: <tt><em>timedatestamp</em>.log</tt>.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>If the log files do not reveal the cause of the problem, follow the plug-in problem determination steps:</p>
|
||
|
|
|
||
|
|
<p><b>Plug-in Problem Determination Steps</b></p>
|
||
|
|
|
||
|
|
<p>The plug-in provides readable tracing that can be beneficial for problem analysis. Set the <strong>LogLevel</strong> attribute in the
|
||
|
|
<tt>config/plugin-cfg.xml</tt> file to <strong>Trace</strong>. (For the default application server, you can find this file in the /QIBM/UserData/WebAS51/Base/default/config/cells directory.) From there, you can follow the request processing to see what is going wrong. The process is as follows:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li>The plug-in gets a request.</li>
|
||
|
|
<li>The plug-in checks the routes defined in the <tt>plugin-cfg.xml</tt> file.</li>
|
||
|
|
<li>It finds the server group.</li>
|
||
|
|
<li>It finds the server.</li>
|
||
|
|
<li>It picks the transport protocol, usually HTTP.</li>
|
||
|
|
<li>It sends the request.</li>
|
||
|
|
<li>It reads the response.</li>
|
||
|
|
<li>It writes it back to the client.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p>You can see the process by reading through the trace for
|
||
|
|
a single request:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Determine if the plug-in has successfully loaded into the HTTP server.
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p>Check to make sure the <tt>http_plugin.log</tt> file has been created.</p></li>
|
||
|
|
<li><p>If the http_plugin.log file exists, open the file and check if any error
|
||
|
|
messages indicate some type of failure that took place during plug-in initialization. If no errors are found, check for the following stanza, which indicates that the plug-in started normally. Make sure that the timestamps for the messages correspond to the time
|
||
|
|
you started the Web server:</p>
|
||
|
|
<pre>
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: ---System Information---
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: Bld date: Jul 3 2002, 15:35:09
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: Web server: IIS
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: Hostname = SWEETTJ05
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: OS version 4.0, build 1381,
|
||
|
|
'Service Pack 6'
|
||
|
|
[Thu Jul 11 10:59:15 2002] 0000009e 000000b1 - PLUGIN: -------------------------
|
||
|
|
</pre>
|
||
|
|
</li>
|
||
|
|
<li><p>A common errors is <strong>ws_transport: transportInitializeSecurity: Keyring wasn't set</strong>. The HTTPS transport defined in the configuration file was prematurely terminated and did not contain the Property definitions for the keyring and
|
||
|
|
stashfile. Check your XML syntax for the line number given in the error messages
|
||
|
|
that follow this one to make sure the Transport element contains definitions
|
||
|
|
for the keyring and stashfiles before it is terminated.</p>
|
||
|
|
</li>
|
||
|
|
<li><p>If the <tt>http_plugin.log</tt> file is not created, check the Web server error
|
||
|
|
log to see if any plug-in related error messages have been logged that
|
||
|
|
indicate why the plug-in failed to load. Typical causes of this can include
|
||
|
|
failing to correctly configure the plug-in with the Web server environment. See <a href="../admin/admplugin.htm">Configure Web server plug-ins</a> for more information.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</li>
|
||
|
|
<li><p>Determine whether there are network connection problems with the plug-in
|
||
|
|
and the various application servers defined in the configuration. Typically
|
||
|
|
you will see the following message when this is the case:</p>
|
||
|
|
<p><strong>ws_common: websphereGetStream: Failed to connect to app server, OS err=%d</strong></p>
|
||
|
|
<p>Where %d is an OS specific error code related to why the connect() call failed. This can happen for a variety of reasons.</p>
|
||
|
|
<ul>
|
||
|
|
<li>Ping the machines to make sure they are properly connected to the network.
|
||
|
|
If the machines can't be pinged then there is no way the plug-in will be
|
||
|
|
able to contact them. Possible reasons for this include:
|
||
|
|
<ul>
|
||
|
|
<li>Firewall policies limiting the traffic from the plug-in to the app server.</li>
|
||
|
|
<li>The machines are not on the same network.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>If you are able to ping the machines then the likely cause of the problem
|
||
|
|
is that the port is not active. This could be because the application server
|
||
|
|
or cluster has not been started or the application server has gone down for
|
||
|
|
some reason. You can test this by hand by trying to telnet into the port
|
||
|
|
that the connect is failing on. If you cannot telnet into the port the application
|
||
|
|
server is not up and that problem needs to be resolved before the plug-in
|
||
|
|
will be able to connect successfully.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</li>
|
||
|
|
<li>Determine whether other activity on the machines where the servers are
|
||
|
|
installed is impairing the server's ability to service a request. Check the
|
||
|
|
processor utilization as measured by the task manager, processor ID, or some
|
||
|
|
other outside tool to see if it:<ul>
|
||
|
|
<li>Is not what was expected.</li>
|
||
|
|
<li>Is erratic rather than a constant.</li>
|
||
|
|
<li>Shows that a newly added member of the cluster is not being utilized.</li>
|
||
|
|
<li>Shows that a failing member that has been fixed is not being utilized.</li>
|
||
|
|
</ul></li>
|
||
|
|
<li>Check the administrative console
|
||
|
|
to ensure that the application servers are started. View the administrative
|
||
|
|
console for error messages or look in the <a href="trbjvmintro.htm">JVM log file</a> for more information.</li>
|
||
|
|
|
||
|
|
<li> In the administrative console, select the problem application server,
|
||
|
|
and view the installed applications to verify that they are started.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>If none of these steps solves the problem:</p>
|
||
|
|
<ul>
|
||
|
|
<li>For specific problems that can cause web pages and their contents not
|
||
|
|
to display, see <a href="trbpgdisplayprob2.htm">Troubleshoot: Starting an
|
||
|
|
application</a>.</li>
|
||
|
|
<li>If you do not see a problem that
|
||
|
|
resembles yours, or if the information provided does not solve your problem, <a href="../intro/support.htm">Get support for WebSphere Application Server for iSeries</a> in the <em>Overview</em> topic for more information.</li>
|
||
|
|
</ul>
|
||
|
|
<p>For current information available from IBM Support on known problems and
|
||
|
|
their resolutions, see the following Web sites:</p>
|
||
|
|
<ul>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPBD">HTTP transport</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCC2GP">HTTP plugin</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPDA">HTTP plugin remote install</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>IBM Support has documents that can save you time gathering information
|
||
|
|
needed to resolve this problem. Before you open a problem report, see the following Web sites:</p>
|
||
|
|
<ul>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPBD&q=mustgather">HTTP transport</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCC2GP&q=mustgather">HTTP plugin</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
<li><a target="_blank" href="http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPDA&q=mustgather">HTTP plugin remote install</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center" border="0">
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|