PK75672: IN THE ADMINSTRATIVE SUBSYSTEM INITIALIZATION PROCESSING, THE CONFIGREPOSITORY SHOULD BE THE FIRST INITIALIZATION.

Fixes are available

APAR status

Closed as program error.

Error description

In the Adminstrative subsystem initialization processing, the
ConfigRepository should be the first initialization.

For WebSphere Application Server V7, when you attempt to create
a node or run registerNode.sh you will get NullPointerException
errors such as the following:
---------------------------

[10/21/08 11:14:56:573 BST] 00000018 UserRegistryC E SECJ0281E:
Error creating user registry object. The exception is
java.lang.NullPointerException
at
com.ibm.ws.management.repository.FileRepository.getConfig(FileRe
pository
.java:332)
at
com.jpmc.gti.dcs.ase.ws7.SmallRegistry.initialize(SmallRegistry.
java:278)
-----------------------------

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server        *
*                  version 7.0 users who also utilize the      *
*                  Administrative Agent with a Custom User     *
*                  Registry.                                   *
****************************************************************
* PROBLEM DESCRIPTION: NullPointerException during             *
*                      Administrative Subsystem registration.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If security is enabled, and a Custom User Registry is defined
with code that accesses the Configuration Repository, then a
NullPointerException may be received when the administrative
agent initializes the administrative subsystem as part of node
registration.  This may result in the following sequence of
messages:

ADMU8036I: Registering the node with an AdminAgent.
ADMU8042I: Node has been successfully registered.
ADMU8040I: The administrative agent is initializing the
  administrative subsystem for the registered node.
ADMU8014I: The administrative subsystem for registered node
  has been successfully initialized.

ADMU8041I: The administrative agent is starting the
  administrative subsystem for the registered node.

...

ADMU0113E: Program exiting with error:
  com.ibm.websphere.management.exception.AdminException:
  ADMU8024E: An error occured when invoking startProfile
  operation on AdminAgent mbean; rolling back to original
  configuration., resulting from: java.lang.Exception:
  Access Denied

The above is caused by a combination of incorrect Custom User
Registry code and incorrect Administrative Subsystem code.

The correct way for a Custom User Registry to access the
Configuration repository is by code like:

String configRoot = ProfileUtility.getProfilePath()
   + File.separator + "config";

The Administrative Subsystem incorrectly registers the Discovery
Management Bean before registering the ProfileUtility.
Registration of the Discovery Management Bean may cause Custom
User Registry code to be driven.

Problem conclusion

The code has been modified such that the Administrative
Subsystem registers the ProfileUtility first when the
Administrative Subsystem initializes.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.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
PK75672
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-14
Closed date
2009-02-03
Last modified date
2009-02-03

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
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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK75672: IN THE ADMINSTRATIVE SUBSYSTEM INITIALIZATION PROCESSING, THE CONFIGREPOSITORY SHOULD BE THE FIRST INITIALIZATION.

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?