Can you send or paste your log4j prop file. I'll try it with a test app
-R
Sent from my iPhone
On Feb 11, 2009, at 8:10 AM, "Stanley, Eric"
<[email protected]> wrote:
Anyone have any thoughts on this? It's making me crazy. Your help is
very much appreciated.
-Ryan
-----Original Message-----
From: Stanley, Eric [mailto:[email protected]]
Sent: Monday, February 09, 2009 9:42 AM
To: [email protected]
Subject: RE: logging not working using log4j
Richard,
It has always been in WEB-INF/classes, and I am positive its
getting loaded properly. Like I mentioned before, my app uses the same
properties file, and it works fine. I have switched the the rootLogger
severity to confirm this. I am also positive that iBATIS code is being
called as all my selects are being populated properly. What am I
missing?
-Ryan
-----Original Message-----
From: Richard Yee [mailto:[email protected]]
Sent: Sunday, February 08, 2009 5:30 PM
To: [email protected]
Subject: Re: logging not working using log4j
Eric,
Did you at least see more logging messages? If not, this indicates
that
the log4j.properties file that you are editing is not in the classpath
and is not getting read by the application. I'd suggest putting it in
the WEB-INF/classes directory of your webapp.
Otherwise, you can put it in one of the library directories of your
application server. However, doing this, will set the logging level
for
all applications in the container.
-Richard
Stanley, Eric wrote:
Richard,
I have set it to DEBUG, still nothing.
-Ryan
-----Original Message-----
From: Richard Yee [mailto:[email protected]]
Sent: Saturday, February 07, 2009 12:14 AM
To: [email protected]
Subject: Re: logging not working using log4j
Set the rootlog level to debug. You might have more than one log4j
file in your classpath.
-r
Sent from my iPhone
On Feb 6, 2009, at 1:25 PM, "Stanley, Eric"
<[email protected]>
wrote:
Richard,
I know its being read. As I mentioned below, all other components
of the app are using it just fine. My app, struts2 and tomcat are
both
using it without a problem. The only thing that's not logging is
iBATIS.
-Ryan
-----Original Message-----
From: Richard Yee [mailto:[email protected]]
Sent: Friday, February 06, 2009 7:53 AM
To: [email protected]
Subject: Re: logging not working using log4j
Where did you put your log4j.properties file? It needs to be in the
classpath.
Do you get any indication that it is being read at all?
-R
Stanley, Eric wrote:
Hello,
I have a Tomcat 6 container, and my java 1.5 app is using iBATIS
2.3.4 and struts2. This is my log4.properties:
# Set root logger
log4j.rootLogger=INFO, R, A1
# A1 is set to be a ConsoleAppender.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %C %x -
%m
%n
# R is a file appender
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=log/pt.log
log4j.appender.R.MaxFileSize=1MB
log4j.appender.R.MaxBackupIndex=5
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d [%t] %-5p %C %x - %m%n
# SqlMap logging configuration...
log4j.logger.com.ibatis=DEBUG
log4j.logger.com.ibatis.common.jdbc.SimpleDataSource=DEBUG
log4j.logger.com.ibatis.sqlmap.engine.cache.CacheModel=DEBUG
log4j.logger.com.ibatis.sqlmap.engine.impl.SqlMapClientImpl=DEBUG
log4j.
logger.com.ibatis.sqlmap.engine.builder.xml.SqlMapParser=DEBUG
log4j.logger.com.ibatis.common.util.StopWatch=DEBUG
log4j.logger.java.sql.Connection=DEBUG
log4j.logger.java.sql.Statement=DEBUG
log4j.logger.java.sql.PreparedStatement=DEBUG
log4j.logger.java.sql.ResultSet=DEBUG
If I understand correctly, this should spit out debug for
everything
iBATIS logs, right? Problem is, I dont get any logging for iBATIS,
but
I do for my app, tomcat, and struts2. What am I missing here?
-Ryan
This communication is the property of Qwest and may contain
confidential or privileged information. Unauthorized use of this
communication is strictly prohibited and may be unlawful. If you
have
received this communication in error, please immediately notify the
sender by reply e-mail and destroy all copies of the communication
and
any attachments.
