[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster-devel] unprocessedEvents

Hi Andrew,

i've found this in the svn logs:

r16557 | laghi | 2007-10-26 10:31:40 +0000 (Fri, 26 Oct 2007) | 1 line

removed memory leak due to EventPlugin and fixed one bug in EventPlugin (flag about already processed was for all queues: once one queue had fired, no other event on the same queue type would have been fired)
r16482 | ruff | 2007-09-17 17:49:54 +0000 (Mon, 17 Sep 2007) | 1 line

StorageEventHandler.java leak sneaked in on 2007-06-19, the queue.shutdown is now freeing the map entry again
r16365 | laghi | 2007-07-18 21:03:07 +0000 (Wed, 18 Jul 2007) | 1 line

added missing class

If you don't want to use a newer xmlBlaster you can:

* Disable the plugin in xmlBlasterPlugins.xml
* or set a break point into the constructor and comment out the calling code
* or apply the patches


Andrew Mason schrieb:
Hi guys,

We are experiencing the same memory leak problem that I noticed another
person had around the time of September 07. when we perform requests from a client to a server, the events
are being stored in the unprocessedEvents
Map in the org.xmlBlaster.util.queue.StorageEventHandler class. We are
having to restart the server every few days because of
Out of memory.

I am wondering what the best solution to this problem is? We are currently
using xmlBlaster version 1.62 and would prefer
Not to update to a later version. Is there a patch available or other simple

Thanks for your help

Andrew Mason

Marcel Ruff
Phone: +49 7551 309371