`

websphereFindTransport: Nosecure transports available

 
阅读更多

Case:

今天在 setup HTTPS 过程中,碰到这个Error. 

问题就出在WAS8.5.5跟之前版本的行为不一样。

 

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.

http://www-01.ibm.com/support/docview.wss?uid=swg21651261

----------------------------------------------------------------------

[20/Jan/2014:09:10:26.77103] 000025f5 a2b9d700 - ERROR: ws_common: websphereFindTransport: Nosecure transports available

[20/Jan/2014:09:10:26.77109] 000025f5 a2b9d700 - ERROR: ws_common: websphereWriteRequestReadResponse: Failed to find a transport

[20/Jan/2014:09:10:26.77111] 000025f5 a2b9d700 - ERROR: ESI: getResponse: failed to get response: rc = 4

[20/Jan/2014:09:10:26.77113] 000025f5 a2b9d700 - ERROR: ws_common: websphereHandleRequest: Failed to handle request

----------------------------------------------------------------------

 

Solution 1:

在 plugin-cfg.xml 中 Change 

UseInsecure="false"

to 

UseInsecure="true"

 

Solution 2 (No tested):

直接删掉下面一段:

         <Transport Hostname="tkdp2rbpwas17.was.hk.hsbc" Port="18129" Protocol="https">

            <Property Name="keyring" Value="/opt/IBM/WebSphere/Plugins/etc/plugin-key.kdb"/>

            <Property Name="stashfile" Value="/opt/IBM/WebSphere/Plugins/etc/plugin-key.sth"/>

         </Transport>

分享到:
评论

相关推荐

Global site tag (gtag.js) - Google Analytics