RE: Tomcat-7.0.23 startup deadlocks

> 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 yo

RE: Tomcat-7.0.23 startup deadlocks

> 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 org.apache.catal

RE: Tomcat-7.0.23 startup deadlocks

> -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" wrote: > > >Hi, > > > >I'

RE: Tomcat-7.0.23 startup deadlocks

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.startInterna

Tomcat-7.0.23 startup deadlocks

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 attached. Note that I do not define any s in s

RE: Cache-Control headers not being added to secure requests

uests On 23/08/2011 19:09, Zampani, Michael wrote: > Chris, > > Doesn't the entire securePagesWithPragma flag fail the robustness > principle? It's specifically there to fix caching issues with IE, > similar to the issue we're now seeing. > > I understand ho

RE: Cache-Control headers not being added to secure requests

nt: Tuesday, August 23, 2011 6:48 AM To: Tomcat Users List Subject: Re: Cache-Control headers not being added to secure requests -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael, On 8/22/2011 5:39 PM, Zampani, Michael wrote: > However, I'm still confused about >> - {request.isSec

RE: Cache-Control headers not being added to secure requests

ark Thomas [mailto:ma...@apache.org] Sent: Wednesday, August 17, 2011 12:34 AM To: Tomcat Users List Subject: Re: Cache-Control headers not being added to secure requests On 16/08/2011 22:20, Zampani, Michael wrote: > It was my understanding that the fix for IE was just the > securePagesWithP

RE: Cache-Control headers not being added to secure requests

to secure requests On 08/16/2011 03:57 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael, > > On 8/16/2011 4:42 PM, Zampani, Michael wrote: >> I don't understand why it was ever present, though. Does anybody >> know why

Cache-Control headers not being added to secure requests

Hi, CLN 1126273 http://svn.apache.org/viewvc?view=revision&revision=1126273 Seems to have disabled the automatic addition of the cache-control and pragma response headers on secure constrained pages. The initial revision of this file(at least the oldest copy I could find) had this check http://