Hi Matthias, thanks for your reply. Well, brief steps how to reproduce this are already in the ticket (not much descriptive though :-). The scenario consist just from creating two JSF pages and sending them simultaneously immediately when the server has just started. As regards the patch, I've just spoken to Rich Kao who is there as an author of the comment and he said he's there by mistake actually, he said he'd just voted for this issue which happened to appear at patch available comment. I'm wondering why no one else is complaining as it seems this issue it must occur quite often.
Jakub On 24 August 2010 14:56, Matthias Wessendorf <mat...@apache.org> wrote: > HEllo Jakub, > > can you update the ticket with how to reproduce? > I'll take a look next week (currently on vacation) > > -M > > On Tue, Aug 24, 2010 at 2:48 PM, Jakub Kahovec > <jakub.kaho...@googlemail.com> wrote: > > Hi there, > > > > in our application (tomcat 6.0.28+ trinidad 1.2.13+facelets) we are time > to > > time experiencing java.lang.IllegalStateException: Factory already > available > > for this class loader, which > > seems to be happening when there are two (or more) requests sent very > > quickly to the server (which IMHO should be pretty normal in busy web > apps, > > right ?) > > I've found this problem reported in apache JIRA ( > > > https://issues.apache.org/jira/browse/TRINIDAD-195?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel > ) > > but there is no solution (it shows that there is a patch is available but > > it's not there) and the priority was changed from major or minor. > > Well, this issue seems to me quite critical unless there is something > wrong > > in our settings, which might be likely as I haven't found much references > to > > this issue (actually just one). > > So has anyone else experienced this problem or is there an easy fix or > > workaround for it ? > > > > Thanks. > > > > Jakub > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf >
