IV54864: NOCLASSDEFFOUNDERROR OBSERVED WHEN CUSTOM CLASSLOADER USED AS SYSTEM CLASSLOADER WITH LAZY CLASSLOADER INITIALIZATION.

APAR status

• Closed as program error.

Error description

• Error Message: Error noticed:
  Exception in thread "main" java.lang.NoClassDefFoundError:
  <Class name>
  Could not find the main class: <Class name>.  Program will exit.
  <Class name> is the customer class loader
  .
  Stack Trace: LoadClass
  JavaMain
  _pthread_body
  .
  

Local fix

• The issue can be worked around using the
  -Djava.lang.ClassLoader.lazyInitialization=false option. Note
  however that this will cause an increase in footprint when new
  ClassLoaders are created but never being used.
  

Problem summary

• The problem is caused when we specify a custom classloader to be
  used as system classLoader, together with lazy classloader
  initialization logic.
  

Problem conclusion

• This APAR will be fixed in the following Java Releases:
     6    SR16      (6.0.16.0)
     6 R1 SR8       (6.1.8.0)
     7    SR7       (7.0.7.0)
     7 R1 SR1       (7.1.1.0)
  .
  The JVM has been updated to correctly process the initialisation
  of custom classloader as system classloader in all conditions.
  

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

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSY

     UP

• R260 PSY

     UP

• R270 PSY

     UP