<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hibernate and Logging</title>
	<atom:link href="http://www.basilv.com/psd/blog/2008/hibernate-and-logging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging</link>
	<description></description>
	<lastBuildDate>Wed, 16 May 2012 04:03:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Basil Vandegriend</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-95195</link>
		<dc:creator>Basil Vandegriend</dc:creator>
		<pubDate>Thu, 30 Jul 2009 04:22:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-95195</guid>
		<description>@Bill, the last portion of each entry represents the elapsed duration (in milliseconds) since the application started (more accurately, I believe, when Log4J was initialized.) I use this both as an uptime statistic and as a way to compare elapsed time between two log entries.

This does NOT represent query duration, and I&#039;m not aware of an easy way to log this. One option that comes to mind is to use aspects to weave in before/after method advice on either Hibernate query methods directly or on methods in your Data Access Objects (DAOs) to measure and log the performance.</description>
		<content:encoded><![CDATA[<p>@Bill, the last portion of each entry represents the elapsed duration (in milliseconds) since the application started (more accurately, I believe, when Log4J was initialized.) I use this both as an uptime statistic and as a way to compare elapsed time between two log entries.</p>
<p>This does NOT represent query duration, and I&#8217;m not aware of an easy way to log this. One option that comes to mind is to use aspects to weave in before/after method advice on either Hibernate query methods directly or on methods in your Data Access Objects (DAOs) to measure and log the performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-95169</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 29 Jul 2009 15:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-95169</guid>
		<description>In your sample log snippet, each entry ends with &quot;[44513 ms]&quot;.  What does that represent?  If that is how long the query took to run (although I&#039;d hope it didn&#039;t take 44 seconds), or you know how to log query duration, please post.</description>
		<content:encoded><![CDATA[<p>In your sample log snippet, each entry ends with &#8220;[44513 ms]&#8220;.  What does that represent?  If that is how long the query took to run (although I&#8217;d hope it didn&#8217;t take 44 seconds), or you know how to log query duration, please post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul G</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-89783</link>
		<dc:creator>Paul G</dc:creator>
		<pubDate>Sat, 02 May 2009 06:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-89783</guid>
		<description>Jcl &quot;smart&quot; classloader scanning cause no end of problems in servers. I would really suggest looking at sl4j which may help with everyones logging in server issues.</description>
		<content:encoded><![CDATA[<p>Jcl &#8220;smart&#8221; classloader scanning cause no end of problems in servers. I would really suggest looking at sl4j which may help with everyones logging in server issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul G</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-89782</link>
		<dc:creator>Paul G</dc:creator>
		<pubDate>Sat, 02 May 2009 06:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-89782</guid>
		<description>If you use sl4j you get none of the websphere problems. Sl4j provides a bridge so it will work with jcl and then you can use log4j or the new replacement logback.</description>
		<content:encoded><![CDATA[<p>If you use sl4j you get none of the websphere problems. Sl4j provides a bridge so it will work with jcl and then you can use log4j or the new replacement logback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sasha</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-84128</link>
		<dc:creator>Sasha</dc:creator>
		<pubDate>Thu, 05 Mar 2009 04:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-84128</guid>
		<description>Thank you Basil for a good tip.

I&#039;ve got a slightly different problem where Hibernate 3.2.6.ga does not log &quot;debug&quot; messages when running in Tomcat 5.5 (which in its turn runs in JBoss 4.0.3). I&#039;ve tried creating commons-logging.properties but it did not log debug messages either.

However, when I run the same code in a standalone environment, I&#039;ve got all debug messages coming from hibernate.

All suggestions would be greatly appreciated.</description>
		<content:encoded><![CDATA[<p>Thank you Basil for a good tip.</p>
<p>I&#8217;ve got a slightly different problem where Hibernate 3.2.6.ga does not log &#8220;debug&#8221; messages when running in Tomcat 5.5 (which in its turn runs in JBoss 4.0.3). I&#8217;ve tried creating commons-logging.properties but it did not log debug messages either.</p>
<p>However, when I run the same code in a standalone environment, I&#8217;ve got all debug messages coming from hibernate.</p>
<p>All suggestions would be greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basil Vandegriend</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-82568</link>
		<dc:creator>Basil Vandegriend</dc:creator>
		<pubDate>Mon, 23 Feb 2009 13:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-82568</guid>
		<description>Thanks Peter! I made the fix.</description>
		<content:encoded><![CDATA[<p>Thanks Peter! I made the fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Kelley</title>
		<link>http://www.basilv.com/psd/blog/2008/hibernate-and-logging/comment-page-1#comment-82545</link>
		<dc:creator>Peter Kelley</dc:creator>
		<pubDate>Mon, 23 Feb 2009 10:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/hibernate-and-logging#comment-82545</guid>
		<description>I think that that log implementation class should be org.apache.commons.logging.impl.Log4JLogger (upper case J)</description>
		<content:encoded><![CDATA[<p>I think that that log implementation class should be org.apache.commons.logging.impl.Log4JLogger (upper case J)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

