128MB heap is small, try something like 512MB
I admit that 128 is pretty small, but I had also tried 256MB and it also had the same problem. My concern is that if there really is a memory leak issue, the used memory will just continue to grow and grow hitting whatever limit I set it at.
obviously there aren't leaks that would cause hundreds of megabytes of memory to disappear, or people would have noticed it already
how many concurrent clients do you have and how long has the server been running til you hit the out of memory exception?
We think we have identified the memory leak and it was a problem in our code. There were instances where PreparedStatement and ResultSet objects were being reused in a method without first closing them. This must have then left open objects that were not being garbage collected.
The interesting thing though is that JBoss 2.4.6 let us get away with this, while JBoss 3.0.2 just kept on eating up memory until we crashed. I'm not sure what changed between the two versions to account for this. Anyway, just wanted to post our stupid mistake in the hope that it is some help to someone else one day ( I hate those posts where you never find out how the problem was ever solved.. ).
And thanks for your responses juha. :)
JBoss 2.4 didn't support open connections across
different transactions. It automatically closed
them when the transaction was committed/rolled back.
You wouldn't have noticed your bug :-)
agreed on the posts that leave solutions out, they suck
glad you found the cause