PK58239: FP61013XP PSY VCT:PMIUNIT TEST CASES FAIL DUE TO JMX ERROR.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• FP61013XP PSY VCT:PMIUNIT test cases fail due to JMX error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: websphere Application Server vers 6.1 users  *
  *                 who uses Performance Monitoring              *
  *                 infrastucture.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: JMX Exceptions in SystemOut.log when    *
  *                      Performance monitoring infrastucture    *
  *                      is used.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Following exceptions are seen in the Systemout.log of
  Application Server when enabling performace monitoring
  infrastucture.
  
   [10/17/07 3:30:22:962 GMT+00:00] 00000023 SecurityManag W
  BBOO0221W: SECJ6206W: The current Java 2 Security policy
  report a potential violation of a Java 2 Security Permission.
  Stack Trace:
  Begin SecurityException
  java.security.AccessControlException: Access denied
  (java.lang.RuntimePermission createClassLoader)
    at java.lang.SecurityManager.checkPermission
       (SecurityManager.java:548)
    at com.ibm.ws.security.core.SecurityManager.checkPermission
       (SecurityManager.java:189)
    at java.lang.SecurityManager.checkCreateClassLoader
       (SecurityManager.java:610)
    at java.lang.ClassLoader.<init>(ClassLoader.java:134)
    at com.ibm.ws.management.connector.interop.JMXClassLoader.
       <init>(JMXClassLoader.java:67)
    at com.ibm.ws.management.connector.soap.GenericSerializer.
       loadJMXClassLoader(GenericSerializer.java:269)
    at com.ibm.ws.management.connector.soap.GenericSerializer.
       <clinit>(GenericSerializer.java:253)
    at java.lang.J9VMInternals.initializeImpl(Native Method)
    at java.lang.J9VMInternals.initialize(J9VMInternals.java:194)
    at com.ibm.ws.management.connector.soap.AdminServiceSMR.
       <clinit>(AdminServiceSMR.java:51)
  
  This happens as the caller is not inside doPrivs block.
  

Problem conclusion

• Added the caller into doPriv block.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.17.
  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 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP