Am 29.11.2011 01:28, schrieb Zampani, Michael:
-Original Message-
From: ma...@apache.org [mailto:ma...@apache.org]
Sent: Monday, November 28, 2011 4:02 PM
To: Tomcat Users List
Subject: Re: Tomcat-7.0.23 startup deadlocks
Zampani, Michael zamp...@amazon.com wrote:
Hi,
I'm trying
Which two threads are waiting on the same lock? I don't see that in your
thread dump.
It's not obvious from the thread dump, but if I attach with jconsole, I see:
Name: main
State: WAITING on java.util.concurrent.FutureTask$Sync@6cc2a4
Name: pool-2-thread-1
State: BLOCKED on
I think you are right. When no realm is configured in server.xml and in the
context of a webapp, StandardEngine tries to set a default realm.
That is guarded by a lock, which is held by the main thread.
To work around this problem, you can define a simple realm inside the
context of your
On 29/11/2011 19:27, Zampani, Michael wrote:
I think you are right. When no realm is configured in server.xml and in the
context of a webapp, StandardEngine tries to set a default realm.
That is guarded by a lock, which is held by the main thread.
To work around this problem, you can define a
Looks like the attachments didn't all make it. Trying again
Hi,
I'm trying to upgrade an existing webapp installation from 7.0.22 - 7.0.23.
On startup, it appears to deadlock, with the threads stuck in
ContainerBase.setRealm HostConfig.deployDirectories
ContainerBase.startInternal
Zampani, Michael zamp...@amazon.com wrote:
Hi,
I'm trying to upgrade an existing webapp installation from 7.0.22 -
7.0.23.
On startup, it appears to deadlock, with the threads stuck in
ContainerBase.setRealm
HostConfig.deployDirectories
ContainerBase.startInternal
server.xml and thread dump
-Original Message-
From: ma...@apache.org [mailto:ma...@apache.org]
Sent: Monday, November 28, 2011 4:02 PM
To: Tomcat Users List
Subject: Re: Tomcat-7.0.23 startup deadlocks
Zampani, Michael zamp...@amazon.com wrote:
Hi,
I'm trying to upgrade an existing webapp installation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
On 11/28/11 7:28 PM, Zampani, Michael wrote:
Things certainly seem to stop moving forward. If I attach
JProfiler, I see two threads waiting on the same lock, but I'm not
familiar enough with the application to know if it's a 'real'
