This keeps coming up. According to the spec, doStartTag, doEndTag, etc
can be called multiple times between calls to reset(). This happens on
Tomcat if you are doing tag pooling. Some containers instead comply to
what people sometimes think is going on in that they call reset(),
doStartTag, doEn
So to wrap this one up, the problem turned out to be a tag that wasn't
resetting its state correctly -- or rather, was only doing so in its
reset() method. All was fine with tag pooling turned off but with it on
the tag could wind up with inconsistent internal state. Cleaning up in
doEndTag() s
Sure, I'll update Bug# 21611 as I get more details.
L.
Bill Barker wrote:
I just got a ton of these while doing a stress-test to try and get another
bug to crawl out from under it's rock ;-). I believe that there is a bug
here somewhere, but I'm currently chasing bug #1. If your server logs ar
I just got a ton of these while doing a stress-test to try and get another
bug to crawl out from under it's rock ;-). I believe that there is a bug
here somewhere, but I'm currently chasing bug #1. If your server logs are
more interesting than mine (which don't say much more than NPE at ...),
cou
Agreed :-) But understanding the life cycle of CoyoteRequestFacade may
make it easier to do so. There's nothing particularly funky going on in
the code that's exhibiting the problem so I don't know yet what I can
pare away. I'm trying to get a local build of Tomcat set up so I can add
some trac
Howdy,
The best thing is to come up with a way for us to reproduce it. The
simplest, most direct way to get the exception.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Laurie Harper [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, September 09, 2003 6:17 PM
>To: [EMAIL P
