DO NOT REPLY [Bug 30489] - removeAttribute: Session already invalidated

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37929] - invalidated session causes pageContext methods to fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37934] - Tomcat does not follow SRV 12.8.3 regarding empty auth-constraint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37934] New: - Tomcat does not follow SRV 12.8.3 regarding empty auth-constraint

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37933] New: - Bugs in Tomcat

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37929] - invalidated session causes pageContext methods to fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26372] - java.lang.ThreadDeath when trying to reload an application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26372] - java.lang.ThreadDeath when trying to reload an application

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 30489] - removeAttribute: Session already invalidated

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37929] - invalidated session causes pageContext methods to fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37929] New: - invalidated session causes pageContext methods to fail

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [VOTE] Tomcat v5.5.14 Stability

got it, I would have placed that in the body, with the payload info instead of altering the protocol. but I am glad you got it fixed. I have been too busy to work on the tomcat project this year, and it sounds like it will be a little while before 5.5 reaches the stability for us to move to it.

Improving memory efficiency

Hi there, while hunting down a memory leak (it turned out that some servlets didn't release PageContexts after use) I came across some places in tomcat which are a bit memory inefficent. (I'm talking about Tomcat 5.5 SVN as of tuesday or yesterday.) The root cause (but not the problem) is that P

Re: [VOTE] Tomcat v5.5.14 Stability

Compression is optional for cluster messages. Very big message can be set a flag that need compression. This flag is the header extension. Peter Filip Hanik - Dev Lists schrieb: interesting, why did the protocol header need to change? that is so old proven code. didn't know there was anything

Re: [VOTE] Tomcat v5.5.14 Stability

interesting, why did the protocol header need to change? that is so old proven code. didn't know there was anything wrong with it. Filip Peter Rossbach wrote: Hey Filip, it was a new one and is only inside >5.5.10 source. After I have change the message header format the bug is comes in. N

DO NOT REPLY [Bug 37918] New: - EL cannot find valid getter from object when using some inheritance

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [VOTE] Tomcat v5.5.14 Stability

Hey Filip, it was a new one and is only inside >5.5.10 source. After I have change the message header format the bug is comes in. Now it is fixed. Every help is welcome. Peter Filip Hanik - Dev Lists schrieb: out of curiosity, I haven't yet been too much on the 5.5 platform, is this a new b

Re: [VOTE] Tomcat v5.5.14 Stability

out of curiosity, I haven't yet been too much on the 5.5 platform, is this a new bug introduced, cause we have never seen it on 5.0 Filip Peter Rossbach wrote: Hey! I have changed the cluster message header format long time ago 5.5.10. In some situations TCP Stack split the message, then the