Fixes are available
APAR status
Closed as program error.
Error description
When using the RMI connection to WAS the client connection can fail. To reproduce: 1) Plug a laptop into network and start AST v6.1. 2) Define a new WAS v6.1 server and verify that you can start it and the status appears correctly in the Servers view. 3) Stop the server. 4) Unplug the network connection. 5) Start WAS v6.1 - note that the server status stays as Starting... and will eventually timeout. 6) Switch to SOAP, and it can connect to the server. 7) Switch back to RMI, and the client fails again as the server status goes back to Stopped. 8) Restart AST, and RMI will work again. Tracing activity shows the following exception: com.ibm.ws.orbimpl.transport.WSTCPTransportConnection connect:403 WAS communication ORBRas[default] java.net.NoRouteToHostException: No route to host: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:372) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:2 33)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users using the version 6.1 WebSphere * * Application Server runtime in Rational * * Application Developer v7.0 and WebSphere * * Application Server Toolkit v6.1 * **************************************************************** * PROBLEM DESCRIPTION: The connection to the version6 * * WebSphere Application Server runtime * * is lost when using RMI as the connector * * and the localhost network address * * changes. * **************************************************************** * RECOMMENDATION: * **************************************************************** If a computer is connected to a wired network and a version6 WebSphere Application Server runtime is being used via the RMI connector when the network changes (for example, to a wireless network) then the connection to the server is permanently lost in Rational Application Developer and WebSphere Applicatoin Server Toolkit.
Problem conclusion
The JVM name lookup cache policy for Rational Application Developer and WebSphere Application Server Toolkit has been modified to cache the hostname for only 1 second. Therefore, if the address changes for the local adaptor then the connection will re-establish after 1 second. The fix for this APAR is currently targeted for inclusion in Rational Application Developer v7.0.0.3 and WebSphere Application Server Toolkit v6.1.1.3. Please refer to the Recommended Updates page for WebSphere Application Server Toolkit delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK40728
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-03-07
Closed date
2007-04-05
Last modified date
2007-04-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021