Bug 778140 (SOA-653) - 4.3 IR1 server - logging cycled every minute
Summary: 4.3 IR1 server - logging cycled every minute
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-653
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 IR1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 IR1
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-08 17:17 UTC by Len DiMaggio
Modified: 2008-09-30 10:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P 4.3, IR4 (standalone/default and embedded/production)
Last Closed: 2008-09-30 10:21:10 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-653 0 None None None Never

Description Len DiMaggio 2008-08-08 17:17:54 UTC
Date of First Response: 2008-08-11 05:33:06
project_key: SOA

The server.log is being truncated and recreated every minute.

13:15:06,929 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
13:15:06,960 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:15:07,096 INFO  [Server] JBoss (MX MicroKernel) [SOA_4.3.0.GA_IR1 (build: SVNTag=SOA_4.3.0.GA_IR1 date=200808090523)] Started in 1m:45s:181ms
13:15:34,883 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:16:34,887 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:17:34,890 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml

Comment 1 Julian Coleman 2008-08-11 09:33:06 UTC
The issue occurs when the time stamp of the jboss-log4j.xml is in the future.

The source of the problem is the clock on the build machine (stacks4), which
is set approximately 24 hours in the future.

The fix is to ensure that the clock on stacks4 is synchronised via NTP (need
to talk to the administrator of stacks4 to fix this).

We will also ensure that NTP synchronisation is running on the new build
machine in Brno (jawa05) when we run future builds.



Note You need to log in before you can comment on or make changes to this bug.