APAR status
Closed as program error.
Error description
After starting nodeagent it displayed as stopped in the
adminconsole, even though node agent is up and running.
Even when the nodeagent was restarted then there was no
discovery of the process.
According to the traces the dmgr process was able to recognize
all the node agents. The delay in the discovery was because the
socket was not open at that time. Later, when the nodeagent was
restarted then there was no discovery signal.
Local fix
A workaround has been provided to the customer:
To get around this problem, the customer may delete the EndPoint
CELL_MULTICAST_DISCOVERY_ADDRESS from dmgr's endpoint list, if
it is not in use and then perform sync.
Problem summary
****************************************************************
* USERS AFFECTED: Users who define the end point *
* CELL_MULTICAST_DISCOVERY_ADDRESS in the *
* dmgr endpoints and try to restart the *
* node-agent while dmgr is running will face *
* this problem i.e nodeagent will be not *
* be displayed as started in the console. *
****************************************************************
* PROBLEM DESCRIPTION: After starting the nodeagent it is *
* displayed as stopped in the console *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem occurs when the end point
CELL_MULTICAST_DISCOVERY_ADDRESS is defined in the dmgr
endpoints. When the you try to restart the nodeagent it is
not displayed as started in the administrative console. The logs
show that nodeagent has started but the administrative console
shows the status as unavailable.
This is because of a code bug in JMXConnectors.java due
to which the nodeagent is not able to send the notification
to dmgr.Discovery of the nodeagent.
When you define the end point (CELL_MULTICAST_DISCOVER ADDRESS)
the code gets activated and the discovery query is discarded.
The bug was the wrong node name in this file.
Problem conclusion
The problem was fixed by making a code change in the file
JMXConnectors.java, the variable nodename was changed
to nextnodeName, so that when the discovery query is
passed the node name is matched and dmgr discovers the
node agent.
The fix for this APAR is currently targeted for inclusion
in 5.02.11 and 5.1.1.5.
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 |
PK00893 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-02-09 |
Closed date |
2005-04-05 |
Last modified date |
2005-04-05 |
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 |
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 |
|