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

Re: [xmlblaster] Durable QoS performance



Doug.Palmer at csiro.au wrote:

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
is:

ERROR
[MessageUnitHandler-/node/http:152.83.91.4:3412/msg/http_152_83_91_4_3412-10
26354250965-76.EmptyMessageUnit] Internal problem, msgUnit = null, there was
not yet any message published, only subscription exists on this unpublished
message:
  <MessageUnitHandler>
     <uniqueKey>http_152_83_91_4_3412-1026354250965-76</uniqueKey>
     <MessageUnitWrapper>null</MessageUnitWrapper>
     <SubscriptionInfo id='__subId:XPATH2:77/>
     <handlerIsNewCreated>false</handlerIsNewCreated>
  </MessageUnitHandler>

java.lang.Throwable 	at
org.jutils.runtime.StackTrace.getStackTrace(StackTrace.java:50) 	at
org.xmlBlaster.engine.MessageUnitHandler.getMessageUnitWrapper(MessageUnitHa
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
org.xmlBlaster.protocol.corba.serverIdl.ServerPOA._invoke(ServerPOA.java:80)
at
org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:207)
at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:404) 	at
org.jacorb.poa.RequestProcessor.run(Request

I think this was fixed yesterday, the newest cvs should have fixed this.

cu

Marcel



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