PK02109; 5.1.1.4: application servers are not
re-registered
Downloadable files
Abstract
Some application servers are not re-registered after a
nodeagent is stopped and restarted.
Download Description
PK02109 resolves the following problem:
ERROR DESCRIPTION:
When deploying a nodeagent, the following exception is logged:
01/8/05 16:42:58:454 JST 1b70064a ORBRas ecom.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 are not re-registered after a nodeagent is
stopped and restarted.
RECOMMENDATION:
None
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 re-registering 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 targeted for V5.0.2.11, 5.1.1.5, and V6.0.1.2
Recommended Updates for WebSphere Application Server Base and Network
Deployment editions:
General/swg27004980.html
Prerequisites
Please download the UpdateInstaller below to install this fix.