Thanks a lot Heri.
I added jars and that solved the problem.
thanks again.
Bender Heri wrote:
>
> Hibernate uses the commons-logging framework. Your list of jars does not
> include the commons-logging.jar. I guess that hibernate when loaded the
> first time finds the commons-logging of the t
Curt Arnold wrote:
> Here are the bug reports for both Tomcat and Bugzilla, all you need to
> know are there:
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=6637
Interesting. I'm running GF2.1, latest release bundled with Netbeans
In the buzilla log, it says:
--- Additional comme
Curt Arnold wrote:
> http://logging.apache.org/log4j/companions/extras/index.html and
> http://logging.apache.org/log4j/companions/extras/download.html.
>
> Not all that big, but that was an expressed concern.
Thanks.
You really should have a link to this on the front landing page for
Log4j 1.2
On Nov 16, 2009, at 7:51 PM, Brett Randall wrote:
Hi Pat,
I don't know Glassfish as well as other containers, but according to
Wikipedia[1], "It uses a derivative of Apache Tomcat Apache_Tomcat> as
the servlet container for serving Web content"
You mentioned that this problem occurs when de
On Nov 16, 2009, at 11:17 AM, Pat Farrell wrote:
Yair Ogen wrote:
do you have log4j extras jar in your classpath?
Did know I needed it, so no
Where do I find it?
Slightly OT, but why not just include the classes in the standard
distribution? Is it that big?
http://logging.apache.org/log4
Hi Pat,
I don't know Glassfish as well as other containers, but according to
Wikipedia[1], "It uses a derivative of Apache Tomcat as
the servlet container for serving Web content"
You mentioned that this problem occurs when deploying a new WAR file - that
would agree with aforementioned likely
Jacob Kjome wrote:
> Given that it happens after a redeploy cycles, it is likely the infamous
> Tomcat bug
How can it be a Tomcat bug when it happens with Glassfish V2.1?
If I was using Tomcat, sure.
> You say you are not using Tomcat, but your server might be using Tomcat
> under the covers.
JK> Given that it happens after a redeploy cycles, it is likely the infamous
Tomcat bug (though they probably don't consider it one) where normally
static final constants are nulled by Tomcat code to work around garbage
collection bugs while leaving the classloader in-tact
+1
On Tue, Nov 17, 2009
Is this actually bombing out your code or is the exception just printed to
System.err? If the latter, then this does not constitute and "uncaught
exception... requiring immediate attention".
Given that it happens after a redeploy cycles, it is likely the infamous Tomcat
bug (though they pro
Curt Arnold wrote:
> The log4j 1.2 date and date caching code is problematic and was replaced
> in the abandoned log4j 1.3 effort...
>From the log4j FAQ, it says:
"If for any reason, log4j throws an uncaught exception, please send an
email to the log4j-user@logging.apache.org mailing list. Uncau
Yair Ogen wrote:
> do you have log4j extras jar in your classpath?
Did know I needed it, so no
Where do I find it?
Slightly OT, but why not just include the classes in the standard
distribution? Is it that big?
--
Pat Farrell
http://www.pfarrell.com/
--
I am not seeing log4j extras jar in apache-log4j-1.2.15.zip.
Where is this log4j extras jar file and is the name log4j_extras.jar?
Kay Green
11000 Westmoor Circle
Westminster, CO 80021
Office: 720 239-4639
Email: kay.gr...@mckesson.com
McKesson Provider Technologies
"Remember Life should NOT b
do you have log4j extras jar in your classpath?
On Mon, Nov 16, 2009 at 3:42 PM, Pat Farrell wrote:
> In another thread, it was suggested that I convert from using
>
> PatternLayout to EnhancedPatternLayout
>
> so I changed all occurances of PatternLayout to EnhancedPatternLayout in
> my log4j.p
Hibernate uses the commons-logging framework. Your list of jars does not
include the commons-logging.jar. I guess that hibernate when loaded the first
time finds the commons-logging of the tomcat root libraries and initializes
there, where your special logger is not found. Include a commons-logg
Yes I have only log4j.xml. No other file in class path:(
And my file is being taken bcaz it creates hibernate.log file but it remains
empty.
I also tried to removing log settings in hibernate.cfg.xml but in no luck.
I have these jars in WEB-INF\lib
09/02/2009 08:10 PM62,394 activa
In another thread, it was suggested that I convert from using
PatternLayout to EnhancedPatternLayout
so I changed all occurances of PatternLayout to EnhancedPatternLayout in
my log4j.properties file. A typical line now looks like:
log4j.appender.fnfbookfile.layout=org.apache.log4j.EnhancedPatter
Are you sure that your log configuration file is picked up? Maybe there is
annother config file on the class path which is used before yours is found.
I have no problems on Tomcat with special hibernate loggers.
Heri
-Ursprüngliche Nachricht-
Von: John2000 [mailto:johnk...@gmail.com]
Ges
We are using log4j.xml for logging. Everything is working fine except
hibernet logging. All logs files are crated but for hibernate only log file
is created and it remains empty.
My log4j.xml settings are
According to the javadocs:
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html#subAppend(org.apache.log4j.spi.LoggingEvent)
"Before actually logging, this method will check whether it is time to do a
rollover. If it is, it will schedule the next rollover tim
19 matches
Mail list logo
