RE: Need help getting log4j to work under apache/tomcat/jboss on a linux server

[Swami Iyer <SI...@descartes.com>]

Hi gary,
The log4j in jboss 2.2.2 needs to be enabled through the mbean(s) in the
jboss.conf. Because the jboss 2.2.2 still uses its own logging mechanism and
allowed the usage of the log4j.

With the jboss 2.4.x and jboss 3.x the jboss uses log4j as its only means to
do logging.

Thanks,
Swami

> -----Original Message-----
> From: Gary Graham [mailto:gary.graham@isspitt.com]
> Sent: September 6, 2002 10:04 AM
> To: Log4J Users List
> Subject: RE: Need help getting log4j to work under apache/tomcat/jboss
> on a linux server
> 
> 
> Hi Ceki,
> 
> I assume that log4j must be part of this version of jboss 
> since i found a log4j.properties file in the directory 
> jboss/conf/default directory.  Is this what I should use, or 
> is this just an example file that needs to be placed 
> somewhere else once it has been modified as needed?
> 
> I tried simply putting the categories I need in this log4j 
> properties file but it dodnt seem to make any difference.
> 
> Best,
> 
> Gary
> 
> -----Original Message-----
> From: Ceki Gülcü [mailto:ceki@qos.ch]
> Sent: Thursday, September 05, 2002 4:27 PM
> To: Log4J Users List
> Subject: RE: Need help getting log4j to work under apache/tomcat/jboss
> on a linux server
> 
> 
> 
> I think older versions of JBoss use log4j.properties. 
> Actually, I am not 
> sure JBoss 2.2.x uses log4j at all. Is log4j shipped with JBoss 2.2.2?
> 
> At 14:23 05.09.2002 -0400, Gary Graham wrote:
> >Hi Ceki,
> >
> >Thank you for your response.  I read the article and went 
> looking for the 
> >log4j.xml file on our linus server but could not find it 
> anywhere.  We are 
> >running jboss 2.2.2 with Tomcat 3.2.2
> >could this be why I cant find the configuration file?
> >
> >Thanks,
> >
> >Gary
> >
> >-----Original Message-----
> >From: Ceki Gülcü [mailto:ceki@qos.ch]
> >Sent: Thursday, September 05, 2002 12:27 PM
> >To: Log4J Users List
> >Subject: Re: Need help getting log4j to work under 
> apache/tomcat/jboss
> >on a linux server
> >
> >
> >
> >JBoss used log4j internally. Consequently, the WEB-INF/lib 
> does not work.
> >You need to adapt JBoss' log4j configuration file.
> >
> >See JBoss discussion groups
> >and  http://www.jboss.org/developers/guides/logging.jsp for 
> more info.
> >
> >At 10:48 05.09.2002 -0400, you wrote:
> > >Hello all,
> > >
> > >I have been trying - unsuccessfully I might add - to get 
> log4j to produce
> > >a log file on our linux server running 
> apache/tomcat/jboss.  I deployed a
> > >war file in the Jboss deploy directory andf all of thast 
> worked just
> > >fine.  The application is up and running.  However, - no 
> log4j log file is
> > >being produced.  I placed the log4j.priperties file in the 
> WEB-INF/lib
> > >just like I do on all other configurations, but for some 
> reason log4j
> > >doesn't work and doesn't complain either.  Here is a section of the
> > >log4j.properties file that defines the log file name:
> > >
> > >#log4j props file
> > >log4j.appender.default=org.apache.log4j.FileAppender
> > >log4j.appender.default.File=./wtt.log
> > >log4j.appender.default.layout=org.apache.log4j.PatternLayout
> > >log4j.appender.default.layout.ConversionPattern=%-4r %-5p 
> %c{2} %M.%L %x -
> > >%m\n
> > >#log4j.rootCategory=, default
> > >#set other modules to INFO normally
> > >log4j.category.WirelessLoginAction=INFO, default
> > >log4j.category.WirelessLoginAction2=INFO, default
> > >log4j.category.ConnPool.PoolManager=INFO, default
> > >log4j.category.ConnPool.ConnectionPool=INFO, default
> > >
> > >as you can see I am trying to log information to the file ./wtt.log
> > >
> > >however - no file by that name is ever created anywhere on 
> the server.
> > >
> > >Perhaps someone can point me in the direction of my errors.
> > >
> > >Thanks,
> > >
> > >Gary Graham
> >
> >--
> >Ceki
> >
> >TCP implementations will follow a general principle of robustness: be
> >conservative in what you do, be liberal in what you accept from
> >others. -- Jon Postel, RFC 793
> >
> >
> >
> >--
> >To unsubscribe, e-mail:   
<ma...@jakarta.apache.org>
>For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
>--
>To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
>For additional commands, e-mail:
<ma...@jakarta.apache.org>

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>