JR46804: ORG.OMG.CORBA.NO_IMPLEMENT.FORWARD LIMIT REACHED WHEN REMOVING A GROUP FROM A TEAM

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• The problem is-"Error- org.omg.CORBA.NO_IMPLEMENT.Forward limit
  reached" after changing a Team.
  
  Reproduction steps
  -- 1. I want to-remove two groups-from a team
  -- 2. After removing them I pressed save I obtained above error
  message
  ---3. From now on- adding- users or groups no longer works with
  above error
  
  Stack trace:
  
  2013-05-21 16:58:18,939 [Thread-27] ERROR
  com.lombardisoftware.client.ae.server.RepositoryServerNodeImpl
  - Exception during ping
  com.lombardisoftware.client.delegate.BusinessDelegateException:
  CORBA NO_IMPLEMENT 0x49421040 No; nested exception is:
   org.omg.CORBA.NO_IMPLEMENT: Forward limit reached  vmcid:
  0x49421000  minor code: 40  completed: No
   at
  com.lombardisoftware.client.delegate.BusinessDelegateException.a
  sBusinessDelegateException(BusinessDelegateException.java:41)
   at
  com.lombardisoftware.client.delegate.common.WebsphereDelegateHel
  per.doAs(WebsphereDelegateHelper.java:152)
   at
  com.lombardisoftware.client.delegate.common.WebsphereDelegateHel
  per.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.j
  ava:168)
   at
  com.lombardisoftware.client.delegate.UserStatusServicesDelegateD
  efault.setClientActivityStatusAndPALUpdates(UserStatusServicesDe
  legateDefault.java:141)
   at
  com.lombardisoftware.client.ae.server.RepositoryServerNodeImpl$B
  ackgroundServerPing$4.call(RepositoryServerNodeImpl.java:4463)
   at
  com.lombardisoftware.client.ae.server.RepositoryServerNodeImpl$B
  ackgroundServerPing$4.call(RepositoryServerNodeImpl.java:4461)
   at
  java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:31
  5)
   at java.util.concurrent.FutureTask.run(FutureTask.java:150)
   at
  java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoo
  lExecutor.java:886)
   at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
  cutor.java:908)
   at java.lang.Thread.run(Thread.java:736)
  Caused by: java.rmi.RemoteException: CORBA NO_IMPLEMENT
  0x49421040 No; nested exception is:
   org.omg.CORBA.NO_IMPLEMENT: Forward limit reached  vmcid:
  0x49421000  minor code: 40  completed: No
   at
  com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDeleg
  ateImpl.java:330)
   at javax.rmi.CORBA.Util.mapSystemException(Util.java:84)
   at
  com.lombardisoftware.server.ejb.userstatus._UserStatusServices_S
  tub.setClientActivityStatusAndPALUpdates(_UserStatusServices_Stu
  b.java:327)
   at
  com.lombardisoftware.client.delegate.UserStatusServicesDelegateD
  efault$2.run(UserStatusServicesDelegateDefault.java:144)
   at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:284)
   at javax.security.auth.Subject.doAs(Subject.java:573)
   at
  com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:19
  4)
   at
  com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:15
  1)
   at
  com.lombardisoftware.client.delegate.common.WebsphereDelegateHel
  per.doAs(WebsphereDelegateHelper.java:150)
   at
  com.lombardisoftware.client.delegate.common.WebsphereDelegateHel
  per.doAsCurrentSubjectContextSensitive(WebsphereDelegateHelper.j
  ava:163)
   ... 8 more
  Caused by: org.omg.CORBA.NO_IMPLEMENT: Forward limit reached
  vmcid: 0x49421000  minor code: 40  completed: No
   at
  com.ibm.ws.cluster.router.selection.SelectionManager.targetForwa
  rded(SelectionManager.java:365)
   at
  com.ibm.ws.wlm.client.WLMClientRequestInterceptor.receive_other(
  WLMClientRequestInterceptor.java:363)
   at
  com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorM
  anager.java:599)
   at
  com.ibm.rmi.pi.InterceptorManager.iterateClientInterceptors(Inte
  rceptorManager.java:404)
   at
  com.ibm.rmi.pi.InterceptorManager.iterateReceiveOther(Intercepto
  rManager.java:720)
   at
  com.ibm.rmi.corba.ClientDelegate.intercept(ClientDelegate.java:1
  014)
   at
  com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:453)
   at
  com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:119
  3)
   at
  com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:795)
   at
  com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:122
  3)
   at
  org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:484)
   at
  com.lombardisoftware.server.ejb.userstatus._UserStatusServices_S
  tub.setClientActivityStatusAndPALUpdates(_UserStatusServices_Stu
  b.java:302)
   ... 15 more
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users who run BPM in cluster environment.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Process Designer can't reconnect to     *
  *                      Process Center when server has been     *
  *                      restarted (in cluster environment).     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Process Designer creates many ORB instances, it is not
  supported by WebSphere Application Server WLM. This problem
  only happens in cluster environment.
  

Problem conclusion

• Code logic has been changed during Process Designer
  initialization to avoid creating many ORB instances.
  
  JR46804 for BPM v8.0.1.1 is available in Fix Central.
  Installation instruction can be downloaded along with
  the JR46804 iFix file.
  

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