I am quite sure it is a problem with the webapp (including jackrabit and its dependencies). If the appserver cannot completely dismiss the classloader used to load the app than on consecutive redeployments the problem wll still occur (probably later due to the JVM settings).
./alex -- .w( the_mindstorm )p. --- (http://themindstorms.blogspot.com) On 7/3/06, Edgar Poce <[EMAIL PROTECTED]> wrote:
Hi Thomas, not sure but I don't think this problem is caused by jackrabbit. I had this problem with an application and increasing this value solved the issue, the application has been running fine in a pre production environment for a few months. br, edgar On 7/3/06, Thomas Buffagni <[EMAIL PROTECTED]> wrote: > > Hi! > i think that the last solution will work but only postpone the problem... > I suppose that some singleton aren't released in jackrabbit, it's possibile? > > > > -- > View this message in context: http://www.nabble.com/PerGen-Exception-in-RepositoryImpl.create-tf1883463.html#a5151788 > Sent from the Jackrabbit - Users forum at Nabble.com. > >
