On 17.05.2007, at 20:24, Gregg Wonderly wrote:
Timur Mehrvarz wrote:
I still need to implement your third suggestion (below). I can do
so next week. And I will report back, if this fully fixes the
issue for me.
With Javaspaces, you should typically request notification, and
then do a read
to see if there is an entry that matches the same template, and
then take that
entry to process it if so.
(I'm back from traveling. Sorry for the delay.)
Doing one read operation, right after requesting the notification,
does - in my case - not seem to catch any missing objects. I still
need to do the "background polling", to prevent from dropped
notification.
Missing 1 in 50 or so sounds like a potential concurrency related
bug. If you increase the flow of data does that proportionally
increase the missing notifies? If you greatly reduce the flow does
that make the notifies more reliable?
My observation is, that there is no obvious relation between the
amount (or frequency) of data written to space - and the number of
skipped notifications. If (and when) a notification is dropped, seems
to be totally random and independent of what I do.
Timur
