Hi to everybody ,
I'm currently developing a web server application in Tomcat that uses
jackrabbit.
I've found a small issue that took me some time to solve and I would like to
tell you about it,
I do not know if it deserves to be identified as a small bug. You'll tell me.
I was frequently deploying and undeploying my application while developing and
after 4 or 5 deployment repetition Tomcat was issuing the following error
java.lang.OutOfMemoryError: PermGen
In additionTomcat was revealing leaks in my undeployed application.
I fixed the issued adding the line
<param name="shutdownOnClose" value="true"/>
in the repository.xml file like shown in this part of xml code
<PersistenceManager
class="org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager">
<param name="url"
value="jdbc:derby:${rep.home}/version/db;create=true"/>
<param name="schemaObjectPrefix" value="version_"/>
<param name="shutdownOnClose" value="true"/>
</PersistenceManager>
The problem was due to the fact that the thread derby.antiGC was not stopped.
The issue is that the repository.xml was automatically generated by Jackrabbit.
I would expect it should already include the shutdownOnClose set to true.
The Jackrabbit version I was using were different the last is 2.6.0 (and
earlier).
I tried both with Tomcat 6 and 7
Best regards,
Bernardo
--
Departamento de EstadÃstica
Universidad Carlos III de Madrid
Avda Universidad, 30
28911 Leganes (Madrid)
Spain
email: [email protected]
home: www.est.uc3m.es/bdauria
tel: + 34.91.624.8804
fax: + 34.91.624.9177
