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

RE: [xmlblaster] Durable QoS performance

> Dead letters are volatile messages, this memory leak was fixed
> some days ago.
> Can you please confirm that the memory exhaust disappeared in 
> the newest 
> cvs?

I've checked out the latest from CVS and tried it. Thanks for fixing the
filename bug. Without setting messages to volatile, things work OK, although
I have to clear out the message store for each run. Using XPath, maximum
number of messages per second rises from 5 to 10.

However, if I set isVolatile(true) in the publication code, then what I get

26354250965-76.EmptyMessageUnit] Internal problem, msgUnit = null, there was
not yet any message published, only subscription exists on this unpublished
      <SubscriptionInfo id='__subId:XPATH2:77/>

java.lang.Throwable 	at
org.jutils.runtime.StackTrace.getStackTrace(StackTrace.java:50) 	at
ndler.java:154) 	at
org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1212) 	at
org.xmlBlaster.engine.RequestBroker.publish(RequestBroker.java:1032) 	at
org.xmlBlaster.engine.XmlBlasterImpl.publish(XmlBlasterImpl.java:138) 	at
org.xmlBlaster.protocol.corba.ServerImpl.publish(ServerImpl.java:108) 	at
at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:404) 	at

I'll check out the XML database next. I'm using BLOBs for data, but I know I
have to be careful there.