PK72258: JAX-WS MANAGED CLIENT INVOCATION WITH JAVA 2 SECURITY ENABLED RESULTS IN FFDC ENTRIES REPORTING ACCESSCONTROLEXCEPTIONS.

Fixes are available

APAR status

Closed as program error.

Error description

When Java 2 Security is enabled, and a user attempts to invoke
a JAX-WS managed client, an error similar to the following is
recorded in FFDC logs:

[9/11/08 21:58:34:184 CDT]     FFDC Exception:java.security.
AccessControlException SourceId:com.ibm.ws.security.core.
SecurityManager ProbeId:180 Reporter:com.ibm.ws.security.
core.SecurityManager@2aa39be4 java.security.AccessControl
Exception : access denied (java.io.FilePermission
/test/wasr64/WebSphere/AppServer/profiles/AppSrvr/config/cells
/ws-sol10-2NoderCell/applications/jaxwsejb3mcservice4.ear/
deployments/jaxwsejb3mcservice4/jaxwsejb3mcclient4.jar/
WEB-INF/ibm-serviceref.xml read)
at java.security.AccessControlContext.checkPermission(Access
ControlContext.java:323) at java.security.AccessController.
checkPermission(AccessController.java:546)
at java.lang.SecurityManager.checkPermission(SecurityManager.
java:532)
at com.ibm.ws.security.core.SecurityManager.checkPermission(
SecurityManager.java:210)
at
java.lang.SecurityManager.checkRead(SecurityManager.java:871)
at java.io.File.exists(File.java:731)
at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.
LoadStrategyImpl.containsUsingLooseArchive(LoadStrategyImpl.
java:205)
at org.eclipse.jst.j2ee.commonarchivecore.internal.
strategy.LoadStrategyImpl.contains(LoadStrategyImpl.java:187)
at com.ibm.ws.websvcs.annotations.injection.ServiceRefObject
Factory.getServiceRefBindingInfo(ServiceRefObjectFactory.java
:432)

The error does not cause the client invocation to fail, but
it is reported in the FFDC logs.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  version 7.0 utilizing JAX-WS managed        *
*                  client capabilities.                        *
****************************************************************
* PROBLEM DESCRIPTION: During the invocation of a managed      *
*                      JAX-WS client, FFDC entries are         *
*                      logged for Java 2 Security violations.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The invocation of a JAX-WS managed client results in FFDC
entries for Java 2 Security violations. The FFDC entries do
not cause the invocation to fail, but appear in the logs for
each managed client invocation.

Problem conclusion

The Java 2 Security violation has been fixed, and the FFDC
entries no longer appear.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK72258
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-09-16
Closed date
2008-10-17
Last modified date
2008-10-17

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

Document Information

Modified date:
23 October 2021

Tips

PK72258: JAX-WS MANAGED CLIENT INVOCATION WITH JAVA 2 SECURITY ENABLED RESULTS IN FFDC ENTRIES REPORTING ACCESSCONTROLEXCEPTIONS.

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?