Memory problem when sending large number of messages

[benstarr]

I have a complex J2EE application which uses JMS quite a lot. There is a batch process which it runs overnight which is causing a memory leak. Each morning the server has used more and more memory and eventually it will run out of memory. The memory is never reclaimed by the JVM.

I think I have isolated the problem to a part of the batch process which sends a large number of messages. The pesudo code is something like the following:

1. Lookup queue connection factory
2. Create queue connection
3. Lookup queue
4. Create queue session
5. Create queue sender
6. Send 1,000s of messages using the queue sender
7. Close the queue connection

This all occurrs within an MDBs onMessage method. Each message is a map message and I am reusing the same message object each time by calling message.clearBody after each call.

I am running JBoss 3.2.3 on Mac OS 10.3 Server (Java 1.4.2) and am using an Oracle database for message persistence. I am using JMS in many other parts of the application but generally only sending one message at a time. Any help in identifying the possible cause of the memory leak would be much appreciated.

[genman]

Where are the thousands of messages going? Are they being consumed or not? Are they going to the DB, and what DB is being used?

Reusing the same object doesn't improve anything, as it gets serialized (copied) on the way to the server anyway.

If it's easy enough to reproduce, I would first upgrade to JBoss 3.2.6RC1.

[benstarr]

The messages are being consumed by another MDB and it is possible that the memory problem is related to that MDB but I don't think that is the case. I am using an Oracle database as a persistence mechanism for the messages. Unfortunately I don't have a lot of flexibility in the JBoss version used in production.

[stephanenicoll]

Do you need to send those 10.000 messages in the same transaction? Otherwise, you can use java:/JmsXA and create a connection for each message. Won"t be a problem since it's a pooled behind the scenes.

Regards,

Stephane

[benstarr]

I'm not actually sending them within a transaction. I've set the transaction attributes of the MDB that is sending the messages to NotSupported. I don't know whether it is using a single database transaction to commit the messages to the persistent store though (Oracle).