[
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
