My Oracle Support Banner

GlassFish Server 2.1.x Logger Format Messed Up And Not Logging After Updating Java to JDK6u51, JDk5u51 Or JDK7u25 (Doc ID 1566979.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.

Symptoms

When using GlassFish Server 2.1.x with the newest Java version


the logs changed format on startup to something like the following:

Jul 1, 2013 5:51:50 PM com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
INFO: WEB0712: Starting Sun GlassFish Enterprise Server v2.1.1 Patch21 HTTP/1.1 on 8080
Jul 1, 2013 5:51:50 PM com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
INFO: WEB0712: Starting Sun GlassFish Enterprise Server v2.1.1 Patch21 HTTP/1.1 on 8083
Jul 1, 2013 5:51:50 PM com.sun.enterprise.web.connector.grizzly.GrizzlyHttpProtocol start
INFO: WEB0712: Starting Sun GlassFish Enterprise Server v2.1.1 Patch21 HTTP/1.1 on 4849
Jul 1, 2013 5:51:50 PM com.sun.enterprise.management.selfmanagement.SelfManagementService onReady

 
After the GlassFish completely startup, no more logging will end up on the server.log and logging stops.

Changes

This change when the Java JDK version is update to JDK 6 update 51 (from JDK 6 update 45).
Similar issue when when GlassFish using JDK 5 is updated to latest JDK 5 update 51.
For JDK 7, this issue is also seen when JDK 7 update 25 is used with GlassFish 2.1.x.

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!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.