IZ37032: SEMAPHORE ERROR CATCHING FOR SHARED CLASS CACHE.

APAR status

• Closed as program error.

Error description

• Error Message: The user would not see an error if the a
  semaphore for the shared class cache could not be taken or
  given.
  
  This problem may surface as a hang in a call to semop when
  initializing the shared classes feature of Java 5.0 when 2
  or more application servers are started concurrently.
  

Local fix

• If you are encountering a hang or other errant behavior with the
  Shared Classes feature of Java 5.0, please delete the "control
  files" created.
  
  These files are typically created in the /tmp directory, but the
  "controlDir" option of -Xshareclasses may be used to override
  the location. If you are using a middleware product which
  enables these Shared Classes, consult that product's
  documentation as to the location of these Control Files.
  
  You can also avoid this problem entirely by disabling use of the
  shared class feature. By default the JVM ships with this feature
  disabled, so Stand-Alone Java applications should not require
  any changes.
  If you are using a product which does enable this feature
  (middleware like WebSphere Application Server for example) the
  following java commandline option can be used to deactivate it:
      -Xshareclasses:none
  

Problem summary

• Certain Error Conditions in Shared Classes code were not being
  correctly handled. These error conditions now generate
  appropriate messages and terminate the use of the shared classes
  feature.
  

Problem conclusion

• This problem will be resolved in Java 5.0 SR9
  

Temporary fix

• Remove any Shared Class files that are in effect
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PK77156

Fix information

• Fixed component name

  JAVA 5 J9 COMMO

• Fixed component ID

  620500127

Applicable component levels

• R500 PSY

     UP