PK91442: NODEAGENT RESTART CAUSES TWO NODEAGENTS TO START UP

Fixes are available

APAR status

Closed as program error.

Error description

Restarting a nodeagent either from the administrative console
or using the wsadmin tool will cause two nodeagents to start in
its place. This poses no real problem functionally as one of
the two nodeagents does start successfully. No errors are
observed from the administrative console. Only in the
nodeagent logs can the problem be observed.

NOTE: To be clear this is not an issue with a "stop" or "start"
explicitly, but a **restart** function of the nodeagent.

Trace example :

This is where the original nodeagent finally stops:
----------------------------------------------------------------
[7/9/09 8:31:01:054 MEST] 0000000e ServerCollabo A   WSVR0024I:
Server
nodeagent stopped
----------------------------------------------------------------

Next two snippets shows 1 of the 2 nodeagents starting with PID
27101:
************ Start Display Current Environment ************
WebSphere Platform 7.0.0.3 [ND 7.0.0.3 cf030911.09] running with
process
name
wps-itssandboxsolaris-cellwas-wps-itssandboxsolaris-de-frawas12
0-node

odeagent and process id 27101
----------------------------------------------------------------

Shows second nodeagent of the 2 nodeagents starting with PID
27081:
************ Start Display Current Environment ************
WebSphere Platform 7.0.0.3 [ND 7.0.0.3 cf030911.09] running with
process
name
wps-itssandboxsolaris-cellwas-wps-itssandboxsolaris-de-frawas12
0-node

odeagent and process id 27081
----------------------------------------------------------------

Below shows the exception where one nodeagent fails to bind
as the other one has taken the assigned ports for the nodeagent
:
----------------------------------------------------------------
[7/9/09 8:31:45:585 MEST] 0000000a ORBRas        E
com.ibm.ws.orbimpl.transport.WSTransport createServerSocket
P=103411:O=0:CT ORBX0390E: Cannot create listener thread.
Exception=[
java.net.BindException: Address already in use - received while
attempting to open server socket on port 31107 ].
[7/9/09 8:31:45:600 MEST] 0000000a WsServerImpl  E   WSVR0009E:
Error
occurred during startup
com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL:
CREATE_LISTENER_FAILED_4  vmcid: 0x49421000  minor code: 56
completed:
No
----------------------------------------------------------------

Eventually you see the one remaining nodeagent completes its
startup successfully and opens for e-business.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server        *
*                  Network Deployment edition v7.0 customers   *
*                  who try to restart nodeagent.               *
****************************************************************
* PROBLEM DESCRIPTION: Restarting nodeagent causes two         *
*                      nodeagents to startup.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Nodeagent SystemOut.log will showed that the nodeagent was
started twice.

Problem conclusion

Removed the extra code that starts the nodeagent.
The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7. 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
PK91442
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-15
Closed date
2009-07-28
Last modified date
2009-07-28

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK91442: NODEAGENT RESTART CAUSES TWO NODEAGENTS TO START UP

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?