Re: [jgroups-dev] message passing up is broken in NAKACK

I suggest take a look at Infinispan: it already provides locking, but 
doesn't require an additional lock() / unlock() cycle.

On 5/21/13 5:25 AM, hyliu wrote:
> now I set a 5 seconds timeout, while not sure what's the reason,
> occasionally, not all member received msg according the returned RspList.
> (maybe it caued by GC or network traffic problem)
>
> so I added a retry logic.
>
> following your suggesion, I'll try to remove retry logic and use a larger
> timeout. but not sure how to do if still has member not received msg after
> timeout.
>
> my use case is a cache service, the entries in cache is sensitive for
> application, each nodes need get the latest entry. dummy code is like below.
> I guess jboss cache would have same reqirement, not sure how it achieve
> this.
>
> ========put a entry========
> Lock l = LockService.getLock("name")
> l.lock()
> castMessage(...)
> l.unlock()
>
> ========received a entry====
> put the entry to a memory map.
>
> ========get a entry========
> Lock l = LockService.getLock("name")
> l.lock()
> getMessage from memory map
> l.unlock()


-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Javagroups-development mailing list