My testing env setup:
tomcat 5.0.28
JAVA_OPTS=-server -Xms512m -Xmx512m
<PersistenceManager class="info.magnolia.state.berkeley.BerkeleyDBPersistenceManager" />
Here are jars we updated and added for 3.0.5:
derby-10.2.2.0.jar
jackrabbit-api-1.3.3.jar
jackrabbit-core-1.3.3.jar
jackrabbit-jcr-commons-1.3.3.jar
jackrabbit-text-extractors-1.3.3.jar
lucene-core-2.0.0.jar
magnolia-bdb-1.2.jar
PooledJNDIDatabasePersistenceManager.jar
For 3.5, I also use magnolia-bdb-1.2.jar same as above.
As for the graphs in the doc, every first graph for each mangolia version is just recording the mem at start up till after about 15 minutes with no hit at all. Page 1 for 3.0.5 and page 5 for 3.5. And you can see that mem usage was about 100M for 3.0.5 and 67M for 3.5;
Page 2 shows mem leak trend for version 3.0.5 when consistant hit starts after 15 minutes of startup till about 50 minutes after startup.
Page 6 shows mem leak trend for version 3.5 when consistant hit starts after about 15 min of startup till about 90min after startup, heap climb up to 210M. The leak certainly grows much slower than version 3.0.5, but still grows. It gets 260M after 100min
I hereby attach a screen shot Mag3.5Jackrabbit1.3.3_memGraph.JPG for mem heap usage when I tested v3.5
Our production is using 3.0.5 so the situation is really bad.
I recorded the mem leak behavious for 3.0.5 and 3.5. Heap still have a growing trend and will eventually cause problem. And the record is only under small testing environment with pretty small load. The mem leak crushed our production server which have hundreds of sites and high load and already given big heap size for JVM. Your fast fix on this issue will surely save us from a catastrophe. Looking forward to your great news on this.