Thanks for fixing the build.
This SVN client in Eclipse is getting really annoying.
For some reason it had forgotten that my microcontainer/tools project
was managed by SVN?
This isn't the only problem with this buggy software. :-(
e.g. In the workspace where I'm doing the EJB metadata changes
I can't even resynchronise with SVN (it is totally broken).
Ironcially, I only started using Eclipse because it told me what I had changed
so I didn't break the build with partial checkins. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995858#3995858
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995858
No, this is just an example: for UDP, if you call RpcDispatcher.callRemoteMethods() with use_anycast=false, I'll use regular multicast. If it is true, I'll use single unicasts *no matter how many members there are in the target list* !
So the decision whether to use anycast or not would be made by JBossCache, possibly based on my previous example. Maybe even configurable ? Although we have already too many attributes... :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995857#3995857
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995857
Another issue I see with the state transfer approach is that we need to run the flush protocol *once* for each state transfer. Unless we can have the coordinator start and stop the flush protocol, this might be quite expensive.
Regarding deadlocks: we could wait until JGroups 2.5 is in place; with the threadless stack and parallel and out-of-band processing, deadlocks should not occur anymore.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995809#3995809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995809
"manik.surtani(a)jboss.com" wrote :
| IIRC, if the transport is UDP and multicast is enabled, this is achieved by multicasting and only named recipients accepting the comms (Bela or Vlad, perhaps you could confirm this?).
|
No, we always use unicasts. It is up to the caller of RpocDispatcher.callRemoteMethods() to decide whether a multicast or multiple unicasts are used.
With TCP as transport, of course *always* use anycasting. With UDP (IP multicasting), it depends on the subset to which you want to send a message, e.g.
1-3 out of 10: anycast
4-10 out of 10: multicast
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995807#3995807
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995807