David Rees wrote:I just entered this bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22096
I can reproduce it. Right now, I can't isolate the root cause.
Surprised it wasn't caught before the release.
I doubt this was introduced between 4.1.26 and 4.1.27, so there should have been plenty of time to catch it indeed.
One problem is that the reload mechanism is overly complex, so historically, there has been a significant amount of bugs in it. In 5.0.x, all the custom logic is now replaced by stop + start (which is marginally slower, but is *a lot* simpler).
Not being familiar with the workings of the manager app, but if it's a lot easier implement a simple stop/start the context when reloading, why not do so in 4.1.x like TC 5?
I doubt anyone will notice a tiny performance hit when doing reloads, especially since it's broken anyway. ;-)
Wish I had time to dig into Tomcat internals.
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
