Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
>> But anyhow, Servlet instances are _recycled_. Once a servlet
>> instance is done processing a request, it will be reused for a
>> future request. <snip> - Geoff
> Isn't this only true if you've set CacheServletInstances to a non zero
> value? It may be a quibbling point, but if you set this value to 0,
> it shouldn't be recycling servlet instances anymore, right?
> Its possible I misunderstand the meaning behind that configuration
> value, but thats the meaning I've been assuming. Depending upon how
> heavy your traffic is or how large your servlet classes are some
> people might not be switching that value to non zero in a production
> version of their application.
> Admittedly, this doesn't in any way detract the from the rest of what
> you said. I just wanted to get clarification on servlet recycling and
You are correct. CacheServletInstances does default to True in the config
file, so in the absence of any changes to the configuration, servlets will
I believe you can also override this behavior on a servlet by servlet basis
by providing a "canBeReused" method or something along those lines. So if
you need one particular servlet to be constructed anew on every request,
there's a way to do that.