PI50075: EJBDEPLOY RMIC CLASS NOT FOUND EXCEPTION ON SUN OS WHEN USING NO N DEFAULT JVM

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• EJBDeploy RMIC class not found exception on sun os when using no
  default JVM
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server on Solaris or HP UX that use the     *
  *                  non-default JVM for EJBDeploy               *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using non-default JVM with         *
  *                      EJBDeploy on certain Operating          *
  *                      Systems the java process fails with a   *
  *                      'no such method error'                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using EJBDeploy on a non-default JVM on certain Operating
  Systems, the java process fails with a 'no such method error'.
  This was caused by a hardcoded path in the EJBDeploy code.
  

Problem conclusion

• The hardcoded path has been replaced.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.8.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP