PM50100: EJB 2.1 MODULE WITH WEBSERVICE-ONLY STATELESS SESSION BEAN FAILS WHEN DEPLOYED FROM A RAD WORKSPACE WITHOUT EXPORTING.

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
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

• [10/12/11 16:48:43:265 CDT] 0000001b EJBContainerI I
  CNTR0167I: The server is binding the
  webservice.address.TestAddressHome interface of the
  TestAddressSoapBindingImpl enterprise bean in the EJB21.jar
  module of the EJB21EAR application.  The binding location is:
  <null>
  [10/12/11 0:44:35:109 EDT] 00000009 AppManagement W
  ADMA0116W: Unable to start: TEW8J14_E2EEAR using:
  WebSphere:name=ApplicationManager,process=server1,platform=proxy
  ,node=ws002Node09,version=8.0.0.0,type=ApplicationManager,mbeanI
  dentifier=ApplicationManager,cell=testCell,spec=1.0
  exception is: javax.management.MBeanException: Exception
  thrown in RequiredModelMBean while trying to invoke operation
  startApplication
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Rational Application Developer users of     *
  *                  Enterprise Java Beans (EJB).                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Stateless session beans with only a     *
  *                      webservices client view prevents        *
  *                      the application from starting.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When Rational Application Developer is used to deploy an EJB
  application without exporting the application, a binding object
  is not created for a stateless session bean that has a
  webservices client view only.  In this scenario, the EJB
  container should create a default binding name based on the
  home interface name of the stateless session bean, but because
  a binding object does not exist, this logic does not run.  The
  EJB container then tries to bind the EJB using a null binding
  name.
  

Problem conclusion

• The logic to create a default binding name has been fixed to
  run regardless of whether or not a binding object exists.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2.  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

• R800 PSY

     UP