[
https://issues.apache.org/jira/browse/VYSPER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902402#action_12902402
]
Ashish Paliwal commented on VYSPER-243:
---------------------------------------
I don't think this is correct, that Timer.schedule will create a thread for
every session.
Here is note from javadoc
This class scales to large numbers of concurrently scheduled tasks (thousands
should present no problem). Internally, it uses a binary heap to represent its
task queue, so the cost to schedule a task is O(log n), where n is the number
of concurrently scheduled tasks.
However, moving to a more simple approach is better.
> 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.
