[
https://jira.jboss.org/jira/browse/JBAS-5419?page=com.atlassian.jira.plug...
]
Sam[Shankar Pattabiraman] closed JBAS-5419.
-------------------------------------------
Please close this issue. I don't use JBoss anymore. I started Oracle's Web Logic
server with clustering built in and no issues.
It takes two long years to figure out a simple clustering bug. Simple to reproduce, just
keep hitting the server with JMeter or some tool. Try to kill one server before it get
killed it is paused in the command line and the sessions never get serverd by the current
or the other server in the cluster.
There is some process issue and I think no one takes ownweship in a open source
environment.
Server Shutdown Latency - Session replication and Forwarding
------------------------------------------------------------
Key: JBAS-5419
URL:
https://jira.jboss.org/jira/browse/JBAS-5419
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.5.GA
Environment: Java 1.5.0_05, Win XP,Red Hat 3 JBoss 4.0.5 Apache
Reporter: Sam[Shankar Pattabiraman]
Assignee: Brian Stansberry
Priority: Minor
Setup a cluster with 2 nodes. Be in a session where a server is servicing.
Try to give a Control Z to kill the server while servicing. The latency involved in
shutting down the server never gives a chance for the server to switch to the other.
The session in the latency period of shutdown never gets successfully switched to the
other node in the cluster.
Apache-2 Node Jboss Cluster and a Trivial JEE Application.
Check this out whether it is a configuration issue or a real issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira