5 Replies Latest reply on Oct 15, 2001 2:54 PM by Ashu

    Memory problem?

    ocquidant Newbie

      Hello,

      I am confronted to a memory problem, or perhaps it's not a problem but i have no explanation.

      I use jboss with large arrays that I store in the database using Blobs. In order to optimize memory ressource I have choosen the C commit option to not use the cache (I can't use the cache, my objects are too big).
      To give you an idea, i have 25 entity beans, each with 8 MB array fields. The jboss JVM grows up to 400 MB! Even if the beans were all resident memory, they should occupate about 200 MB. Since i use the C commit option, this is not true because the containers should passivate beans after each transaction.
      I don't understand why the server JVM grows up to 400MB.
      Another thing seems a bit strange to me. At the end of my tests, the server display lot of ejbPassivate() messages (messages that I wrote in the corresponding methods) and the JVM memory doesn't shrink.

      Of course my bean fields are transient so the passivation should not consider them (i've also tried to put them to null in ejbPassivate()).

      Do someone have experienced a similar problem?

      Thanks a lot.

      Nicolas