users
[Top] [All Lists]

Re: [cinjug-users] Log4J event has commas inside Long integers

To: James Carman <james@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [cinjug-users] Log4J event has commas inside Long integers
From: twcrone@xxxxxxxxxxxxx
Date: Wed, 12 Dec 2007 09:49:40 -0500
Cc: users@xxxxxxxxxx
Delivered-to: mailing list users@xxxxxxxxxx
In-reply-to: <f2e8eedf0712120606gb6dee49rd260eafbd1c00e07@xxxxxxxxxxxxxx>
Mailing-list: contact users-help@xxxxxxxxxx; run by ezmlm
Priority: normal
References: <f6f6deb1c03c.475fa158@xxxxxxxxxxxxx> <f2e8eedf0712120606gb6dee49rd260eafbd1c00e07@xxxxxxxxxxxxxx>
It is in a longer string (e.g."1,099@@taskType@@Descriptive text here.")

----- Original Message -----
From: James Carman <james@xxxxxxxxxxxxxxxxxxxx>
Date: Wednesday, December 12, 2007 9:07
Subject: Re: [cinjug-users] Log4J event has commas inside Long integers
To: "twcrone@xxxxxxxxxxxxx" <twcrone@xxxxxxxxxxxxx>
Cc: users@xxxxxxxxxx

> Are you just logging the Long by itself, or is it contained
> within a
> longer string (something like "processing " + id)?
>
> On 12/12/07, twcrone@xxxxxxxxxxxxx <twcrone@xxxxxxxxxxxxx> wrote:
> > Has anyone ever had a problem with a Log4J logging event
> containing commas
> > (and maybe even some extra spaces) in a Long integer ID. 
> Seems like there
> > should be a way to configure it to not add commas to integers
> even in the
> > output or something.  Right now we simply strip them but
> that is a temp fix.
> >
> > Thanks,
> >
> > - Todd
> >
>
<Prev in Thread] Current Thread [Next in Thread>