<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Tomcat Restarts: Is it a Big Deal?</title>
	<atom:link href="http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/</link>
	<description>Musings from the MuleSoft Experts</description>
	<lastBuildDate>Wed, 08 Sep 2010 22:06:52 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sateesh Narahari</title>
		<link>http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/comment-page-1/#comment-4055</link>
		<dc:creator>Sateesh Narahari</dc:creator>
		<pubDate>Fri, 22 Jan 2010 19:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mulesoft.org/?p=1687#comment-4055</guid>
		<description>Hi Matt, 

Thank you for your comment. I assume the solution you described is working good for your environment.  

Couple of things to consider: 1. Give Tomcat a chance to shutdown gracefully before issuing a kill -9.    2.  Auto restarts based on a condition - do you find that you get false positives and do restarts when it was just a long running request for the app?. 

With Tcat Server, it is an administrator&#039;s decision to restart Tomcat server and the logic in Tcat Server does give Tomcat a chance to shutdown properly.  Give it a shot for few of your test Tomcat servers and see how that works for you. ( you can use it for free in dev and pre-production).

Best Regards,
Sateesh</description>
		<content:encoded><![CDATA[<p>Hi Matt, </p>
<p>Thank you for your comment. I assume the solution you described is working good for your environment.  </p>
<p>Couple of things to consider: 1. Give Tomcat a chance to shutdown gracefully before issuing a kill -9.    2.  Auto restarts based on a condition &#8211; do you find that you get false positives and do restarts when it was just a long running request for the app?. </p>
<p>With Tcat Server, it is an administrator&#8217;s decision to restart Tomcat server and the logic in Tcat Server does give Tomcat a chance to shutdown properly.  Give it a shot for few of your test Tomcat servers and see how that works for you. ( you can use it for free in dev and pre-production).</p>
<p>Best Regards,<br />
Sateesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/comment-page-1/#comment-4032</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 15 Jan 2010 21:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mulesoft.org/?p=1687#comment-4032</guid>
		<description>We dozens of applications on hundreds of Tomcat instances. Our solution is to run them (and any other Java  deamon) inside a Java Service Wrapper. When an application gets into an instable state (no response according to some criteria, out of memory etc.), the service wrapper simply restarts it. Monitoring will pick this up so we can fix the problem, but for the time being the servers keep running.</description>
		<content:encoded><![CDATA[<p>We dozens of applications on hundreds of Tomcat instances. Our solution is to run them (and any other Java  deamon) inside a Java Service Wrapper. When an application gets into an instable state (no response according to some criteria, out of memory etc.), the service wrapper simply restarts it. Monitoring will pick this up so we can fix the problem, but for the time being the servers keep running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sateesh Narahari</title>
		<link>http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/comment-page-1/#comment-4031</link>
		<dc:creator>Sateesh Narahari</dc:creator>
		<pubDate>Fri, 15 Jan 2010 21:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mulesoft.org/?p=1687#comment-4031</guid>
		<description>This depends on the server on which Tomcat is running and as you say number of applications as well. 

We have seen as short as 1.5 second to probably 20 seconds or so. The advantage of using a solution like Tcat Server is that you are not checking process state repeatedly, as you can just select Restart and Tcat Server will do the required work to reliably restart the Tomcat instance.</description>
		<content:encoded><![CDATA[<p>This depends on the server on which Tomcat is running and as you say number of applications as well. </p>
<p>We have seen as short as 1.5 second to probably 20 seconds or so. The advantage of using a solution like Tcat Server is that you are not checking process state repeatedly, as you can just select Restart and Tcat Server will do the required work to reliably restart the Tomcat instance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loki</title>
		<link>http://blogs.mulesoft.org/tomcat-restarts-is-it-a-big-deal/comment-page-1/#comment-4030</link>
		<dc:creator>Loki</dc:creator>
		<pubDate>Fri, 15 Jan 2010 14:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mulesoft.org/?p=1687#comment-4030</guid>
		<description>How long does a restart (shutdown and startup) take under ideal circumstances. What effect does the number of applications (Mules?) have on this time?</description>
		<content:encoded><![CDATA[<p>How long does a restart (shutdown and startup) take under ideal circumstances. What effect does the number of applications (Mules?) have on this time?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
