[
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
