PM53156: SCA TARGET INNER SERVICE NOT FOUND AT INVOKE TIME

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Within an implementation.composite, a reference to a
  non-promoted singleton service will fail to find the
  service at invoke time.
  
  [10/13/11 15:19:11:810 EDT]     FFDC
  Exception:javax.naming.NameNotFoundException
  SourceId:com.ibm.ws.soa.sca.binding.sca.SCATargetInvoker
  ProbeId:399
  Reporter:com.ibm.ws.soa.sca.binding.sca.SCATargetInvoker@3b0cc74
  javax.naming.NameNotFoundException: Context:
  IBM-DBDC88DFE70Node02Cell/nodes/IBM-DBDC88DFE70Node03/servers/se
  rver1, name:
  cell/persistent/scaServices/ConsumerComponent/c1_1_1: First
  component in name c1_1_1 not found. [Root exception is
  org.omg.CosNaming.NamingContextPackage.NotFound:
  IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: NameNotFoundException occurs invoking   *
  *                      a singleton service defined on an       *
  *                      implementation.composite inner          *
  *                      component.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem affects certain Service Component Architecture
  ( SCA ) applications using implementation.composite. Within
  the implementation, a reference to a singleton service will
  fail to find the service.
  

Problem conclusion

• When a component has only one service, the component name
  alone can be used as a target URI. This causes problems for
  the implementation.composite case because the service is
  registered using the full URI including service name, while
  the inner reference uses the shortened form to perform service
  lookup.
  
  The runtime now detects this condition and will perform the
  correct lookup to find the service.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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:

  PM53208

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP