Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.br;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding;
  b=2LnhzvYq6X6a+QGeE4INEQGzmYXoLxap7d/IpI0m72sCSoUW7AcbSdkbJ2yeNYtwfn4tMOa3UeCA9lDNRoNXNXqrad/GHRgPgMjPkViOXnCw4DyRcm9eOLUPWjCXV+eUlGejGlk+jUcpYIChnEPEGZlFaUHgPqq4GurFHCXktAM=
  ;
Subject: Re: POST request hangs hup
From: Daniel Henrique Alves Lima <email_daniel_h@yahoo.com.br>
To: Tomcat Users List <users@tomcat.apache.org>
In-Reply-To: <e0f9b3820907021440k452cafa8v58555192e377eb60@mail.gmail.com>
References: <e0f9b3820907021440k452cafa8v58555192e377eb60@mail.gmail.com>
Content-Type: text/plain
Date: Thu, 02 Jul 2009 19:20:03 -0300
Message-Id: <1246573203.7681.13.camel@magnaopus.no-ip.biz>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit


On Thu, 2009-07-02 at 23:40 +0200, Ivan Longhi wrote:
> Hi,

	Hi, Ivan.

> I'm running tomcat 6.0.18 with java 1.6.0_13 on a linux box.
> The only webapp deployed is Sun OpenSSO (http://www.opensso.org) built from
> source (20090930).
> Sometimes a tomcat thread hangs hup while serving a POST request
> (/UI/Login): monitoring tomcat
> status I see the processing time grows and the thread never ends. When this
> happens I am not able to shutdown
> tomcat with shutdown.sh and I need to kill -9 the java process.
> I think it is not a problem of memory exausted because if I run "top" the
> memory usage by java process
> is ok (a few hundreds MB despite CATALINA_OPTS="-Xmx6048M") but the cpu
> usage is 100%.

	I think could be anything: An infinite loop in your app, a database (or
other resource) deadlock, any intensive db query (with a really long
transaction timeout).
	For instance, last month we've adopted a new Transaction Manager that
keeps some threads (non daemons) running and prevents Tomcat of doing a
"clean" stop. Now i'm "forcing" Tomcat to stop after 5 minutes waiting. 

	My (little) experience tells me that in cases like this, your app is
more guilt than your Application Server/Web Container. But it is just my
2 cents.


	[]'s


> 
-- 
"If there must be trouble, let it be in my day, 
 that my child may have peace."

Thomas Paine


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org