[infinispan-issues] [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Fri Jan 14 08:45:49 EST 2011


    [ https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575583#comment-12575583 ] 

Galder Zamarreño commented on ISPN-868:
---------------------------------------

Did you get this error immediately or after a while?

Hmmm, I've just built 4.2.x branch and installing a 4.2.1-SNAPSHOT in my own repo and seems to go fine:

[2011-41-14 02:41:04.702,  2059]WARN [main](arjunaI18NLoggerImpl.java:523) - ARJUNA-12130 Name of XA node not defined. Using Arjuna:56565
[2011-41-14 02:41:07.246,  4603]INFO [main](FillCartonTest.java:71) - 100 kiwis in the carton
[2011-41-14 02:41:09.199,  6556]INFO [main](FillCartonTest.java:71) - 200 kiwis in the carton
[2011-41-14 02:41:10.964,  8321]INFO [main](FillCartonTest.java:71) - 300 kiwis in the carton
....

Can you try cloning the git repo I mentioned, switching to 4.2.x and build it without running tests (http://community.jboss.org/wiki/InfinispanandMaven) and see if it works?

Maybe a new snapshot needs uploading, let me upload a new one.

> Running out of memory using Infinispan after adding a small number of entities
> ------------------------------------------------------------------------------
>
>                 Key: ISPN-868
>                 URL: https://issues.jboss.org/browse/ISPN-868
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.2.0.Final
>         Environment: JBossJTA 4.14.0/Hibernate 3.6.0.Final/Spring 3.0.5
>            Reporter: Tom Waterhouse
>            Assignee: Galder Zamarreño
>             Fix For: 4.2.1.Final
>
>         Attachments: ISPN-868-1.zip, ISPN-868.zip, ispn686-error-galder.txt, jconsole-mbeans.JPG, jconsole-memory-view.JPG, Memory leak.jpg, test-progress.JPG
>
>
> While running a load test data builder for our application we ran out of memory very quickly.  A simple test case (attached) was created to duplicate the issue.  We found running the simple test case illustrates that Infinispan uses a large amount of heap space.
> As a reference the same test was run using EHCache 2.2.  Memory usage was much lower; we never ran out of heap space.  Note that EHCache was used as a reference only, our goal is to go to production with Infinispan.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list