My Oracle Support Banner

Variable Names Are Not Resolved Immediately When Used as Part of Log File Name in Oracle GlassFish Server 3.1.1 (Doc ID 1377265.1)

Last updated on NOVEMBER 30, 2011

Applies to:

Oracle GlassFish Server - Version: 3.1.1 to 3.1.1 - Release: 3.1 to 3.1
Information in this document applies to any platform.

Symptoms

If you modify the GlassFish Server's logging.properties file and specify a variable name as part of the log file destination, you will notice that the first few seconds of logging is not sent to the correct file.

For example, after setting:

com.sun.enterprise.server.logging.GFFileHandler.file=${com.sun.aas.instanceRoot}/logs/${com.sun.aas.instanceName}.log

When you start the Domain Administration Server (DAS) you will notice the first few seconds of output is logged to the file called:

${com.sun.aas.instanceName}.log

That is, the variable name is not resolved and is used literally as the filename.  Shortly afterward, the logging starts to appear in the server.log as expected.

Note: This issue is specific only to the DAS server instance.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.