PK79936: Server fails to discover admin agent

Fixes are available

APAR status

Closed as program error.

Error description

When using an Admin Agent and attempting to start up one of
the servers on a registered node via the administrative
console, the server starts and the status shows as started in
the console, but there is an error message in the
administrative console saying it failed to start and to check
the jvm logs. When looking at the SystemOut.log, you see the
last few entries say:
"Failed to send out the discovery message to the process:
adminagent".

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7.0 users who *
*                  are using admin agents to manage registered *
*                  nodes.                                      *
****************************************************************
* PROBLEM DESCRIPTION: When using an admin agent to manage a   *
*                      registered node, commands cannot be     *
*                      sent to the node from the admin agent   *
*                      if the node's profile name begins       *
*                      with "Default".                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a profile name of a registered node begins with "Default",
the IPC connector code in the admin agent would conclude that
the profile key is null.  This results in the wrong admin
subsystem being used for the connection.  The application
server's log contains "Failed to send out the discovery
message to the process: adminagent".

Problem conclusion

IPC connector code was updated to correctly distinguish
between profiles when one or more have a name beginning with
"Default".

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.3.  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
PK79936
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-02-03
Closed date
2009-02-10
Last modified date
2009-02-10

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

PK79936: Server fails to discover admin agent

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?