[jira] Created: (CONTINUUM-1799) Thread count for schedule is not configurable

Thread count for schedule is not configurable
---------------------------------------------

                 Key: CONTINUUM-1799
                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.0.2
            Reporter: Paul Spencer


Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].

This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.

[1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138572#action_138572 ]

Paul Spencer commented on CONTINUUM-1799:
-----------------------------------------

I coppied the org.apache.maven.continuum.scheduler.ContinuumScheduler component descriptor into classes/META-INF/plexus/application.xml per Emmanuel Venisse[1], but this did not change the number of threads.  I then reviewed DefaultContinuumScheduler.java and found where the Quartz schedule was created, but it appears the properties sent to the factory may not have been populated.
 

[1] http://markmail.org/message/zpuq4tm2luopyz4h

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Paul Spencer
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138575#action_138575 ]

Paul Spencer commented on CONTINUUM-1799:
-----------------------------------------

An enhancement would be to add Quartz schedule configuration to Continuums schedule configuration.  That way the "DEFAULT_SCHEDULE" count be limited to threads as a way of limiting the  impact on system resources.  This also makes it easier to run Continuum without unpacking the war.

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Paul Spencer
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138576#action_138576 ]

Paul Spencer commented on CONTINUUM-1799:
-----------------------------------------

The Affects Version/s should include 1.1.  I selected 1.0.2 in error.

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>            Reporter: Paul Spencer
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated CONTINUUM-1799:
------------------------------------

    Affects Version/s: 1.1
        Fix Version/s: 1.2

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.0.2, 1.1
>            Reporter: Paul Spencer
>             Fix For: 1.2
>
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy updated CONTINUUM-1799:
------------------------------------

    Affects Version/s:     (was: 1.0.2)

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Paul Spencer
>             Fix For: 1.2
>
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy reassigned CONTINUUM-1799:
---------------------------------------

    Assignee: Olivier Lamy

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Paul Spencer
>            Assignee: Olivier Lamy
>             Fix For: 1.2
>
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy closed CONTINUUM-1799.
-----------------------------------

    Resolution: Fixed

As I see in the code the component org.apache.maven.continuum.scheduler.ContinuumScheduler is not used anymore.
Only org.apache.maven.continuum.build.settings.SchedulesActivator is used.
This means we have to add in application.xml in the webapp, a declaration of the default plexus-quartz component with the value :
{code:xml}
<property>
  <name>org.quartz.threadPool.threadCount</name>
  <value>7</value>
</property>
{code}
7 should be enough for Continuum.
Fixed in rev 673519

> Thread count for schedule is not configurable
> ---------------------------------------------
>
>                 Key: CONTINUUM-1799
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1799
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Paul Spencer
>            Assignee: Olivier Lamy
>             Fix For: 1.2
>
>
> Their are 15 Quartz worker threads in the default configuration,  In environment swhere the number of threads per process is limited, for example HP-UX 11.x's default limit is 64, this may prevent the including of Continuum in an existing Servlet engine, i.e. Tomcat.  It appears the number of thread was configurable in components.xml, but that changed around 16-may-2006[1].
> This issue is a result of the thread titled 'Getting "java.lang.OutOfMemoryError: unable to create new native thread"Link to this message" on the continuum user mailing list.
> [1]http://svn.apache.org/viewvc/continuum/trunk/continuum-core/src/main/resources/META-INF/plexus/components.xml?r1=344177&r2=406895&diff_format=h

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira