PK75424: ADDRESSES PROBLEMS DISCOVERED WITH THE ADMIN AGENT DURING INTERNAL TESTING.

Fixes are available

APAR status

Closed as program error.

Error description

This addresses problems discovered with the Administrative
Agent in the following areas:
1. Registration failures, various problems
2. RMI / JSR160RMI connector problems
3. Error reports in System.out and FFDCs

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server V7.0  *
*                  Administrative Agent.                       *
****************************************************************
* PROBLEM DESCRIPTION: This addresses problems discovered      *
*                      with the Administrative                 *
*                      Agent in the following areas:           *
*                      1. Registration failures, various       *
*                      problems                                *
*                      2. RMI / JSR160RMI connector problems   *
*                      3. Error reports in System.out and      *
*                      FFDCs                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1. registerNode fails when kerberos is set as the active
authentication mechanism on zOS:
ADMU0113E: Program exiting with error:

com.ibm.websphere.management.exception.AdminException:
ADMU8023E: An error occured when invoking initializeProfile
operation on AdminAgent mbean; rolling back to
original configuration., resulting from: [SOAPException:
faultCode=SOAP-ENV:Client; msg=Read timed out;
targetException=java.net.SocketTimeoutException: Read timed
out]


2. Can not connect to Admin subsystem with JSR160RMI
connector:
WASX7023E: Error creating "JSR160RMI" connection to host
"localhost"; exception information:
com.ibm.websphere.management.exception.ConnectorNotAvailableExce
ption: java.io.IOException: Connector not available: A
communication failure occurred while attempting to obtain an
initial context with the provider URL:
"corbaloc:iiop:localhost:9813/WsnAdminNameService".


3. registerNode command hangs on Linux when the X11 DISPLAY
variable is not defined.  This is due to the GUI "signer
exchange" prompt being instantiated (it throws due to a
"headless" environment, but does not terminate the process),
and then not receiving a response from the user.

4. The Administrative Agent gets into a state where the RMI
connector does not not start for the subsystem, due to
permission issue ; OR the RMI connector does start, and
authentication to the subsystem seems to not work. Normal
credentials do not work.

5. Trying to register the Dmgr to the Administrative Agent:
ADMU0113E:
Program exiting with error:
com.ibm.websphere.management.exception.AdminException:
ADMU8049E: An error occured when adminagent tried to exchange
signers with the node., resulting from:
com.ibm.websphere.management.cmdframework.CommandValidationExcep
tion:
 A signer certificate for the base application server node's
RSA Token Framework could not be found.

6 . From SystemOut.log:
[10/28/08 7:23:38:484 CDT] 0000001b SecurityConfi E   Unable
to release caches during AdminAgent profile refresh.

7. Node registration to an Administrative Agent fails when the
key store passwords for the profiles are different.

8.When you register a Base application server to an
Administrative Agent that has a different realm than the
Administrative Agent, after registration is complete you have
to restart the Adminagent server. The admin-authz.xml does not
seem to be refreshed.

Problem conclusion

1. Resolved a circular initialization loop which only occurs
on zOS when kerberos is the active authentication mechanism,
and LDAP is the active user registry.

2. Systems management and security code was changed to create
admin connector IORs for RMI and JSR160RMI with the proper
subsystem thread context.

3. This problem occurs when you try registerNode with a Base
application server that already started and failed. Changed
code to detect this case.

4. During registration, the primaryAdminID for the profile is
entered into the naming-auth.xml, adding explicit permission
for CosNamingWrite. However, after a userRegistry change is
made, there is no new entry in naming-authz.xml, so authz
fails. Changed code to update the naming-authz.xml on registry
change.

5. Registering a Dmgr to an Administrative Agent was never
supported, a more clear error message is now thrown:
ADMU0111E: Program exiting with error:
com.ibm.websphere.management.exception.AdminException:
ADMU8019E: Error trying to register a non supporting profile

6. Modified ordering of cache clean-up, resolving this issue.

7. Administrative Agent was using it's keystore password for
the registered profile. Changed internal code to access the
configuration of the registered profile.

8. Code was changed to reload admin-authz.xml when server id's
are exchanged.

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
PK75424
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-11
Closed date
2009-02-13
Last modified date
2009-02-13

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK79901

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

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:
23 October 2021

Tips

PK75424: ADDRESSES PROBLEMS DISCOVERED WITH THE ADMIN AGENT DURING INTERNAL TESTING.

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?