At Start-Up, GlassFish Server or SGCS Log Shows Invalid 'Does not exist' Path for Classpath Elements

(Doc ID 1283315.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Communication Server - Version: 2.0 and later   [Release: 2.0 and later ]
Oracle GlassFish Server - Version: 2.1.1 and later    [Release: 2.1 and later]
Information in this document applies to any platform.

Symptoms

At start-up time, the application or communications server log shows classpath elements containing the text 'Does not exist', such as the following

-Dcom.sun.aas.classloader.serverClassPath.ee=Does not exist/lib/hadbjdbc4.jar,/opt/sgcs-2_0-p05/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,Does not exist/lib/dbstate.jar,Does not exist/lib/hadbm.jar,Does not exist/lib/hadbmgt.jar,/...


Changes

If present at all, this message will almost certainly have been present since installation of the product.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms