You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Stephen Graham <sg...@bigpond.com> on 2003/06/09 03:02:50 UTC
Logger seems broken or how to configure Log4J in my service.
I've been using the nightly builds and as of about the 5th June I've had a
problem with configuring log4j in my service.
The class that implements my web service calls
public DataFacade() {
System.out.println("Constructing 'DataFacade' server interface...");
System.out.println("Loading logger configuration : " +
ServerProperties.getInstance().loggerConf);
PropertyConfigurator.configure(ServerProperties.getInstance().loggerConf);
...
}
Since around the date I mentioned the call to PropertyConfigurator.configure
hangs (never returns), which stops my service from starting up.
When this first happened I tried using a log4j-yyyymmdd.jar from an earlier
version - which immediately fixed the problem, so I assumed this was just
temporarily broken.
But now I'm using nightly build 20030608 and the problem still exists.
So I'm wondering what is the appropriate way to configure log4j in my
service (read: am I doing something wrong) or is this a bug?
Regards
Stephen Graham.
RE: Logger seems broken or how to configure Log4J in my service.
Posted by Benjamin Tomasini <bt...@neteverything.com>.
About this bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10479
It is rather insidious as it breaks the logger in other parts of the
app. A log4.properties doesn't belong in a jar any more than a web.xml
belongs in a jar (not that it would be read). These are runtime
parameters. It breaks the whole contract with log4j.
I can submit a build.xml patch if there is a consensus that this is a
but an not a feature.
Ben
On Sun, 2003-06-08 at 23:51, Stephen Graham wrote:
> Yes it's in there. I assume, I get rid of it and all will be fine?
> I'll see if I can find it in the bug database but I'm not quite sure about
> how to go about that.
>
> Regards
> Stephen.
>
> > -----Original Message-----
> > From: Benjamin Tomasini [mailto:btomasini@neteverything.com]
> > Sent: 9 June 2003 11:11 AM
> > To: axis-user@ws.apache.org
> > Subject: Re: Logger seems broken or how to configure Log4J in
> > my service.
> >
> >
> > Open up axis.jar and see if log4.properties is in the jar.
> >
> > This is an open (and very annoying) bug.
> >
> > Please post back if it is there. I think developers have
> > burned up hours on this one.
> >
> >
> > On Sun, 2003-06-08 at 21:02, Stephen Graham wrote:
> > > I've been using the nightly builds and as of about the 5th
> > June I've
> > > had a problem with configuring log4j in my service.
> > >
> > > The class that implements my web service calls
> > >
> > > public DataFacade() {
> > > System.out.println("Constructing 'DataFacade' server
> > interface...");
> > > System.out.println("Loading logger configuration : " +
> > > ServerProperties.getInstance().loggerConf);
> > >
> > >
> > PropertyConfigurator.configure(ServerProperties.getInstance().
> > loggerConf);
> > > ...
> > > }
> > >
> > > Since around the date I mentioned the call to
> > > PropertyConfigurator.configure hangs (never returns), which
> > stops my
> > > service from starting up.
> > >
> > > When this first happened I tried using a log4j-yyyymmdd.jar from an
> > > earlier version - which immediately fixed the problem, so I assumed
> > > this was just temporarily broken.
> > >
> > > But now I'm using nightly build 20030608 and the problem
> > still exists.
> > >
> > > So I'm wondering what is the appropriate way to configure
> > log4j in my
> > > service (read: am I doing something wrong) or is this a bug?
> > >
> > > Regards
> > > Stephen Graham.
> > --
> > Benjamin Tomasini <bt...@neteverything.com>
> > NetEverything, LLC
> >
--
Benjamin Tomasini <bt...@neteverything.com>
NetEverything, LLC
RE: Logger seems broken or how to configure Log4J in my service.
Posted by Stephen Graham <sg...@bigpond.com>.
Yes it's in there. I assume, I get rid of it and all will be fine?
I'll see if I can find it in the bug database but I'm not quite sure about
how to go about that.
Regards
Stephen.
> -----Original Message-----
> From: Benjamin Tomasini [mailto:btomasini@neteverything.com]
> Sent: 9 June 2003 11:11 AM
> To: axis-user@ws.apache.org
> Subject: Re: Logger seems broken or how to configure Log4J in
> my service.
>
>
> Open up axis.jar and see if log4.properties is in the jar.
>
> This is an open (and very annoying) bug.
>
> Please post back if it is there. I think developers have
> burned up hours on this one.
>
>
> On Sun, 2003-06-08 at 21:02, Stephen Graham wrote:
> > I've been using the nightly builds and as of about the 5th
> June I've
> > had a problem with configuring log4j in my service.
> >
> > The class that implements my web service calls
> >
> > public DataFacade() {
> > System.out.println("Constructing 'DataFacade' server
> interface...");
> > System.out.println("Loading logger configuration : " +
> > ServerProperties.getInstance().loggerConf);
> >
> >
> PropertyConfigurator.configure(ServerProperties.getInstance().
> loggerConf);
> > ...
> > }
> >
> > Since around the date I mentioned the call to
> > PropertyConfigurator.configure hangs (never returns), which
> stops my
> > service from starting up.
> >
> > When this first happened I tried using a log4j-yyyymmdd.jar from an
> > earlier version - which immediately fixed the problem, so I assumed
> > this was just temporarily broken.
> >
> > But now I'm using nightly build 20030608 and the problem
> still exists.
> >
> > So I'm wondering what is the appropriate way to configure
> log4j in my
> > service (read: am I doing something wrong) or is this a bug?
> >
> > Regards
> > Stephen Graham.
> --
> Benjamin Tomasini <bt...@neteverything.com>
> NetEverything, LLC
>
Re: Logger seems broken or how to configure Log4J in my service.
Posted by Benjamin Tomasini <bt...@neteverything.com>.
Open up axis.jar and see if log4.properties is in the jar.
This is an open (and very annoying) bug.
Please post back if it is there. I think developers have burned up
hours on this one.
On Sun, 2003-06-08 at 21:02, Stephen Graham wrote:
> I've been using the nightly builds and as of about the 5th June I've had a
> problem with configuring log4j in my service.
>
> The class that implements my web service calls
>
> public DataFacade() {
> System.out.println("Constructing 'DataFacade' server interface...");
> System.out.println("Loading logger configuration : " +
> ServerProperties.getInstance().loggerConf);
>
> PropertyConfigurator.configure(ServerProperties.getInstance().loggerConf);
> ...
> }
>
> Since around the date I mentioned the call to PropertyConfigurator.configure
> hangs (never returns), which stops my service from starting up.
>
> When this first happened I tried using a log4j-yyyymmdd.jar from an earlier
> version - which immediately fixed the problem, so I assumed this was just
> temporarily broken.
>
> But now I'm using nightly build 20030608 and the problem still exists.
>
> So I'm wondering what is the appropriate way to configure log4j in my
> service (read: am I doing something wrong) or is this a bug?
>
> Regards
> Stephen Graham.
--
Benjamin Tomasini <bt...@neteverything.com>
NetEverything, LLC