[jboss-jira] [JBoss JIRA] Commented: (JBREM-821) JBoss Remoting fails under load
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Thu Oct 18 14:25:03 EDT 2007
[ http://jira.jboss.com/jira/browse/JBREM-821?page=comments#action_12383309 ]
Ron Sigal commented on JBREM-821:
---------------------------------
Regarding issue 2) from Tim's note: org.jboss.remoting.transport.socket.SocketServerInvoker.cleanup() should wait for all worker threads to finish processing before returning to SocketServerInvoker.stop(), which then calls ServerInvoker.stop(). The problem is that ServerInvoker.stop() removes all callback handlers, which could happen while a worker thread is still processing.
> JBoss Remoting fails under load
> -------------------------------
>
> Key: JBREM-821
> URL: http://jira.jboss.com/jira/browse/JBREM-821
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.2.SP1
> Reporter: Ovidiu Feodorov
> Assigned To: Trustin Lee
> Priority: Blocker
> Fix For: 2.4.0.Beta1 (Pinto)
>
>
> This is a duplicate of JBMESSAGING-1114 present here to remind Remoting people that Messaging has this urgent need.
> Phrasing belongs to Tim:
> 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
More information about the jboss-jira
mailing list