[
http://jira.jboss.com/jira/browse/JBREM-658?page=all ]
Ron Sigal closed JBREM-658.
---------------------------
Resolution: Done
In the course of testing the new blocking policy, a problem was discovered in the way
client side oneway invocations are handled in the socket transport. See JIRA issue
JBREM-706: "In socket transport, prevent client side oneway invocations from
artificially reducing concurrency".
The unit tests have passed on cruisecontrol.
bug in oneway thread pool under heavy load
------------------------------------------
Key: JBREM-658
URL:
http://jira.jboss.com/jira/browse/JBREM-658
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: transport
Affects Versions: 1.4.5.GA, 2.2.0.Alpha4
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
Per forum thread, there looks to be a bug in concurrent lib (deadlock in
BlockedLinkedQueue). Will either need to look for a newer version with fix or a
replacement for the default thread pool being used for oneway invocations.
--
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