2 Replies Latest reply on Jan 5, 2012 5:38 AM by Rob Beer

    JBoss-6.0.0.Final failing to start with Infinispan version 4.2.1.FINAL

    Rob Beer Newbie

      I've been load testing JBoss 6 by simulating a high number of client requests.  The data I am requesting is cached for a minute, so I would expect JBoss to handle the requests with ease.  At first this is the case, but after less than 50,000 requests things slow to a crawl, CPU usage increases significantly (GC I guess) and eventually JBoss runs out of memory.  Increasing the memory allocation produces the same outcome, it just takes a little longer to happen.


      If I turn caching off JBoss performs as expected albeit slower as each request is hitting the database.  The memory and CPU usage stays relatively constant.


      I believe this is related to bug https://issues.jboss.org/browse/ISPN-868, but when I replace:


      C:\platforms\jboss-6.0.0.Final\server\all\lib\infinispan-core.jar (version 4.2.0.FINAL)




      C:\platforms\jboss-6.0.0.Final\server\all\lib\infinispan-core.jar (version 4.2.1.FINAL)


      I get the following error in boot.log (full trace attached):


      "Eviction maxEntries value cannot be less than or equal to zero if eviction is enabled"


      None of my maxEntries in jboss-6.0.0.Final\server\all\deploy\cluster\infinispan-cache-registry.sar\infinispan-configs.xml are less than or equal to zero.  In fact removing all named caches with a maxEntries reference still produces this error.


      My setup is:


      Java 1.6.0_24


      Hibernate 3.6.0.Final

      Hibernate Commons Annotations 3.2.0.Final

      Infinispan 4.2.1.FINAL

      Single JBoss node running on Windows XP Pro




      1) Do any other jars or property files need updating in order for JBoss 6 to work with Infinispan 4.2.1.FINAL?

      2) Are there any other locations where maxEntries is defined and therefore need altering?