Configuring the cache-size down to 1000 worked wonder. I just uploaded 2CMPs with
-Xmx=32m setting without problems.
Thanks for the help,
Heiko
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834136#3834136
Reply to the post :
http://www.jboss.org/index
Alexey is working on instance-per-transaction which isn't a real cache.
You ain't going to get much help with more info.
Asserting you've done things correctly isn't very useful.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834044#3834044
Reply to the post
Adrian,
The setting is not enough. I have run into the same problem (and reported it) a couple
of weeks back. I then tried modifying the container configuration and the read-ahead
setting to anything I could image without results.
However, I have seen that Alexey committed some changes in the c
100 is the pool size, the default cache size is 1 million in jboss.
see standardjboss.xml
Also if you are using hsqldb, its tables are fully loaded into memory unless
you use "create cached table".
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834022#3834022
I ran now the same code with SUNs J2EE reference and Pointbase. Memory usage was
constant after the first 1000 Beans (initialization). I've been running the test up to
5000 Beans. So it seems to be a jboss-related problem.
Heiko
View the original post :
http://www.jboss.org/index.html?module=b
