Hi,
> One important difference we noticed was made by an instance of
> org.exist.storage.NotificationService (notificationService from
> org.exist.storage.BrokerPool) and an underlying java.lang.Object[].
The listener should be cleared immediately after query execution (via a
call to XQueryContext.reset -> clearUpdateListener).
I had a look at this and found one situation in which the XQueryContext
wasn't cleared properly: if an exception occurred during a call to
util:eval(). Are you using util:eval in your application?
If yes, my bug fix is in trunk:
http://exist.svn.sourceforge.net/exist/?rev=7693&view=revIf not, we have to check for other possibilities. For debugging, I just
put a breakpoint into NotificationListener.unsubscribe. Since my test
case was single-threaded, size() should have been 0 after unsubscribing
the only listener.
Wolfgang
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
