PM64165: MBEANDISCOVERYHELPER USES EMF GETSTRING INCORRECTLY

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2

APAR status

• Closed as program error.

Error description

• The following error is caused by incorrect usage of the EMF
  getString() method.
  
  [9/20/11 13:06:19:326 EDT]     FFDC
  Exception:java.lang.IllegalArgumentException
  SourceId:com.ibm.ws.management.discovery.Endpoint.initialize
  ProbeId:101
  Reporter:com.ibm.ws.management.discovery.Endpoint@2081061
  java.lang.IllegalArgumentException: invalid default value:
  used=, expected=null,
  feature=org.eclipse.emf.ecore.impl.EAttributeImpl@210d31c
  (name: serverName) (ordered: true, unique: true, lowerBound:
  0, upperBound: 1) (changeable: true, volatile: false,
  transient: false, defaultValueLiteral: null, unsettable:
  false, derived: false) (iD: false)
  at
  com.ibm.ws.runtime.config.EMFConfigObjectImpl.checkGetAttribute(
  EMFConfigObjectImpl.java:369)
  at
  com.ibm.ws.runtime.config.EMFConfigObjectImpl.getString(EMFConfi
  gObjectImpl.java:517)
  at
  com.ibm.ws.runtime.config.AbstractConfigObject.getString(Abstrac
  tConfigObject.java:36)
  at
  com.ibm.ws.management.discovery.transport.MBeanDiscoveryHelper.<
  init>(MBeanDiscoveryHelper.java:320)
  ...
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: MBeanDiscoveryHelper uses EMF APIs      *
  *                      incorrectly                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Several places in the admin runtime have used the runtime
  config service (RCS) APIs incorrectly and caused an
  IllegalArgumentException and other exceptions to appear in the
  ffdc log.
  [9/20/11 13:06:19:326 EDT]     FFDC
  Exception:java.lang.IllegalArgumentException
  SourceId:com.ibm.ws.management.discovery.Endpoint.initialize
  ProbeId:101
  Reporter:com.ibm.ws.management.discovery.Endpoint@208
  1061
  java.lang.IllegalArgumentException: invalid default value:
  used=, expected=null,
  feature=org.eclipse.emf.ecore.impl.EAttributeImpl@210d31c
  (name: serverName) (ordered: true, unique: true, lowerBound:
  0, upperBound: 1) (changeable: true, volatile: false,
  transient: false, defaultValueLiteral: null, unsettable:
  false, derived: false) (iD: false)
  at
  com.ibm.ws.runtime.config.EMFConfigObjectImpl.checkGetAttribute(
  EMFConfigObjectImpl.java:369)
  at
  com.ibm.ws.runtime.config.EMFConfigObjectImpl.getString(EMFConfi
  gObjectImpl.java:517)
  at
  com.ibm.ws.runtime.config.AbstractConfigObject.getString(Abstrac
  tConfigObject.java:36)
  at
  com.ibm.ws.management.discovery.transport.MBeanDiscoveryHelper.<
  init>(MBeanDiscoveryHelper.java:320)
  

Problem conclusion

• The fix corrected several admin runtime code bugs to ensure
  proper usage of the runtime config service (RCS) methods to
  avoid the exceptions.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.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 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

• R850 PSY

     UP