JR47084: QUERY RELATIONSHIPS FAILS WITH ERROR CWMAM0003E

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 1 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When trying to query some relationships using the
  relationship
  manager in the WAS Console, there might be the following
  exception seen
  --
  CWMAM0003E: An exception was received while trying to invoke the
  Relationship services Mbean. (Application directory for the
  relationship is null.)
  
  There will be exceptions in the FFDC logs:
  [6/19/13 9:29:25:238 CEST]     FFDC
  Exception:com.ibm.wbiserver.relationshipservice.exceptions.Relat
  ionshipS
  erviceException
  SourceId:com.ibm.wbiserver.relationshipservice.management.Relati
  onshipMa
  nagerMBeanImpl.performRangeQuery
  ProbeId:490
  com.ibm.wbiserver.relationshipservice.exceptions.RelationshipSer
  viceExce
  ption:
  Application directory for the relationship is null.
   at
   com.ibm.wbiserver.relationshipservice.management.RelationshipMa
  nagerImp
  l.setALContext(RelationshipManagerImpl.java:1370)
   at
   com.ibm.wbiserver.relationshipservice.management.ClientQueryRes
  ultSetIm
  pl.initialize(ClientQueryResultSetImpl.java:370)
   at
   com.ibm.wbiserver.relationshipservice.management.ClientQueryRes
  ultSetIm
  pl.<init>(ClientQueryResultSetImpl.java:114)
   at
   com.ibm.wbiserver.relationshipservice.management.RelationshipMa
  nagerMBe
  anImpl.performRangeQuery(RelationshipManagerMBeanImpl.java:466)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at
   sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso
  rImpl.ja
  va:60)
   at
   sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho
  dAccesso
  rImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:49)
   at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
   at
   sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho
  dAccesso
  rImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
   at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:256)
   at
   javax.management.modelmbean.RequiredModelMBean.invokeMethod(Req
  uiredMod
  elMBean.java:1085)
   at
   javax.management.modelmbean.RequiredModelMBean.invoke(RequiredM
  odelMBea
  n.java:966)
   at
   com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(De
  faultMBe
  anServerInterceptor.java:848)
   at
   com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.ja
  va:773)
   at
   com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.j
  ava:1335
  )
   at
   com.ibm.ws.security.util.AccessController.doPrivileged(AccessCo
  ntroller
  .java:118)
   at
   com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.
  java:122
  8)
   at
   com.ibm.ws.management.connector.AdminServiceDelegator.invoke(Ad
  minServi
  ceDelegator.java:181)
   at
   com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter
  .java:24
  7)
   at
   com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doW
  ork(IPCC
  onnectorInboundLink.java:360)
   at
   com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPC
  Connecto
  rReadCallback.complete(IPCConnectorInboundLink.java:602)
   at
   com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadComple
  tedCallb
  ack.complete(SSLReadServiceContext.java:1784)
   at
   com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCom
  pleted(A
  ioReadCompletionListener.java:165)
   at
   com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsy
  ncFuture
  .java:217)
   at
   com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(Async
  ChannelF
  uture.java:161)
   at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
   at
  com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
   at
   com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHan
  dler.jav
  a:775)
   at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Business Process Manager Advanced Users     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Queries to relationship via the WAS     *
  *                      Relationship Manager may fail with a    *
  *                      RelationshipServiceException.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Due to upgrade from WPS to BPM. The runtime name has been
  changed; however, the Relationship Manager only handled the
  change in the Process Center (PC) containing this service but
  not the Process Server. When running the query against the
  Process Server, the exception occurs.
  

Problem conclusion

• The fix provided allows the Relationship Manager to correctly
  handle the Process Server
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R800 PSY

     UP