Re: Date corruption in logging

[Mark Lybarger <ml...@gmail.com>]

we experience the same thing on an ibm p520 machine (and a p570). 
seems reverting to a 32bit jvm helps, but that's not really a good
solution.  my understanding is that log4j is just using
java.util.Date() for logging, so it would seem to  be an issue with
the JDK, but i can't say for certain.

one annoying thing is that the daily rolling file appender for the
jboss server.log never ends up rolling, and the file just grows to an
unmanageable size after time.

On 5/26/05, Simon Kelly <si...@talgentra.com> wrote:
> Hi All,
>
> I am currently using log4j on an IBM AS400 pcc64 ( 64 bit architecture )
> within JBoss.  The issue I am having is that the logging date displayed
> is matching the system time for about 30 seconds then it switches to "31
> Dec 1969 16:00:00,000" and stays like this.
>
> Has anyone seen this before, and if so does anyone know a solution?
>
> Kind regards
>
> Simon
>
> Simon D Kelly
> Support Analyst
>
> Talgentra Ltd.
> 720 Waterside Drive,
> Aztec West,
> Bristol.
> BS32 4UD.
>
> Tel    : +44 (0) 1454 892000 (Main)
>          +44 (0) 1454 892032 (Direct)
> Fax    : +44 (0) 1454 892030
> Email  : simon.kelly@talgentra.com
>
> Talgentra develops and markets Tallyman and Gentrack, industry-leading
> solutions for customer billing and revenue collection.
>
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are, by
> definition, not smart enough to debug it."
> -Brian W. Kernighan
> "no level of fitness - or, for that matter, drunkenness - justifies
> wearing a tank top at home"
> -Omelianuk & Allen
>
>
>
> ######################################################################################
>
> This email from Talgentra is intended only for the personal use of the
> recipient(s) named above. The email and any files transmitted with it are confidential to the intended recipient(s) and may be legally privileged or contain proprietary and private information. If you are not an intended recipient, you may not review, copy or distribute this message. If received in error, please notify the sender and delete the message from your system.
>
> Any views or opinions expressed in this email and any files transmitted with it are those of the author only and may not necessarily reflect the views of Talgentra and it does not create any legally binding rights or obligations whatsoever. Unless otherwise pre-agreed by exchange of hard copy documents signed by duly authorised representatives, contracts may not be concluded on behalf of Talgentra by email.
>
> Please note that neither Talgentra nor the sender accepts any responsibility for any viruses and it is your responsibility to scan the email and the attachments (if any). All email received and sent by Talgentra may be monitored to protect the business interests of Talgentra.
>
>
>
> ######################################################################################
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org