JGroups is only going to allow one message at a time from a particular sender
to proceed up the stack past UNICAST. This is needed to ensure message are
delivered in order. So, only one RPC at a time.
There's a JGroups JIRA to add an API whereby the application can define the
scope to which mes
Hi Brian,
okay - that wasn't the most intelligent post ever. So, let's clear things up.
I have a service, which is active on all nodes in the cluster. Nevertheless, if
the node a method of this service is invoked on, is not the master node, the
call is relayed to that master node (callMethodOnCo
"axelerator" wrote : Hi Brian,
|
| thanks. That's a good lookout. Also I tested the setup and AS started
without any itches and behaved pretty much normally.
| What I'm nevertheless a bit curious about is the use of synchronous RPC
calls (callMethodOnCoordinator) with regards to performan
Hi Brian,
thanks. That's a good lookout. Also I tested the setup and AS started without
any itches and behaved pretty much normally.
What I'm nevertheless a bit curious about is the use of synchronous RPC calls
(callMethodOnCoordinator) with regards to performance and timings.
Since we only use
Re: 2.6.13 and AS 4.2.3, I personally haven't tried any 2.6 series release with
AS 4.x. So I'll defer to the rest of the community for detailed input.
The 2.6 series is API compatible with the 2.4 series used in AS 4.2.x, and the
fundamental semantics of Channel behavior are the same, so it shou
Hey guys,
thanks for pointing this out. We enabled send_on_all_interfaces since we're
running in a Solaris Container and weren't sure, which interfaec ultimately
would be used for sending/receiving data.
Also, thanks for pointing out about the 2.6.10.merge release. is 2.6.13.GA
compatible with
And note that 2.6.10.merge is experimental and unsupported ! I recommend
2.6.13.GA instead which has been heavily tested.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260925#4260925
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&m
I don't recommend UDP.send_on_all_interfaces=true.
UDP.receive_on_all_interfaces=true is a bit suspect too, although not as much
as send_on_all_interfaces. It's much better IMO to pick a common network and
bind all nodes to an interface on that network it using -b xxx or
-Djgroups.bind_addr=xxx
Hey,
yeah, sorry for the mess-up. Attached is the correct version. You're right, in
IRC I told you I have those issues with TCP. Though, on the environment where I
copied the config from, UDP was set. after browsing the web for some itches, I
found a text stating that in GBit environments, UDP
Something got messed up in your paste of cluster-service.xml.
Also, I thought you'd said on IRC that you were using a TCP protocol stack?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260837#4260837
Reply to the post :
http://www.jboss.org/index.html?module
10 matches
Mail list logo
