JR50952: GETFAILEDEVENTPARAMETERS FAILED EVENT MANAGER MBEAN CALL FAILS FOR NONE PRIMITIVE TYPES

8.5.0.1-WS-BPM-IFJR50952
Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• The GETFAILEDEVENTPARAMETERS failed event manager MBean API
  might fail when it tries to get failed event parameters for none
  primitive types in a wsadmin environment. You see an error
  similar to the following error on the wsadmin client side:
  
  WASX7017E: Exception received while running file "<your script
  name>"; exception information:
  com.ibm.bsf.BSFException: exception from Jython: Traceback
  (innermost last):  File "<string>", line <line number>, in ?
  com.ibm.wbiserver.manualrecovery.exceptions.
  FailedEventRuntimeException:
  SCA Internal: SCA container initialization failed
  (Container.getComponent() == null) with context classloader
  java.net.URLClassLoader@5818af86
   at com.ibm.wbiserver.manualrecovery.
     FailedEventWithParametersImpl.restoreParameters
     (FailedEventWithParametersImpl.java:454)
   at com.ibm.wbiserver.manualrecovery.
     FailedEventWithParametersImpl.restoreParameters
     (FailedEventWithParametersImpl.java:425)
   at com.ibm.wbiserver.manualrecovery.
     FailedEventWithParametersImpl.getFailedEventParameters
     (FailedEventWithParametersImpl.java:158)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke
     (NativeMethodAccessorImpl.java:60)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke
     (DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   at org.python.core.PyReflectedFunction.__call__
     (PyReflectedFunction.java)
  

Local fix

Problem summary

• The issue occurs when the failed event manager tries to
  transform application-specific messages, such as failure data,
  from an XML representation into business objects. The admin
  command runs out of the scope of a business application;
  therefore, it is not possible to initialize an SCA container.
  Initializing an SCA container is, however, required to call the
  serialization service.
  

Problem conclusion

• A fix is available for IBM BPM V8.0.1.2 that omits the
  transformation from XML to a business object when the SCA
  environment cannot be established.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR50952:
  
  1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
  
  2. Select APAR or SPR, enter JR50952, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

• Not applicable
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R801 PSY

     UP