oh...and incidentally they actually end up increasing the throughput of your application - not the other way around. ...Either way it needs to be configurable to handle the scale of all the variously sized tapestry apps.
On 5/2/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Those are all coming from http://jakarta.apache.org/commons/pool/ . I probably should make all of these instances completely configurable though. If you create a tapestry jira issue I'll give it higher priority. On 5/2/07, Lionel Touati <[EMAIL PROTECTED]> wrote: > > Hi All, > > When runnning tapestry 4.1.2, I see lots of non application / tomcat > threads being created. It seems they're tiggered by > GenericKeyedObjectPool. Any idea of the consequence in a production > environment ? i.e, is there a way to control the number of created > threads ? > > Thanks for the answer > > L. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
