[jboss-jira] [JBoss JIRA] Closed: (JBREM-617) CallbackPoller should have its own thread.
Ron Sigal (JIRA)
jira-events at jboss.com
Sat Oct 28 15:45:41 EDT 2006
[ http://jira.jboss.com/jira/browse/JBREM-617?page=all ]
Ron Sigal closed JBREM-617.
---------------------------
Resolution: Done
Created separate Timer for CallbackPoller.
> CallbackPoller should have its own thread.
> ------------------------------------------
>
> Key: JBREM-617
> URL: http://jira.jboss.com/jira/browse/JBREM-617
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.0.Beta1 (Bluto)
> Reporter: Ron Sigal
> Assigned To: Ron Sigal
> Fix For: 2.2.0.Beta1 (Bluto)
>
>
> Currently, LeasePinger and CallbackPoller share the single thread in org.jboss.remoting.util.TimerUtil. Messaging stress tests have revealed that if CallbackPoller gets a large list of callbacks to deliver, it can take long enough to cause a lease to expire.
--
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