You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2007/06/26 11:00:25 UTC
[jira] Created: (JCR-982) Each TransactionContext creates new
thread
Each TransactionContext creates new thread
------------------------------------------
Key: JCR-982
URL: https://issues.apache.org/jira/browse/JCR-982
Project: Jackrabbit
Issue Type: Improvement
Components: transactions
Reporter: Marcel Reutegger
Priority: Minor
The rollback threads are not stopped when the transaction commits, but only when the timeout occurs. This has the effect that lots of threads are created and sleeping when many transactions are committed in a short time frame. The rollback thread should be signaled when the transaction is committed or even better a Timer should be used with a single thread for all transaction contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Resolved: (JCR-982) Each TransactionContext creates new thread
Posted by Christoph Kiehl <ch...@sulu3000.de>.
Marcel Reutegger (JIRA) wrote:
> Marcel Reutegger resolved JCR-982.
> ----------------------------------
>
> Resolution: Fixed
> Fix Version/s: 1.4
>
> Replaced the rollback thread with a single static Timer instance and use a Task per TransactionContext for the timeout callback.
>
> Committed in revision: 550752
Great news! This issue bugged me as well ;)
Thanks!
Christoph
[jira] Updated: (JCR-982) Each TransactionContext creates new
thread
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-982:
------------------------------
Component/s: jackrabbit-core
> Each TransactionContext creates new thread
> ------------------------------------------
>
> Key: JCR-982
> URL: https://issues.apache.org/jira/browse/JCR-982
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core, transactions
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.4
>
>
> The rollback threads are not stopped when the transaction commits, but only when the timeout occurs. This has the effect that lots of threads are created and sleeping when many transactions are committed in a short time frame. The rollback thread should be signaled when the transaction is committed or even better a Timer should be used with a single thread for all transaction contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-982) Each TransactionContext creates new
thread
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger reassigned JCR-982:
------------------------------------
Assignee: Marcel Reutegger
> Each TransactionContext creates new thread
> ------------------------------------------
>
> Key: JCR-982
> URL: https://issues.apache.org/jira/browse/JCR-982
> Project: Jackrabbit
> Issue Type: Improvement
> Components: transactions
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
>
> The rollback threads are not stopped when the transaction commits, but only when the timeout occurs. This has the effect that lots of threads are created and sleeping when many transactions are committed in a short time frame. The rollback thread should be signaled when the transaction is committed or even better a Timer should be used with a single thread for all transaction contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-982) Each TransactionContext creates new
thread
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-982.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Replaced the rollback thread with a single static Timer instance and use a Task per TransactionContext for the timeout callback.
Committed in revision: 550752
> Each TransactionContext creates new thread
> ------------------------------------------
>
> Key: JCR-982
> URL: https://issues.apache.org/jira/browse/JCR-982
> Project: Jackrabbit
> Issue Type: Improvement
> Components: transactions
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.4
>
>
> The rollback threads are not stopped when the transaction commits, but only when the timeout occurs. This has the effect that lots of threads are created and sleeping when many transactions are committed in a short time frame. The rollback thread should be signaled when the transaction is committed or even better a Timer should be used with a single thread for all transaction contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.