JavaSpace.notify() "not reliable"
Timur Mehrvarz <[email protected]> Fri, 11 May 2007 01:47:12 +0200
| Newsgroups | gmane.comp.java.sun.javaspaces |
|---|---|
| Message-ID | <[email protected]> |
Hi. While looking for a solution to a problem, I found this [1]: "Many people get hung up on JavaSpace.notify() because it is “not reliable”. This needs careful explanation - most JavaSpaces will endeavour to deliver all appropriate events to a client. If the client becomes permanently unavailable (NoSuchObjectException) further events will not be delivered to it." Everything is working fine for me, for a while. But from a random moment on, my EventListener will not get called anymore, when they should. I don't think I am getting NoSuchObjectExceptions. My Jini VM and my apps VM are running side by side on the same intel Linux box. I am using plain Jini2_1 with transient Outrigger. I sure do something wrong. But what could that be? Thanks. Timur [1] http://www.dancres.org/blitzblog/2006/02/20/javaspaces-and-jms/ =========================================================================== To unsubscribe, send email to [email protected] and include in the body of the message "signoff JAVASPACES-USERS". For general help, send email to [email protected] and include in the body of the message "help". To view past JAVASPACES-USERS postings, please see: http://archives.java.sun.com/archives/javaspaces-users.html