APAR status
Closed as program error.
Error description
When deploying a nodeagent, the following exception is logged:
01/8/05 16:42:58:454 JST 1b70064a ORBRas e
com.ibm.rmi.iiop.Connection doLocateRequestWork:2386
ORB.thread.pool : 1
org.omg.CORBA.OBJECT_NOT_EXIST: BAD_SERVER_ID (1) for
0x4a4d4249000000120dab257131613834306461623235373139616166000000
2400003c49454a5001000b436f6e69536572766572321a57736e4469737
4436f734f626a65637441646170746572574c4d0000000b4f6673734
e6574776f726b minor code:4942FC02 completed: No at
com.ibm.CORBA.iiop.ServerDelegate.locate(ServerDelegate.java:
252)
Local fix
The application server that the nodeagent is not recognizing
will have to be restarted.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users with more *
* than one application server in a node. *
****************************************************************
* PROBLEM DESCRIPTION: Some application servers aren't *
* reregistered after a nodeagent is *
* stopped and restarted. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If an application server is stopped while its nodeagent is
running, the nodeagent can't contact it upon restart. When
this happens the nodeagent will stop processing its "active
server list" and stop reregistering the remaining functional
servers in its list. These "orphaned" servers will no longer
be serviced by the nodeagent and would need to be recycled
in order to operate properly again.
Problem conclusion
Changed the nodeagent code so that it would continue to
process its active server list after encountering a server that
was inactive.
This APAR is targetted for 5.0.2.11, 5.1.1.5, and 6.0.1.2
Recommended Updates for WebSphere Application Server Base and
Network Deployment editions:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
The "local fix" on the submitter page is incorrect. Restart-
ing the nodeagent will have no effect; in fact, this is what
caused the problem in the first place. The application server
is what needs to be restarted.
Also, the "bad server id" message would have been intermittent.
It would only occur when one or more of the servers that
were running at the time that the nodeagent was stopped were
themselves stopped. This would make part of the nodeagent's
active server list invalid. The nodeagent wasn't handling
this properly.
APAR information |
APAR number |
PK02109 |
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-03-07 |
Closed date |
2005-07-08 |
Last modified date |
2005-07-08 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|