GlassFish:v2.1.1-(build B31g-fcs) Solaris 10 Container GlassFish access & Server.log Time Stamp Issue (Doc ID 1486141.1)

Last updated on JUNE 07, 2022

Applies to:

Symptoms

GlassFish:v2.1.1-(build b31g-fcs) used on Solaris 10 X86 Containers may lead to mis-match of access & server.log time stamp, if Containers are not restarted after the OS Time Change.

1). <GF_install_root>/bin/asadmin version –verbose
<GF_install_root>/bin$> asadmin version --verbose

Unable to communicate with admin server, getting version locally.

Version = Sun GlassFish Enterprise Server v2.1.1 ((v2.1 Patch06)(9.1_02 Patch12)) (build b31g-fcs)

Command version executed successfully.

2). uname -a, /etc/release

xxxxx@[SERVER1]:~$> uname –a
SunOS [SERVER1] 5.10 Generic_147441-09 i86pc i386 i86pc
xxxxx@[SERVER1]:~$>

xxxxx@[SERVER1]:~$> cat /etc/release
                   Oracle Solaris 10 8/11 s10x_u10wos_17b X86
 Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
                           Assembled 23 August 2011
xxxxx@[SERVER1]:~$>


3). output of "time" and "date" commands for both the containers

xxxxx@[SERVER1]:~$> date
Mon Aug 13 17:30:21 PKT 2012

xxxxx@[SERVER1]:~$> date
Mon Aug 13 17:30:19 PKT 2012

These 2 containers are Local Zones.

Changes

 Changes to OS Time Zone specific to Country Standard Time.

Cause

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