[JBoss JIRA] Created: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
2:02 a.m.
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: Manik Surtani
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
2:09 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: ISPN-868.zip
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: Manik Surtani
Attachments: ISPN-868.zip
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
2:11 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Steps to Reproduce: Use the attached test case. Either FillCartonTest.java or
FillContainerTest.java can be used. FillCartonTest.java uses the simpler Hibernate
entities. (was: Use the attached test case.)
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: Manik Surtani
Attachments: ISPN-868.zip
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
11:52 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-868:
-------------------------------
Fix Version/s: 4.2.1.Final
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.zip
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
11:52 a.m.
New subject: [JBoss JIRA] Assigned: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani reassigned ISPN-868:
----------------------------------
Assignee: Galder Zamarreño (was: Manik Surtani)
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.zip
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
10:30 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
Thanks for the report and the test case. Unfortunately I've imported the test into my
IDE and cannot run the tests. See attached errors. Do they ring a bell?
Secondly, I have doubts that you're comparing the same here. The Infinispan
configuration that you're using has nothing to do with the default and recommended one
(https://github.com/hibernate/hibernate-core/blob/3.6/cache-infinispan/src...).
In fact, I think this is key cos the default cache config has no eviction and some of your
entities have "pastry" as region name but there's no such cache in the
infinispan config, and because your default cache has no eviction/expiration (the ehcache
does have eviction/expiration settings in default cache), these caches would grow without
limit.
So, let's go back to step one. First of all, based on what I saw in your config, you
don't need an infinispan.xml at all. From an Infinispan perspective, here're
different options you can use to config Infinispan 2LC:
Option 1. If you remove the region attribute settings of your @Cache annotations, you can
use something like this (Box and Bag entities not included):
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.max_entries"
value= "1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Egg.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 2. Still with no regions defined in @Cache, the configuration in Option 1 can be
further simplified like this so that all entities have the same eviction/expiration
settings:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.entity.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.entity.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 3. If you still wanna keep your @Cache region definitions, based on the
region's in the actual code and not the infinispan.xml file, this would look something
like this:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.container.eviction.strategy"
value= "LRU" />
<entry key="hibernate.cache.infinispan.container.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.pastry.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.pastry.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.carton.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.carton.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.egg.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.kiwi.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Finally, all this is in http://community.jboss.org/docs/DOC-14105
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.zip
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
10:32 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño edited comment on ISPN-868 at 1/12/11 4:31 AM:
----------------------------------------------------------------
Thanks for the report and the test case. Unfortunately I've imported the test into my
IDE and cannot run the tests. See attached errors. Do they ring a bell?
Secondly, I have doubts that you're comparing the same here. The Infinispan
configuration that you're using has nothing to do with the default and recommended one
(https://github.com/hibernate/hibernate-core/blob/3.6/cache-infinispan/src...).
In fact, I think this is key cos the default cache config has no eviction and some of your
entities have "pastry" as region name but there's no such cache in the
infinispan config, and because your default cache has no eviction/expiration (the ehcache
does have eviction/expiration settings in default cache), these caches would grow without
limit.
So, let's go back to step one. First of all, based on what I saw in your config, you
don't need an infinispan.xml at all. From an Infinispan perspective, here're
different options you can use to config Infinispan 2LC:
Option 1. If you remove the region attribute settings of your @Cache annotations, you can
use something like this (Box and Bag entities not included):
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.max_entries"
value= "1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Egg.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 2. Still with no regions defined in @Cache, the configuration in Option 1 can be
further simplified like this so that all entities have the same eviction/expiration
settings:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.entity.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.entity.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 3. If you still wanna keep your @Cache region definitions, based on the
region's in the actual code and not the infinispan.xml file, this would look something
like this:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.container.eviction.strategy"
value= "LRU" />
<entry key="hibernate.cache.infinispan.container.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.pastry.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.pastry.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.carton.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.carton.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.egg.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.kiwi.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Finally, this is explained in http://community.jboss.org/docs/DOC-14105
was (Author: galder.zamarreno(a)jboss.com):
Thanks for the report and the test case. Unfortunately I've imported the test into
my IDE and cannot run the tests. See attached errors. Do they ring a bell?
Secondly, I have doubts that you're comparing the same here. The Infinispan
configuration that you're using has nothing to do with the default and recommended one
(https://github.com/hibernate/hibernate-core/blob/3.6/cache-infinispan/src...).
In fact, I think this is key cos the default cache config has no eviction and some of your
entities have "pastry" as region name but there's no such cache in the
infinispan config, and because your default cache has no eviction/expiration (the ehcache
does have eviction/expiration settings in default cache), these caches would grow without
limit.
So, let's go back to step one. First of all, based on what I saw in your config, you
don't need an infinispan.xml at all. From an Infinispan perspective, here're
different options you can use to config Infinispan 2LC:
Option 1. If you remove the region attribute settings of your @Cache annotations, you can
use something like this (Box and Bag entities not included):
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Container.eviction.max_entries"
value= "1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Doughnut.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Muffin.eviction.max_entries" value=
"1000"/>
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.strategy" value=
"LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Carton.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Egg.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.strategy"
value= "LRU" />
<entry
key="hibernate.cache.infinispan.org.foobar.Kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 2. Still with no regions defined in @Cache, the configuration in Option 1 can be
further simplified like this so that all entities have the same eviction/expiration
settings:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.entity.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.entity.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Option 3. If you still wanna keep your @Cache region definitions, based on the
region's in the actual code and not the infinispan.xml file, this would look something
like this:
<property name="jpaPropertyMap">
<map>
<entry key="hibernate.dialect"
value="org.hibernate.dialect.H2Dialect" />
<entry key="hibernate.hbm2ddl.auto" value="update" />
<entry key="hibernate.jdbc.batch_size" value="400" />
<entry key="hibernate.jdbc.fetch_size" value="200" />
<entry key="hibernate.jdbc.wrap_result_sets" value="true"
/>
<entry key="hibernate.generate_statistics" value="true" />
<!-- 2 is TRANSACTION_READ_COMMITTED -->
<entry key="hibernate.connection.isolation" value="2" />
<!-- second level cache config for all cache providers -->
<entry key="hibernate.cache.use_second_level_cache"
value="true" />
<entry key="hibernate.cache.use_query_cache" value="true"
/>
<entry key="hibernate.cache.region.factory_class"
value="org.hibernate.cache.infinispan.InfinispanRegionFactory" />
<entry key="hibernate.cache.infinispan.container.eviction.strategy"
value= "LRU" />
<entry key="hibernate.cache.infinispan.container.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.pastry.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.pastry.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.carton.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.carton.eviction.max_entries"
value= "1000"/>
<entry key="hibernate.cache.infinispan.egg.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.egg.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.cache.infinispan.kiwi.eviction.strategy" value=
"LRU" />
<entry key="hibernate.cache.infinispan.kiwi.eviction.max_entries" value=
"1000"/>
<entry key="hibernate.connection.isolation" value="2" />
<!--
http://docs.jboss.org/hibernate/core/3.3/reference/en/html/architecture.h...
-->
<entry key="hibernate.current_session_context_class"
value="org.hibernate.context.JTASessionContext" />
<entry key="hibernate.transaction.manager_lookup_class"
value="org.foobar.helper.HibernateTransactionManagerLookup"/>
</map>
</property>
Finally, all this is in http://community.jboss.org/docs/DOC-14105
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.zip, ispn686-error-galder.txt
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
10:32 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-868:
----------------------------------
Attachment: ispn686-error-galder.txt
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.zip, ispn686-error-galder.txt
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
9:47 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: ISPN-868-1.zip
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
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
9:57 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: test-progress.JPG
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, 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
9:57 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: jconsole-mbeans.JPG
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, 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
9:57 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: jconsole-memory-view.JPG
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, 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
10:02 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse commented on ISPN-868:
-------------------------------------
A new test project has been attached that will function correctly. Infinispan and
JBossJTA both include jboss-logging but different versions. That has been fixed.
The updated proejct includes the configuration from option #3 below. I ran the test
FillCartonTest.testKiwisAllInOneCarton() with the VM argument -Xmx256m. The test made it
to somewhere between 3400 and 3500 Kiwi objects added to the Container object before
generating the message 'java.lang.OutOfMemoryError: GC overhead limit exceeded'.
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, 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
10:58 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
To run the same test with EhCache, you simply have to change
hibernate.cache.region.factory_class to net.sf.ehcache.hibernate.EhCacheRegionFactory,
correct? What kind of numbers are you getting with EhCache for the same test and memory
settings?
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, 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
11:17 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
Btw, if you're comparing Infinispan and EhCache, I don't think the memory settings
for the different caches in EhCache match the ones for Infinispan:
[2011-01-13 11:01:28.437, 0]WARN [main](Cache.java:950) - Cache: kiwi has a
maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no
capacity limit. Set it to 1 if you want no elements cached in memory
[2011-01-13 11:01:28.481, 44]WARN [main](Cache.java:950) - Cache: carton has a
maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no
capacity limit. Set it to 1 if you want no elements cached in memory
[2011-01-13 11:01:28.482, 45]WARN [main](Cache.java:950) - Cache: container has a
maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no
capacity limit. Set it to 1 if you want no elements cached in memory
[2011-01-13 11:01:28.484, 47]WARN [main](Cache.java:950) - Cache: pastry has a
maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no
capacity limit. Set it to 1 if you want no elements cached in memory
[2011-01-13 11:01:28.504, 67]WARN [main](Cache.java:950) - Cache: egg has a
maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no
capacity limit. Set it to 1 if you want no elements cached in memory
So, if you were to compare them equally, I suppose you'd have to change
maxElementsInMemory to 1000 for all caches in the ehcache config too?
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, 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
12:25 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
Forget about EhCache, there appears to be a leak in Infinispan and there's a fairly
good chance that the leak was recently discovered in ISPN-845:
I took a heap dump once passed the 3500 object mark and I see this:
"3,530 instances of
"com.arjuna.ats.internal.jta.transaction.arjunacore.AtomicAction", loaded by
"sun.misc.Launcher$AppClassLoader @ 0x10a802050" occupy 235,563,912 (89.75%)
bytes. These instances are referenced from one instance of
"java.util.concurrent.ConcurrentHashMap$Segment[]", loaded by "<system
class loader>"
These ConcurrentHashMap belongs to
org.infinispan.transaction.xa.TransactionTable.localTransactions map and ISPN-845
precisely points to a leak there. I'm attaching a screenshot of Eclipse MAT.
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, 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
12:27 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-868:
----------------------------------
Attachment: Memory leak.jpg
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
12:30 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
Tom, we have not yet released a version that contains the fix for ISPN-845 but you can
build it from https://github.com/galderz/infinispan/tree/4.2.x
Could you build it, update the dependencies and see if the test carries on? I'll try
to do the same on my part and see if I can find out about ISPN-845
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
1:20 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-868:
------------------------------------
If you grab Infinispan 4.2.1-SNAPSHOT from Maven, it contains the fix to ISPN-845.
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
5:14 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse commented on ISPN-868:
-------------------------------------
With Infinispan 4.2.1-SNAPSHOT I receive the following error. I do not receive this error
with Infinispan 4.2.0.FINAL.
[2011-11-13 08:11:30.489, 1896]WARN [main](arjunaI18NLoggerImpl.java:523) - ARJUNA-12130
Name of XA node not defined. Using Arjuna:8317
[2011-11-13 08:11:30.727, 2134]WARN [main](jtaI18NLoggerImpl.java:177) - ARJUNA-16041
prepare on < formatId=131076, gtrid_length=39, bqual_length=28,
tx_uid=0:ffffc0a80170:207d:4d2f2432:d, node_name=Arjuna:8317,
branch_uid=0:ffffc0a80170:207d:4d2f2432:10, eis_name=unknown eis name >
(TransactionXaAdapter{localTransaction=org.infinispan.transaction.xa.LocalTransaction@178af9c0})
failed with exception XAException.XAER_NOTA
javax.transaction.xa.XAException
at
org.infinispan.transaction.xa.TransactionXaAdapter.getLocalTransactionAndValidate(TransactionXaAdapter.java:148)
at
org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:62)
at
com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:204)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2567)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2524)
at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2065)
at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1458)
at
com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:99)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:159)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1158)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:119)
at
org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1009)
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
at
org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393)
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:621)
at org.foobar.BoxDAO$$EnhancerByCGLIB$$13c53863.merge(<generated>)
at org.foobar.FillContainerTest.testMufinsAllInOneBox(FillContainerTest.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82)
at
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:240)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:180)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
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
2:45 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
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
4:33 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
Actually, I get your exception now. I think I might have not have synchronized my
repository before trying the fix. Let me look at this and upload a correct snapshot
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
5:21 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
I've investigated more the issue and your leak is definitely caused by the phenomenon
explained in ISPN-845 but the issue is not completely fixed. We'll let you know when
we've found a solution.
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
6:22 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-868:
----------------------------------
Attachment: With proper fix.jpg
With the proper fix, the memory consumption looks fine now. Closing the issue since
it's been solved by ISPN-845
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, With
proper fix.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
6:22 p.m.
New subject: [JBoss JIRA] Resolved: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño resolved ISPN-868.
-----------------------------------
Resolution: Duplicate Issue
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, With
proper fix.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
6:24 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-868:
---------------------------------------
We'll upload a snapshot in a few mins.
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, With
proper fix.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
6:49 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-868:
------------------------------------
4.2.1-SNAPSHOT published to Maven with this fix.
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, With
proper fix.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
7:39 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse commented on ISPN-868:
-------------------------------------
The 4.2.1-SNAPSHOT build resolves the issue. The test is currently at 3500 kiwis and
total memory usage has yet to exceed 90 meg. With 4.2.0.FINAL memory usage was near 256
meg.
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, With
proper fix.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
7:41 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Tom Waterhouse updated ISPN-868:
--------------------------------
Attachment: memory usage with 4.2.1-SNAPSHOT.png
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, memory usage with
4.2.1-SNAPSHOT.png, test-progress.JPG, With proper fix.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
7:49 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-868:
------------------------------------
Awesome, good to know. :)
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, memory usage with
4.2.1-SNAPSHOT.png, test-progress.JPG, With proper fix.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
1:22 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-868) Running out of memory using Infinispan after adding a small number of entities
[
https://issues.jboss.org/browse/ISPN-868?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-868:
-------------------------------
Fix Version/s: 4.2.1.CR4
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.CR4, 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, memory usage with
4.2.1-SNAPSHOT.png, test-progress.JPG, With proper fix.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
4805
days inactive
4863
days old
infinispan-issues@lists.jboss.org
30 comments
3 participants
participants (3)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Tom Waterhouse (JIRA)