User development,

A new message was posted in the thread "JBoss Remoting in AS Cluster":

http://community.jboss.org/message/525019#525019

Author  : Wolfgang Medlitsch
Profile : http://community.jboss.org/people/medlW

Message:
--------------------------------------------------------------
Additionally to the post in the AS Clustering Community I post it also here:
I configured and deployed a simple  Remoting Application into a 4.2.2 AS and 
run it successfully (below my  mbean-definition).  I set up a 2-node cluster 
using the default cluster  configuration by starting each server with "run -c 
all" (having prooved  that the node did recognise each other). Then I ran over 
some seconds  hundreds of calls in different threads using different 
connections. Only  the Server which is contained in thelocatorUrl did respond. 
Principally  what do I have to do to run the JBoss Remoting in a cluster and 
observe  some sort of load balancing?
Do I have to use a special  connector or transport? What about 
Cluster-Policy-Hints like @Clustered(loadBalancePolicy="RoundRobin"....?
 
Her the simple mbean definition:
<server>
 
<mbean  code="org.jboss.remoting.transport.Connector"
name="jboss.remoting:service=Connector,transport=Socket"
display-name="Socket  transport Connector">
<attribute name="InvokerLocator">
<![CDATA[socket://localhost:5400]]>
</attribute>
<attribute  name="Configuration">
<config>
<handlers>
<handler   
subsystem="cluster">medl.remoting.cluster.server.SimpleInvocationHandler</handler>
</handlers>
</config>
</attribute>
</mbean>
</server>
 
Thanks in  advance

--------------------------------------------------------------

To reply to this message visit the message page: 
http://community.jboss.org/message/525019#525019


_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to