APAR status
Closed as program error.
Error description
Access Denied exception running XIO and Security enabled on WAS85_WXS_Clients
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere eXtreme Scale Client * * V8.6.0 * * who are running the client in a Java * * virtual * * machine(JVM) that has an active security * * manager. * **************************************************************** * PROBLEM DESCRIPTION: When V8.6 clients * * run with Java security manager, * * all access fails with an * * AccessControlException exception. * **************************************************************** * RECOMMENDATION: * **************************************************************** You can run WebSphere eXtreme Scale Client V8.6.0 with a security manager. When you are running the client in a stand- alone JVM, enable the security manager with the - Djava.security.manager argument on the start server command. When you are running the client in a WebSphere Application Server process, enable the Java security manager by turning on Java 2 security for the WebSphere Application Server environment. When you have the security manager configured, all access from the client to the catalog and container servers fail. The client logs contain the following exception: java.security.AccessControlException: Access denied (java.lang.RuntimePermission modifyThreadGroup) ‚ ‚ ‚ at java.security.AccessController.checkPermission(AccessController. java:132) ‚ ‚ ‚ at java.lang.SecurityManager.checkPermission(SecurityManager.java:5 44) ‚ ‚ ‚ at com.ibm.ws.security.core.SecurityManager.checkPermission(Securit yManager.java:208) ‚ ‚ ‚ at com.ibm.ws.security.core.SecurityManager.checkAccess(SecurityMan ager.java:407) ‚ ‚ ‚ at java.lang.ThreadGroup.checkAccess(ThreadGroup.java:226) ‚ ‚ ‚ at java.lang.Thread.initialize(Thread.java:346) ‚ ‚ ‚ at java.lang.Thread.<init>(Thread.java:281) ‚ ‚ ‚ at java.lang.Thread.<init>(Thread.java:239) ‚ ‚ ‚ at java.util.concurrent.Executors$DefaultThreadFactory.newThread(Ex ecutors.java:553) ‚ ‚ ‚ at java.util.concurrent.ThreadPoolExecutor.addThread(ThreadPoolExec utor.java:683) ‚ ‚ ‚ at java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(T hreadPoolExecutor.java:708) ‚ ‚ ‚ at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecut or.java:663) ‚ ‚ ‚ at java.util.concurrent.AbstractExecutorService.submit(AbstractExec utorService.java:103) ‚ ‚ ‚ at com.ibm.ws.objectgrid.naming.LocationServiceFactory.getTransport (LocationServiceFactory.java:1194)
Problem conclusion
This problem has been corrected. Upgrade the client to a recent fix pack level to resolve the problem.
Temporary fix
Comments
APAR Information
APAR number
PM79165
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-13
Closed date
2013-06-20
Last modified date
2013-06-20
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
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
20 June 2013