[
https://issues.apache.org/jira/browse/VYSPER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902542#action_12902542
]
Bogdan Pistol commented on VYSPER-243:
--------------------------------------
You are right if you are using a single Timer instance to schedule n tasks. But
in the current implementation there are n instances of Timer, and every
instance is used to schedule 1 task, hence using n threads to schedule n tasks
(for n sessions), which is inefficient.
> Bosh inactivity checking thread
> -------------------------------
>
> Key: VYSPER-243
> URL: https://issues.apache.org/jira/browse/VYSPER-243
> Project: VYSPER
> Issue Type: Improvement
> Components: BOSH
> Reporter: Bogdan Pistol
> Priority: Minor
>
> There should be a single checking thread that will periodically check to see
> if there are sessions that passed their inactivity time.
> Right now this is done for every session with Timer.schedule that creates a
> thread for every session, which is not scalable (the number of threads
> increases linearly with the number of concurrent sessions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
