tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34222] - TagHandlerPool does not call release on pooled tags
Date Tue, 26 Feb 2008 20:57:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<https://issues.apache.org/bugzilla/show_bug.cgi?id=34222>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

https://issues.apache.org/bugzilla/show_bug.cgi?id=34222


tsharif@farecast.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |
             Status|RESOLVED                    |REOPENED
                 CC|                            |tsharif@farecast.com




------- Additional Comments From tsharif@farecast.com  2008-02-26 12:57 -------
How is this not a bug. The JSP Spec explicitly states that release should be called.

http://java.sun.com/products/jsp/tutorial/TagLibraries18.html#62842

The consumer of JSP should not expereince any difference whether pooling is
enabled or not.

If the pool size is N, it seems like the use of N+1 tag (in which case release
will be called) has a different behavior than the tags 1..N.

This could be a real problem a JSP serving requests for multiple users.

Please advise,

Thanks,
Talib Sharif
farecast.com
tsharif@farecast.com

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message