-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teemu,
On 3/10/2011 12:12 PM, Teemu Kivimäki wrote:
> Found out that it was DWR 3.0 rc1 causing this.. So not really Tomcat
> related,
> although the log messages didn't really give any hints towards this, but
> thats
> just life :)
Tomcat can on
Mikolaj Rydzewski ceti.pl> writes:
>
>
> On Thu, 10 Mar 2011 12:36:14 + (UTC), Teemu Kivimäki
> gmail.com> wrote:
> > Was this ever resolved? I have the exact same problem when shutting
> > down tomcat.
> > Not critical but pretty annoying.
>
> For proper webapplications problem is no
On Thu, 10 Mar 2011 12:36:14 + (UTC), Teemu Kivimäki
wrote:
Was this ever resolved? I have the exact same problem when shutting
down tomcat.
Not critical but pretty annoying.
For proper webapplications problem is non existent one.
Webapp should terminate any threads it created. It's not
Was this ever resolved? I have the exact same problem when shutting down
tomcat.
Not critical but pretty annoying.
Cheers,
Teemu
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pix,
On 12/7/2010 5:13 AM, pix_siro wrote:
> # give application 5 seconds to stop itself
> sleep 2
Fail
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEAREC
On 12/7/10 10:38 AM, pix_siro wrote:
> GRAVE: The web application [/OverEncrypt] appears to have started a thread
> named [pool-1-thread-1] but has failed to stop it. This is very likely to
> create a memory leak.
>
> I think the second GRAVE error is that significant.
That'll be the one.
Ensure
ss, not the specific Java thread. Take a thread dump to
>>> see what threads are still running. You want the non-daemon one.
>>>
>>> Mark
>>>
>>> -
>>> To unsubscribe, e-mail: users-
On 12/7/10 10:13 AM, pix_siro wrote:
>
> I solved writing a simple script to shutting down tomacat and kill the java
> process:
>
> # stop tomcat
> su - primelife -c "/usr/local/apache-tomcat-7.0.4/bin; ./shutdown.sh
>> /dev/null 2>&1"
>
> # give application 5 seconds to stop itself
> sleep 2
>
see what threads are still running. You want the non-daemon one.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
On 12/3/10 6:59 PM, Mark Thomas wrote:
> On 03/12/2010 18:36, pix_siro wrote:
>>
>> Hi all,
>> I'm working on Ubuntu 9.10, I have implemented a Java application and I have
>> installed it on Tomcat 7.0.4 with a WAR file. When I shut down Tomcat with
>> the command ./shutdown.sh, a java thread remai
On 03/12/2010 18:36, pix_siro wrote:
>
> Hi all,
> I'm working on Ubuntu 9.10, I have implemented a Java application and I have
> installed it on Tomcat 7.0.4 with a WAR file. When I shut down Tomcat with
> the command ./shutdown.sh, a java thread remains open. Notice that
> application have a con
r=/usr/lib/apache-tomcat-7.0.4/temp
org.apache.catalina.startup.Bootstrap start
--
View this message in context:
http://old.nabble.com/java-thread-open-after-Tomcat-shutting-down-tp30366568p30366568.html
Sent from the Tomcat - User mailing list archive at
12 matches
Mail list logo
