PI32652: UNABLE TO START SERVER FROM IBM I QSHELL ENVIRONMENT DUE TO CLASS LOADING ISSUE

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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

• When an application is packaged with an older version of commons
  logging the server is unable to be started via the 'startserver'
  command in QShell.  The following is seen in the callstack for
  the failure:
  
  Caused by: org.apache.commons.logging.LogConfigurationException:
   org.apache.commons.logging.LogConfigurationException:
  org.apache.commons.logging.LogConfigurationException: Class
  org.apache.commons.logging.impl.Log4JLogger does not implement
  Log
  

Local fix

• To resolve the issue the behavior of the classloader can be
  modified by adding the following JVM argument to the server:
  
  -Dibm.websphere.internalClassAccessMode=allow
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: On IBM i systems, the startServer       *
  *                      command fails. Starting a server in     *
  *                      Integrated Solutions Console,           *
  *                      if available, succeeds.                 *
  ****************************************************************
  * RECOMMENDATION:  Apply fix pack 8.5.5.6                      *
  ****************************************************************
  The WebSphere Application Server startServer command fails
  with a JAVA exception:
  "Class org.apache.commons.logging.impl.Log4JLogger does not
  implement Log".
  If the server is federated to a deployment manager, then
  starting the server from the Integrated Solutions Console
  succeeds.
  

Problem conclusion

• The WebSphere Application Server is fixed to enable the
  startServer command to work properly.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Add the following Generic JVM option to the failed server
  configuration: -Dibm.websphere.internalClassAccessMode=allow
  

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

• R850 PSY

     UP