Just a quick update on these several threads of Tomcat 7 oddball
exceptions. It looks to be as Chuck believed that it was a coding error
on our end that was causing this. In particular, it was the no-no
misuse of instance variables in a controlling servlet.
Thanks for everyone's help!
David
On 5/2/2012 2:41 PM, Caldarale, Charles R wrote:
Look carefully at the code in your webapp(s) for issues like the ones
described in an earlier response.
Has anybody seen this?
Lots of times - and it's _always_ been a problem in a webapp.
- Chuck
I hope my comment about our session trackin
> From: David Wall [mailto:d.w...@computer.org]
> Subject: Tomcat 7 - .ApplicationDispatcher invoke - Cannot create a session
> after the response has been committed
> It really seems like Tomcat is confusing sessions or the like
> when the load gets high, but not sure how to
Here's another odd exception we are receiving on Tomcat 7.0.26 when
doing load testing.
When this exception occurs, our code is basically calling:
response.encodeURL(url);
It's in a FORM tag we created that is defined on a JSP page that should
already have a session object created by:
<%@p
