PI28513: SERVER FAILS TO START DURING INITIALIZING FEDERATED REPOSITORY WITH JAVA.SECURITY.ACCESSCONTROLEXCEPTION.

Fixes are available

APAR status

Closed as program error.

Error description

After applying fixpack 35, server fails to start during
initializing DB repository in federated repository
with java.security.AccessControlException with following stack;
[12/24/14 14:36:13:124 MYT] 00000000 exception     1
com.ibm.ws.wim.dao.AbstractDAO getDirectAccessConnection
com.ibm.websphere.wim.exception.WIMSystemException: CWWIM1999E
An exception occurred during processing: null
at com.ibm.ws.wim.dao.AbstractDAO.getDirectAccessConnection
(Abstrac tDAO.java:354)
>>>
Caused by: java.security.AccessControlException: Access denied
(java.lang.RuntimePermission accessDeclaredMembers)
at java.security.AccessController.throwACE
(AccessController.java:100)
at java.security.AccessController.checkPermission
(AccessController.java:174)
at java.lang.SecurityManager.checkPermission
(SecurityManager.java:5 44)
at java.lang.SecurityManager.checkMemberAccess
(SecurityManager.java:1685)
at java.lang.Class.checkMemberAccess(Class.java:125)
at java.lang.Class.getDeclaredField(Class.java:568)
at com.ibm.db2.jcc.am.ze.run(ze.java:26)
at java.security.AccessController.doPrivileged
(AccessController.java:327)

Local fix

Set JDBC direver path for DB repository(VMM_JDBC_CLASSPATH)
inside WAS_INSTALL_ROOT directory.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server that are NOT using zOS.              *
****************************************************************
* PROBLEM DESCRIPTION: The server is not starting and there    *
*                      are several java 2 security             *
*                      permission issues.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The server is not starting and there
are several java 2 security
permission issues.
The following stack trace should appear:
Caused by: java.security.AccessControlException: Access denied
(java.lang.RuntimePermission accessDeclaredMembers)
at java.security.AccessController.throwACE
(AccessController.java:100)
at java.security.AccessController.checkPermission
(AccessController.java:174)
at java.lang.SecurityManager.checkPermission
(SecurityManager.java:5 44)

Problem conclusion

The problem was that at the time the federated repositories was
being invoked, the JAVA 2 Security had not being initialized.
The code was reviewed and updated in order to make sure that
the JAVA2 Security has been initialized before invoking the
Federated repositories.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.37, 8.0.0.11, 8.5.5.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
PI28513
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-27
Closed date
2015-01-15
Last modified date
2015-02-04

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
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 April 2022

Tips

PI28513: SERVER FAILS TO START DURING INITIALIZING FEDERATED REPOSITORY WITH JAVA.SECURITY.ACCESSCONTROLEXCEPTION.

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?