You might also want to consider disabling tag-pooling in $CATALINA_HOME/conf/web.xml, at least as a start. This will give you a lifecycle that looks more like TC 3.x.
On at least one of my applications, disabling tag-pooling made a huge difference in performance (it basically changed it from a dog to a cat ;). However, your mileage may very depending on what your tags actually do. The trade-off depends on whether it cost more to GC or to manage the pools. "Will Hartung" <[EMAIL PROTECTED]> wrote in message 075f01c2a215$5f21aa90$01000001@Will">news:075f01c2a215$5f21aa90$01000001@Will... > In out port of code from 3.2 to 4.1, we're encountering some problems with > how Tomcat reuses our tags. > > I looked at the code, and TagHandlerPool does not call the 'release' method > of the tag unless the pool is full (this is within the reuse method). > > My question, then, where is the appropriate place to re-initialize internal > properties for a jsp tag? > > The life cycle diagram doesn't really have a "precise" place to reinitialize > the content to their defaults, so I'm curious where others are putting this > kind of code. > > Regards, > > Will Hartung > ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
