You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2009/07/18 12:06:14 UTC

[jira] Created: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
---------------------------------------------------------------------------------------------------------------

                 Key: TAP5-788
                 URL: https://issues.apache.org/jira/browse/TAP5-788
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-ioc
    Affects Versions: 5.1.0.5, 5.1.0.4, 5.1.0.3, 5.1.0.2, 5.1.0.1, 5.1.0.0, 5.2, 5.1
            Reporter: Massimo Lusetti


ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.

Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-788:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>            Assignee: Howard M. Lewis Ship
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-788.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-788.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti updated TAP5-788:
---------------------------------

    Attachment: patch

Patch against current trunk, with modified test

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Massimo Lusetti updated TAP5-788:
---------------------------------

    Attachment: patch

Patch against current trunk, with modified test

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TAP5-788) ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAP5-788:
-----------------------------------------

    Assignee: Howard M. Lewis Ship

> ParallelExecutor service throws RejectedExecutionException if more then THREAD_POOL_MAX_SIZE jobs are submitted
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-788
>                 URL: https://issues.apache.org/jira/browse/TAP5-788
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.2, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1
>            Reporter: Massimo Lusetti
>            Assignee: Howard M. Lewis Ship
>         Attachments: patch
>
>
> ParallelExecutor service building method is backed by a bounded BlockingQueue which is the cause of RejectedExecutionException if THREAD_POOL_MAX_SIZE is reached during parallel execution of jobs.
> Changing it to use an unbounded queue will cause new jobs to wait before ParallelExecutor is able to accept new ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.