| Author |
Re: JBoss 3.2.3: how to create 200 000 entity instances without out
|
|
| Marek Lange 2004-03-27, 12:01 am |
| Marcus Beyer wrote:
> We are trying to create (import) 200 000 CMP entity instances in JBoss.
> We get always out of mem when around 10% is done.
> JBoss 3.2.3 then consumes more than 700 MB of memory.
Did you increase the max heap value of the VM (-Xmx)?
> <cache-policy-conf>
> <min-capacity>50</min-capacity>
> <max-capacity>1000</max-capacity>
> <overager-period>150</overager-period>
> <max-bean-age>300</max-bean-age>
> <resizer-period>400</resizer-period>
> <max-cache-miss-period>60</max-cache-miss-period>
> <min-cache-miss-period>1</min-cache-miss-period>
> <cache-load-factor>0.75</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>1000</MaximumSize>
> </container-pool-conf>
> <commit-option>A</commit-option>
> </container-configuration>
> </container-configurations>
You should increase the cache size much more if you use the commit
option A. Keep an eye on the cache numbers in web-console.
-marek
| |
| Marcus Beyer 2004-03-27, 12:01 am |
| Marek Lange wrote:
> Marcus Beyer wrote:
>
>
>
> Did you increase the max heap value of the VM (-Xmx)?
Yes, I did.
Using a memory profiler I discovered the problem: it was not JBoss
or my configuration. The memory leak is in IronEye SQl, a JDBC
statistics tool. Here is my Bugzilla entry:
<http://bugzilla.irongrid.com/show_bug.cgi?id=253>
> You should increase the cache size much more if you use the commit
> option A. Keep an eye on the cache numbers in web-console.
Thank you. I only decreased it because of my memory problem ...
Grüße,
Marcus
| |
| Marcus Beyer 2004-04-01, 2:35 pm |
| Grzegorz Glowaty wrote:
>
>
> You problem is probably Hypersonic DB (bundled with jboss).
> It's configured to be in memory-db as default so all data is stored is in
> the memory.
> Switch to another db or configure hsql to work on disk.
I am using PostgreSQL. As I already said I solved the problem:
"
Using a memory profiler I discovered the problem: it was not JBoss
or my configuration. The memory leak is in IronEye SQl, a JDBC
statistics tool. Here is my Bugzilla entry:
<http://bugzilla.irongrid.com/show_bug.cgi?id=253>
"
Thank you anyway!
Marcus
|
|
|
|