On 31.07.2011 20:45, Mark Thomas wrote: > On 31/07/2011 19:29, Mark Thomas wrote: >> On 31/07/2011 18:57, Rainer Jung wrote: >>> Any idea what's happening here? >> >> Not yet, although it is probably my fault :) >> >> I can reproduce this, looking in more detail now... > > The problem is that calling isSingleThreadModel (triggered by reading > the JMX attributes) triggers creation of an instance that is then thrown > away but the instanceInitialized flag is set. When the first request is > received a new instance is created but not initialized. > > I#ll see if I can come up with a patch. I cam also see a couple of other > ways this could go wrong. I'll try and fix those too.
Thank's for investigating, interesting explanation. Unfortunately it is not completely unlikely, that a jmxproxy dump is done early after startup. e.g. as part of monitoring or availability check. Found it while testing tcnative ... Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
