Greg Wilkins wrote: > > Ouch - that does not look good! > > The > java.lang.IllegalStateException: Not EDITABLE > exception is thrown when something tries to modify a request > when it is not in a modifiable state. This is normally when > the header has already been committed when sending the response. > > However, you are getting this while reading a request?!?!?
It could be the Rice code. They do all sorts of non-standard things (that is the nice way of putting it). > There is either a nasty threading bug in Jetty - or somebody is holding > onto a request object and/or passing it to another thread. Jetty > recycles requests objects, so requests cannot be given to other threads. > > Judging from the line numbers in your stack trace, I think you have > the Jetty-4.1.D2 version. Jules, have you upgraded 3.0 to use > Jetty-4.1.B0 yet? I thought Jules had, so Dain - you may want to > do a cvs update? I'll update later tonight. It has been a while. > Not that B0 has any fixes for any no issues like this? > > What is the exact sequence of events? Do these exceptions appear > in the order that your presented? Yes. The IllegalStateException happens all the time under high load. > PS. I'm going away tomorrow until next Tuesday - how urgent is this? Not urgent at all. I'm just trying to reproduce the results of the Rice study. I'll integrate this into the test suite later so other can run it easily. BTW, they have new test on 3.0 and we are as fast as optimized Jonas, but we tank at 440 users (think it is the database pooling code). -dain ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
