https://bz.apache.org/bugzilla/show_bug.cgi?id=59737
Craig Lynch <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #2 from Craig Lynch <[email protected]> --- Could you please elaborate? The only items in the stacktrace are either in Tomcat or java concurrency code. What appears to be happening ins Tomcat is trying to release a lock that's already been released. It seems unlikely that there's a configuration I could be setting that would cause Tomcat to try to do that. I've actually been working on this problem for well over a month now, and I do have more information that points towards Tomcat -- the TaskQueue builds up large lists of runnables when the sites are in the bad state, and I'm able to reproduce very similar issues by making the queue behave badly in different ways. As I mentioned, I'm happy to provide additional information, I'm just not sure what's useful to the project. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
