I've filed an issue for commons-pool: https://issues.apache.org/jira/browse/POOL-122
2008/1/24, Marcus Schulte <[EMAIL PROTECTED]>: > > Once, after a few days of running, pages with pattern-based validators > would cease to work. > > > The reason, from the stacktrace, was, that commons-pool does not > health-check its one Timer (static instance in base-class), used to schedule > eviction jobs, before scheduling a new Eviction-task with it. So, if, for > some reason, the eviction thread dies, each subsequent pool-creation (and > thus validator-creation) fails with an IllegalStateException. Which happened > to us. > > I know they changed *something* with the eviction-mechanism in the latest > version. When I have any time I'll check out the latest code and file an > issue. > > 2008/1/23, Jesse Kuhnert <[EMAIL PROTECTED]>: > > > > Out of curiosity (and fear) - what is the commons-pool issue that you > > ran in to? Do you think it will effect the other areas of Tapestry > > that uses it? Do they know about it? > > > > On Jan 23, 2008 3:36 PM, < [EMAIL PROTECTED]> wrote: > > > Author: mschulte > > > Date: Wed Jan 23 12:36:08 2008 > > > New Revision: 614655 > > > > > > URL: http://svn.apache.org/viewvc?rev=614655&view=rev > > > Log: > > > fixes TAPESTRY-2071, don't use a pattern-pool for each validator > > instance. > > > > > <snipped> > > > > > > > > -- > > Jesse Kuhnert > > Tapestry / OGNL / Dojo team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Marcus Schulte > http://marcus-schulte.blogspot.com > -- Marcus Schulte http://marcus-schulte.blogspot.com
