[ http://jira.jboss.com/jira/browse/JBREM-36?page=history ]
Tom Elrod updated JBREM-36: ---------------------------- Fix Version: 1.2.0 beta (was: 1.0.1 final) This is only happens for the oneway tests. The problem is that the http server invoker wants to send a reply (status 200) even if the response from the invoker is null. Therefore the socket connection is held while all the header and reply processing is going on. This processing is slow enough that new requests get blocked until the status rely is sent. Eventually, client threads get an error because so many are queued up that the socket will not accept any more. > performance tests fail for http transports > ------------------------------------------ > > Key: JBREM-36 > URL: http://jira.jboss.com/jira/browse/JBREM-36 > Project: JBoss Remoting > Type: Bug > Components: transport > Versions: 1.0.1 beta > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.2.0 beta > > > Either some of the messages are getting lost or the invoker is so slow that > the test finishes before invoker can finish sending messages. Says that it > only got about 4900 messages of 5000 it should have. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development