r*t
发帖数: 34 | 1 Hi, guys
I am sorry to bother you, actually I have two servers (A and B) in my
clustering, both run w2k and jboss4.0.2.
I have a stateful session bean run on two server, and one standalone client
run on one server (A). when I try the failover function of Jboss, I found that
if I kill one server by Ctrl+C, my standalone client will not notice it, so it
failover to another server perfectly. However, if I unplug the network cable
of server B, I found that it will take extreme long time to failover | r*t
发帖数: 34 | 2 I have changed the cluster-service.xml, so if I unplug B, A will detect it
alsmost instantly, however. It still take a long time to do the failover, I go
through the log info, and found:
2005-06-01 17:45:56,897 DEBUG
[org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] End
notifyListeners, viewID: 10
2005-06-01 17:46:52,297 DEBUG [org.jboss.ha.framework.server.HAPartitionImpl]
dests=[],
method_call=SessionState-'/HASessionState/Default'._setOwnership(ejb/MyBank,
192.168.1.100:1099:e9
【在 r*t 的大作中提到】
: Hi, guys
: I am sorry to bother you, actually I have two servers (A and B) in my
: clustering, both run w2k and jboss4.0.2.
: I have a stateful session bean run on two server, and one standalone client
: run on one server (A). when I try the failover function of Jboss, I found that
: if I kill one server by Ctrl+C, my standalone client will not notice it, so it
: failover to another server perfectly. However, if I unplug the network cable
: of server B, I found that it will take extreme long time to failover
|
|
