JBoss clustering with webservices
by Leandro Sales
Hi. I'm implementing cluster of nodes with jboss. Each node provides a
Webservice implemented with EJB (@Stateless, @Webservice and
@Clustered). I deployed the webservice .jar bean into the
server/all/farm directory and hence the webservice is replicated among
the nodes of the cluster. How can I provide the load balancing for
these nodes considering the to points listened below?
1 - The webservice consumer needs to point to a unique address (the
interceptor, which is responsible to select a node and forward to
request to it). How to define this interceptor?
2 - Once one node is selected, I don't want that the node response
pass back through the interceptor (like documentations explains),
instead I want the webservice response be directly sent to the client.
Is this possible?
Thank you. All points/suggestion are greatfully accepted.
Best regards.
-Leandro
16 years
Way to identify graceful startup/shutdown in cluster group
by saravanan m
Hi All,
We know we will get an membershipchanged notification when the server leaves
the current cluster group,
I want to know whether it was an graceful shutdown or an system/hardware
failure. Depends on the shutdown type we want to perform some actions.
Can anyone please give a solution for that.
Thanks,
Saravanan.
16 years
TCP vs. UDP
by M Wagad
We have 2 node JBOSS Cluster, and we are having performance issue, what we found out is that if we turn of the slave server, and operate the one master node (Changing the load balance to 100/0), we have much better performance then when we have both of the running sharing the load with 50/50 load balance. Would changing the default Protocol of UDP to TCP make any difference in terms of Performance? I had come across these posts on the Net that praises TCP over UDP for organizations that have less then 16 JBOSS Nodes :-
For TCP…
“We experiment with another configuration using TCP/IP and show that current J2EE application server clusters up to 16 nodes (the largest configuration we tested) can scale much better with this configuration.
We attribute the superiority of TCP/IP based group communications over UDP/IP multicast to a better flow control management and a better usage of the network switches available in cluster environments.”
And UDP..
“Having to support reliable multicast UDP communication is not a piece of cake. Drop a couple of packets and you get only a fraction of the throughput. Then lose the ordering of the packets and you are in a slump. The situation can turn pretty sour if you use large messages that get fragmented (more than one UDP packet). You only need to lose one packet to lose your entire message - then you resend everything. The point is that in unideal and congested conditions you start to miss TCP, and it is probably extremely hard to beat its adaptive protocol that has been perfected for so many years.”
I would also like to know if any companies out there make the change from UDP to TCP and if they can share their experience with us.
ThanksM. Wagad.
_________________________________________________________________
Find hidden words, unscramble celebrity names, or try the ultimate crossword puzzle with Live Search Games. Play now!
http://g.msn.ca/ca55/212
16 years
