PM67404: com.ibm.websphere.sca.ServiceRuntimeException Operation not implemented

APAR status

• Closed as program error.

Error description

• The bean name for a given service may not always be unique. As
  a result, the first bean registered will recieve all service
  requests. So if the operation is implemented in the second
  bean, then the implementation is not found raising the
  "Operation [myOperation] is not implemented by
  [myImplementation] for
  component [{mycomponent} myImplementation]" message.
  

Local fix

• 1. Look into the ffdc logs where you should see something like
  this:
  
  [6/20/12 9:40:15:635 EDT] FFDC
  Exception:com.ibm.websphere.sca.ServiceRuntimeException
  SourceId:com.ibm.ws.sca.internal.java.handler.JavaImplementation
  Handler
   ProbeId:005
  com.ibm.websphere.sca.ServiceRuntimeException: Operation
  [myOperation] is not implemented by
  [myImplementation] for
  component
   [{myComponent}myImplementation]
   at
   com.ibm.ws.sca.internal.java.handler.JavaImplementationHandler.
  processM
  essage(JavaImplementationHandler.java:201)
   at
   com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proc
  essMessa
  geWithPCI(MessageDispatcherImpl.java:755)
   at
   com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proc
  essMessa
  ge(MessageDispatcherImpl.java:1607)
   at
   com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process
  (Managed
  MessageImpl.java:980)
   at
   com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transaction
  GlobalAc
  tivitySessionAny(UOWNativeWASStrategyImpl.java:853)
   at
   com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage(
  JoinUOWN
  ativeHandler.java:207)
   at
   com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proc
  essMessa
  geWithPCI(MessageDispatcherImpl.java:766)
   at
   com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.proc
  essMessa
  ge(MessageDispatcherImpl.java:1607)
   at
   com.ibm.ws.sca.internal.binding.handler.SCAExportMessageHelper.
  processM
  essage(SCAExportMessageHelper.java:343)
   at
   com.ibm.ws.sca.internal.binding.handler.spi.impl.ExportSCAInvok
  er.invok
  e(ExportSCAInvoker.java:63)
   at
   com.ibm.ws.container.binding.classicsca.ejb.EJBDefaultBindingSe
  rvicePro
  vider$EJBDefaultBindingServiceInvoker.invoke(EJBDefaultBindingSe
  rvicePro
  vider.java:57)
   at
   com.ibm.ws.container.binding.classicsca.ejb.EJBDefaultBindingSe
  rvicePro
  vider$EJBDefaultBindingServiceInvoker.invoke(EJBDefaultBindingSe
  rvicePro
  vider.java:40)
   at
   com.ibm.ws.container.binding.ejb.BaseContainerBeanImpl.invoke(B
  aseConta
  inerBeanImpl.java:54)
   at
  com.ibm.wsspi.container.binding.sca.remote.ServiceRemoteBean_586
  14.proce
  ssMessage(Unknown
  Source)
  
  2. Look for 'component [{X}' - where X will indicate the module
  name for
  the afflicted module, e.g. component [{myComponent} where module
  name is myComponent here.
  3. Take the module name and append 'App' to it - which gives
  you the JEE
  application name, e.g. myComponentApp
  4. Restart the application
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server        *
  *                  Feature                                     *
  *                  Pack for Service Component Architecture     *
  *                  (SCA)                                       *
  *                  users                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: com.ibm.websphere.sca.ServiceRuntimeExc *
  *                      ept                                     *
  *                      ion Operation [o] is not implemented by *
  *                      [i] for component [c]                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Process Server uses the SCA feature pack to create an
  EJB for each application component that has an SCA binding.  The
  code that creates the EJB may randomly use an existing EJB
  intended for another component rather than creating a new EJB.
  When this happens, calls to that component are delivered to the
  wrong implementation which results in the exception
  com.ibm.websphere.sca.ServiceRuntimeException Operation [o] is
  not implemented by [i] for component [c].
  

Problem conclusion

• The code that generates the EJB is corrected so that it won't
  use an existing EJB.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 1.0.1.15. 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:

  PM67655

Fix information

• Fixed component name

  WAS SCA FEATURE

• Fixed component ID

  5724J0854

Applicable component levels

• R700 PSY

     UP