[
http://jira.jboss.com/jira/browse/JBMESSAGING-1114?page=comments#action_1... ]
Ron Sigal commented on JBMESSAGING-1114:
----------------------------------------
I've added Tim's comments to JBREM-821 "JBoss Remoting fails under
load". I agree that issues 1) and 2) should be fixed.
Since there seems to be a workaround, I've scheduled JBREM-821 for Remoting release
2.4.0.Beta1 and reduced the priority to Major. If any further related issues arise, of
course, that can be readjusted.
JBoss Remoting fails under load
-------------------------------
Key: JBMESSAGING-1114
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1114
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.GA
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Critical
Fix For: 1.4.0.SP1
JBoss Remoting fails with various different errors when under extreme load.
To replicate this, set up two clustered server nodes, using a MySQL database.
These can both be on the same machine, using ServiceBindingManager.
On a second machine run Ovidiu's messkit toolki, first to send some messages:
mess -stat send -size 10240 50000
And then to receive them back using 50 concurrent consumers:
mess -stat -sessions 50 receive all
You will notice that JBoss Remoting fails with errors:
I believe this is due to remoting incorrectly thinking a connection has failed and
shutting down the connection. Perhaps due to the load, the ping does not get through in
time to refresh the lease?
I would like a remoting solution that *does not ping* from server to client - for us this
is unnecessary.
It also seems remoting is continually timing out and recreating connections - this could
also be a source of error.
How do we configure remoting so it does not do this?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira