Can you share your log4j.properties file contents and maybe some
example log statements (with necessary context code) that are causing
the problem?
On 12/12/07, twcrone@xxxxxxxxxxxxx <twcrone@xxxxxxxxxxxxx> wrote:
> 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
> > >
> >
|