I've just hit the same problem (with Tomcat 5.5.4). antiJARLocking/antiResourceLocking didn't help. I tried to set 1 of those attributes to context on appplication level (in meta-inf directory) as well on global level (in context.xml in tomcat/conf directory).
Does anyone know if there is a solution? Btw, I noticed that I have this problem only with JSP. If I move code from JSP to a servlet then no locking occurs. > > Thank you for pointing out these redundant attributes. I applied these > changes > > > to the context, but got the same results. If I have time, I'll put > > > together > > > a small application that demonstrates the problem and send that to you. > > > > If the issue is real, then I think there will be someone to provide a > > webapp. > > > > Yes, and that person's me! :) I just sent a test WAR that demonstrates the > problem directly to your Gmail address. As I'm using Gmane, and Gmane does > not > allow attachments, I could not attach the WAR to this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
