Re: javaspace notify

> Thank u for ur reply ..
>
> I am using *javaspace -jini2_1* for space implementation
>
> Here I tried with server using notify and client having only one 
> write(for the entry notified) in an execution. I repeated the client 
> side program at random intervals, but not successful every time
>

I am not sure if this is what is going on, but the std.
JavaSpaces events (the one you register for by calling
JavaSpace.notify) don't have a lot of information in them, at
some level all but the "last one" are redundant, so in cases
where there are a lot of writes in a short period of time
matching a given registration Outrigger will drop many of the
intervening events as an optimization. Still not clear to me if
you are writing enough entries for this to be the explanation for
what you are seeing.

The other thing to look at is logging output. Is there any log
output from the Outrigger process? If a notify attempt fails
Outrigger will log a message. com.sun.jini.outrigger.event is the
relevant logger name. Because event notification failures are
expected Outrigger tends to log them at a fairly low logging
level, you will need to use Level.FINE to get all the possible
message - though most of the interesting messages are logged at
Level.INFO or Level.WARNING which should come out by default.

===========================================================================
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