IBM Support

Cannot connect to Gitweb, Gerrit or HP server from an IBM HTTP server

Troubleshooting


Problem

When connecting to Gitweb, Gerrit or an HP server from an IBM HTTP server, a 500 Internal Server Error results.

Symptom

A 500 Internal Server Error results when connecting to Gitweb, Gerrit or HP Server from IHS. In addition, the http_plugin logfile report shows:

1 - ERROR: ws_common: websphereFindTransport: Nosecure transports available.
[18/Sep/2013:17:03:19.96759] 00000ad9 73df2700 - ERROR: ws_common: websphereWriteRequestReadResponse: Failed to find a transport
[18/Sep/2013:17:03:19.96761] 00000ad9 73df2700 - ERROR: ESI: getResponse: failed to get response: rc = 4
[18/Sep/2013:17:03:19.96762] 00000ad9 73df2700 - ERROR: ws_common: websphereHandleRequest: Failed to handle request
2 - ws_common: websphereUriMatch: Fails to find a match sometimes, but does other times.

Cause

If you have secure and insecure transports defined, and a secure transport cannot be obtained due to a system failure, the web server plug-in uses an insecure transport. This is the default behavior. This behavior changed in WebSphere Application Server 8.5.5.

If a system failure occurs when attempting a secure connection, and there is an insecure transport, the web server plug-in does not use that transport.

Environment

CLM 4.0.3
Distributed environment with IHS on Redhat 6.4 with a DB2 10.1.0.2 server.
CLM is deployed on WebSphere Application Server 8.5.5

Diagnosing The Problem

The administrator is made aware of the problem and can fix it using secure connections.

Resolving The Problem

To revert to the previous default behavior, set a custom property by using the administrative console. Select webserver > "webserver_name" > plugin properties > custom properties, and then set UseInsecure to true.

This change in behavior also impacts a plug-in if you only specify an insecure transport. If you want the previous default behavior, which is for the web server plug-in to use the insecure transport, you must add UseInsecure="true" to the global <Config> element in your plug-in

For example:

<Config ASDisableNagle="false" AcceptAllContent="true" AppServerPortPreference="HostHeader" ChunkedResponse="false" FIPSEnable="false" FailoverToNext="false" HTTPMaxHeaders="300" IISDisableNagle="false" IISPluginPriority="High" IgnoreDNSFailures="false" OS400ConvertQueryStringToJobCCSID="false" RefreshInterval="60" ResponseChunkSize="64" SSLConsolidate="true" TrustedProxyEnable="false" VHostMatchingCompat="false" UseInsecure="true">

For more information see Change in behavior when the web server uses an insecure transport in the topic Web server plug-in troubleshooting tips in the WebSphere Application Server information center.

Related Information

[{"Product":{"code":"SSWMXJ","label":"Rational Lifecycle Integration Adapters"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Integrations: IBM","Platform":[{"code":"PF016","label":"Linux"}],"Version":"1.1.0.1","Edition":"Standard","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

More support for:
Rational Lifecycle Integration Adapters

Software version:
1.1.0.1

Operating system(s):
Linux

Document number:
497421

Modified date:
16 June 2018

UID

swg21651261