APAR status
Closed as program error.
Error description
Compare Inet Address on Quiesce instead of by hostnames
The issue is that host entry for the port
BOOTSTRAP_ADDRESS is FQDN (Fully qualified) and all other
entries are short hostnames including the hostName top entry in
serverindex.xml.
This results in exceptions in stopping RMI Connector during
stopServer. Also delays the process of stopServer.
- <serverEntries xmi:id="ServerEntry_1125487657587"
serverName="perfclone2" serverType="APPLICATION_SERVER">
<deployedApplications>perf-app.ear/deployments/perf-app</deploye
dApplic
tions>
- <specialEndpoints xmi:id="NamedEndPoint_1125487657587"
endPointName="BOOTSTRAP_ADDRESS">
<endPoint xmi:id="EndPoint_1125487657587"
host="DEFX0YBB.xxx.company.net" port="12202" />
</specialEndpoints>
- <specialEndpoints xmi:id="NamedEndPoint_1125487657588"
endPointName="SOAP_CONNECTOR_ADDRESS">
<endPoint xmi:id="EndPoint_1125487657588" host="DEFX0YBB"
port="8884"
/>
</specialEndpoints>
- <specialEndpoints xmi:id="NamedEndPoint_1125487657589"
endPointName="DRS_CLIENT_ADDRESS">
<endPoint xmi:id="EndPoint_1125487657589" host="" port="7876"
/>
</specialEndpoints>
There is an issue in the quisance (stopServer) code with the
handling of the hostnames, if one is short and one is long
(full-qualified), the loopback will not be allowed to occur.
To handle it comparing INET addresses instead of the hostname
should then solve the issue with the long/short name seen above.
Local fix
Keep The BOOTSTRAP_ADDRESS same as other endpoints.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server version 5.0.2 *
* and 5.1.1 users who enter both long and *
* short hostnames for the same host. *
****************************************************************
* PROBLEM DESCRIPTION: The issue is that a host entry for the *
* port BOOTSTRAP_ADDRESS is FQDN (Fully *
* qualified) and all other entries are *
* short hostnames including the hostName *
* top entry in serverindex.xml. This *
* results in exceptions in stopping RMI *
* Connector during stopServer. Also it *
* delays the process of stopServer. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
By comparing on host names, requests that were coming in
locally were thought to be coming in remotely, which caused
this issue.
Problem conclusion
The solution was to compare on INET addresses instead of host
names, which would see it as local regardless of if the host
was long or short.
The fix for this APAR is currently targeted for inclusion
in cumulative fixes 5.02.14 and 5.1.1.8.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK11637 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-09-09 |
Closed date |
2005-10-26 |
Last modified date |
2007-12-04 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK57570
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|