log4perl-devel

[log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

I am working on a project which involves two development environments: one
is in java and uses log4j, the other in perl using log4perl. Programs in
either system are called interchangeably, and we would like to integrate
both the logging systems so they log to one file. What is the best way of
doing this? I've looked at using an SocketServer with log4j and a
SocketAppender with log4perl, but I get stream header errors when sending. =
I
noticed there may be a way to get the two to talk using XMLSocketServer's
and XMLSocketAppender's, but that is only available in the alpha version of
log4j, which I cannot use yet. Has anyone else tried to get a similar setup
going (i.e. log4perl and log4j using the same appender)? Thanks.

Re: [log4perl-devel] log4j Integration

[Mike S. <m...@pe...>]

On Mon, 28 Nov 2005, Anant K wrote:

> I am working on a project which involves two development environments: one
> is in java and uses log4j, the other in perl using log4perl. Programs in
> either system are called interchangeably, and we would like to integrate
> both the logging systems so they log to one file. What is the best way of
> doing this?

That's an interesting use case. CC:ing Ceki.

From a Log::Log4perl point of view, I'd say that a socket appender is probably the
best solution, similar to the Chainsaw example:

    http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff

> I've looked at using an SocketServer with log4j and a
> SocketAppender with log4perl, but I get stream header errors when sending.

With L4p or L4j?

> I
> noticed there may be a way to get the two to talk using XMLSocketServer's
> and XMLSocketAppender's, but that is only available in the alpha version of
> log4j, which I cannot use yet. Has anyone else tried to get a similar setup
> going (i.e. log4perl and log4j using the same appender)? Thanks.

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

The stream errors are on the log4j side; it does not seem to be able to
understand what log4perl is sending it.

On 12/7/05, Mike Schilli <m...@pe...> wrote:
>
> On Mon, 28 Nov 2005, Anant K wrote:
>
> > I am working on a project which involves two development environments:
> one
> > is in java and uses log4j, the other in perl using log4perl. Programs i=
n
> > either system are called interchangeably, and we would like to integrat=
e
> > both the logging systems so they log to one file. What is the best way
> of
> > doing this?
>
> That's an interesting use case. CC:ing Ceki.
>
> From a Log::Log4perl point of view, I'd say that a socket appender is
> probably the
> best solution, similar to the Chainsaw example:
>
>     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
>
> > I've looked at using an SocketServer with log4j and a
> > SocketAppender with log4perl, but I get stream header errors when
> sending.
>
> With L4p or L4j?
>
> > I
> > noticed there may be a way to get the two to talk using
> XMLSocketServer's
> > and XMLSocketAppender's, but that is only available in the alpha versio=
n
> of
> > log4j, which I cannot use yet. Has anyone else tried to get a similar
> setup
> > going (i.e. log4perl and log4j using the same appender)? Thanks.
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>

Re: [log4perl-devel] log4j Integration

[Mike S. <m...@pe...>]

On Wed, 7 Dec 2005, Anant K wrote:

> The stream errors are on the log4j side; it does not seem to be able to
> understand what log4perl is sending it.

Are you using XML format as described in the FAQ?

-- Mike

Mike Schilli
m...@pe...

> On 12/7/05, Mike Schilli <m...@pe...> wrote:
> >
> > On Mon, 28 Nov 2005, Anant K wrote:
> >
> > > I am working on a project which involves two development environments:
> > one
> > > is in java and uses log4j, the other in perl using log4perl. Programs in
> > > either system are called interchangeably, and we would like to integrate
> > > both the logging systems so they log to one file. What is the best way
> > of
> > > doing this?
> >
> > That's an interesting use case. CC:ing Ceki.
> >
> > From a Log::Log4perl point of view, I'd say that a socket appender is
> > probably the
> > best solution, similar to the Chainsaw example:
> >
> >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> >
> > > I've looked at using an SocketServer with log4j and a
> > > SocketAppender with log4perl, but I get stream header errors when
> > sending.
> >
> > With L4p or L4j?
> >
> > > I
> > > noticed there may be a way to get the two to talk using
> > XMLSocketServer's
> > > and XMLSocketAppender's, but that is only available in the alpha version
> > of
> > > log4j, which I cannot use yet. Has anyone else tried to get a similar
> > setup
> > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
>

Re: [log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

No, right now I am just trying to send a small string of text using
the plain layout.

From what I understand, the only reason log4perl works with Chainsaw
is because Chainsaw uses an XMLSocketReceiver to understand the XML
log4perl is sending it. Am I right on this?

I cannot use an XMLSocketReceiver in log4j, since I am forced to use a
stable version (XMLSocketReceiver is only available in the alpha
version of log4j). I would like to get the two to work together,
basically without using an XMLSocketReceiver on the log4j side.

On 12/8/05, Mike Schilli <m...@pe...> wrote:
> On Wed, 7 Dec 2005, Anant K wrote:
>
> > The stream errors are on the log4j side; it does not seem to be able to
> > understand what log4perl is sending it.
>
> Are you using XML format as described in the FAQ?
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>
> > On 12/7/05, Mike Schilli <m...@pe...> wrote:
> > >
> > > On Mon, 28 Nov 2005, Anant K wrote:
> > >
> > > > I am working on a project which involves two development environmen=
ts:
> > > one
> > > > is in java and uses log4j, the other in perl using log4perl. Progra=
ms in
> > > > either system are called interchangeably, and we would like to inte=
grate
> > > > both the logging systems so they log to one file. What is the best =
way
> > > of
> > > > doing this?
> > >
> > > That's an interesting use case. CC:ing Ceki.
> > >
> > > From a Log::Log4perl point of view, I'd say that a socket appender is
> > > probably the
> > > best solution, similar to the Chainsaw example:
> > >
> > >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> > >
> > > > I've looked at using an SocketServer with log4j and a
> > > > SocketAppender with log4perl, but I get stream header errors when
> > > sending.
> > >
> > > With L4p or L4j?
> > >
> > > > I
> > > > noticed there may be a way to get the two to talk using
> > > XMLSocketServer's
> > > > and XMLSocketAppender's, but that is only available in the alpha ve=
rsion
> > > of
> > > > log4j, which I cannot use yet. Has anyone else tried to get a simil=
ar
> > > setup
> > > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> > >
> > > -- Mike
> > >
> > > Mike Schilli
> > > m...@pe...
> > >
> >
>

Re: [log4perl-devel] log4j Integration

[Mike S. <m...@pe...>]

On Thu, 8 Dec 2005, Anant K wrote:

> No, right now I am just trying to send a small string of text using
> the plain layout.

But doesn't the target expect XML?

-- Mike

Mike Schilli
m...@pe...

> >From what I understand, the only reason log4perl works with Chainsaw
> is because Chainsaw uses an XMLSocketReceiver to understand the XML
> log4perl is sending it. Am I right on this?
>
> I cannot use an XMLSocketReceiver in log4j, since I am forced to use a
> stable version (XMLSocketReceiver is only available in the alpha
> version of log4j). I would like to get the two to work together,
> basically without using an XMLSocketReceiver on the log4j side.
>
> On 12/8/05, Mike Schilli <m...@pe...> wrote:
> > On Wed, 7 Dec 2005, Anant K wrote:
> >
> > > The stream errors are on the log4j side; it does not seem to be able to
> > > understand what log4perl is sending it.
> >
> > Are you using XML format as described in the FAQ?
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
> > > On 12/7/05, Mike Schilli <m...@pe...> wrote:
> > > >
> > > > On Mon, 28 Nov 2005, Anant K wrote:
> > > >
> > > > > I am working on a project which involves two development environments:
> > > > one
> > > > > is in java and uses log4j, the other in perl using log4perl. Programs in
> > > > > either system are called interchangeably, and we would like to integrate
> > > > > both the logging systems so they log to one file. What is the best way
> > > > of
> > > > > doing this?
> > > >
> > > > That's an interesting use case. CC:ing Ceki.
> > > >
> > > > From a Log::Log4perl point of view, I'd say that a socket appender is
> > > > probably the
> > > > best solution, similar to the Chainsaw example:
> > > >
> > > >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> > > >
> > > > > I've looked at using an SocketServer with log4j and a
> > > > > SocketAppender with log4perl, but I get stream header errors when
> > > > sending.
> > > >
> > > > With L4p or L4j?
> > > >
> > > > > I
> > > > > noticed there may be a way to get the two to talk using
> > > > XMLSocketServer's
> > > > > and XMLSocketAppender's, but that is only available in the alpha version
> > > > of
> > > > > log4j, which I cannot use yet. Has anyone else tried to get a similar
> > > > setup
> > > > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> > > >
> > > > -- Mike