ConfigEngine script 'cluster-node-config-post-federation' fails with 'Error parsing HTTP status line ""' exceptions

Technote (troubleshooting)


Problem

When executing a ConfigEngine script that must connect to your deployment manager to make changes, such as 'cluster-node-config-post-federation' or 'cluster-node-config-cluster-setup', the script fails with the exception

'Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line
"": java.util.NoSuchElementException

Symptom

The full exception from the ConfigEngine failure is the following:

============================
[wplc-create-variable] Caused by: [SOAPException:
faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line
"": java.util.NoSuchElementException;
targetException=java.lang.IllegalArgumentException: Error parsing HTTP
status line "": java.util.NoSuchElementException]
[wplc-create-variable]  at
org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source)
[wplc-create-variable]  at org.apache.soap.rpc.Call.invoke(Unknown
Source)

============================

If you execute the script several times may continue to fail at different points with slightly different exceptions:

============================
[wplc-create-variable] Caused by: [SOAPException:
faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type
"text/html", must be: "text/xml". Response was:
[wplc-create-variable] <HTML><TITLE>408 - Request
Timeout</TITLE><BODY><h1>408 Connection timed out
while reading request</h1></BODY></HTML>
[wplc-create-variable] ]

============================

Further, if you examine the NodeAgent SystemOut.log from the node where this is failing, you discover that is constantly discovering the DMGR process even though the DMGR has not been restarted:

============================
[6/15/09 17:00:48:187 EDT] 0000002c DiscoveryMBea I   ADMD0023I: The
system discovered process (name: dmgr, type: DeploymentManager, pid:
4896)

============================

Likewise, if you examine the DMGR SystemOut.log files from the same timeframe, you discover that the nodeagent is constantly being discovered even though it too is not being restarted.



Cause

All of these different exceptions indicate there are network issues between the node and the DMGR. Communication is being lost randomly.

Resolving the problem

Unfortunately it is not easy to determine where the problem lies. It could be hardware or it could be in your network. The recommended option is to work with your network administrators, if available, to troubleshoot and any network failures.


Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal
Installation & Configuration

Software version:

6.1

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Enable, Extend

Reference #:

1393929

Modified date:

2009-09-22

Translate my page

Machine Translation

Content navigation