Hi, James The object TransactionID seemed not be released after commit so that the heap was used up and the OutOfMemory error occurred again on my test which just used a connecion, 2 sessions(one is for receive request message the other one is for send respond message), a producer and a consumer. Of course, I put the new ActiveMQObjectMessage.java which updated by Hiroshi Ayukawa shown as below in my java code.
Hiroshi Ayukawa wrote: > > Hi, all. > > org.apache.activemq.command.ActiveMQObjectMessage#storeContent() is > supposed to be buggy. > > ObjectOutputStream should be reset as well as other parts of acticemq do. > ----------------------------------- Line 98--100 should be.. > -------------------------------------------------------------- > ObjectOutputStream objOut = new > ObjectOutputStream(dataOut); > objOut.writeObject(object); > + objOut.flush(); > + objOut.reset(); > objOut.close(); > -------------------------------------------------------------------------------------------------------------------------------------- > > cf. http://java.sun.com/products/jdk/serialization/faq/#OutOfMemoryError > -- View this message in context: http://www.nabble.com/Broker-used-up-the-memory-tf2316972.html#a6617931 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
