Topic
  • 2 replies
  • Latest Post - ‏2010-11-29T11:43:07Z by JamesaCourt
JamesaCourt
JamesaCourt
2 Posts

Pinned topic 9.7.1 scheduler thread limit

‏2010-11-17T09:12:16Z |
We have recently upgraded from SQW 9.1.2 to 9.7.1. We have around 20 processes scheduled in the admin console to start at the same time, but only 10 run at a time. There are no errors, when the first has completed the next starts. We must be hitting some kind of thread limit, but I haven't found it in the WAS console yet. The max no. of threads in the SchedulerWorkManager is 50 and all of the data source connection pools appear to be much higher than 10.

If the processes are started manually they all will run concurrently, it is only when they are scheduled that there is a problem. Any ideas where to look?

Thanks
Updated on 2010-11-29T11:43:07Z at 2010-11-29T11:43:07Z by JamesaCourt
  • JP_Parkin
    JP_Parkin
    128 Posts

    Re: 9.7.1 scheduler thread limit

    ‏2010-11-23T19:31:27Z  
    Hi James,
    The thread limit for the scheduler is a hidden configuration parameter that we're talking about exposing in a more user friendly way.

    The default number of scheduler threads is 10 ( as you have observed ). This number can be adjusted by creating a file named scheduler.properties and putting it in the Config directory.
    In 9.7 and 9.7.1 the Config directory would be found in the root of the install ( ie. /opt/IBM/ISWarehouse/Config/scheduler.properties ).
    Starting in 9.7.2 when the Config directory was moved under the WAS profile, you can now find the Config directory is a directory like /opt/IBM/ISWarehouse/AppServer/profiles/AppSrv01/IBMDataTools/Config/scheduler.properties

    These are the entries in the scheduler.properties file

    # The amount of concurrent threads that can be running a job at the same time
    org.quartz.threadPool.threadCount=10
     
    # The the number of milliseconds the scheduler will 'tolerate' a trigger to pass
    # its next-fire-time by, before being considered "misfired" 4000 ms = 4 secs
    org.quartz.jobStore.misfireThreshold=4000
    


    Increase the org.quartz.threadPool.threadCount to the maximum number of concurrent threads that you wish to support.

    Best regards,
    JP
    Updated on 2014-03-25T18:28:47Z at 2014-03-25T18:28:47Z by iron-man
  • JamesaCourt
    JamesaCourt
    2 Posts

    Re: 9.7.1 scheduler thread limit

    ‏2010-11-29T11:43:07Z  
    • JP_Parkin
    • ‏2010-11-23T19:31:27Z
    Hi James,
    The thread limit for the scheduler is a hidden configuration parameter that we're talking about exposing in a more user friendly way.

    The default number of scheduler threads is 10 ( as you have observed ). This number can be adjusted by creating a file named scheduler.properties and putting it in the Config directory.
    In 9.7 and 9.7.1 the Config directory would be found in the root of the install ( ie. /opt/IBM/ISWarehouse/Config/scheduler.properties ).
    Starting in 9.7.2 when the Config directory was moved under the WAS profile, you can now find the Config directory is a directory like /opt/IBM/ISWarehouse/AppServer/profiles/AppSrv01/IBMDataTools/Config/scheduler.properties

    These are the entries in the scheduler.properties file

    <pre class="java dw" data-editor-lang="java" data-pbcklang="java" dir="ltr"># The amount of concurrent threads that can be running a job at the same time org.quartz.threadPool.threadCount=10 # The the number of milliseconds the scheduler will 'tolerate' a trigger to pass # its next-fire-time by, before being considered "misfired" 4000 ms = 4 secs org.quartz.jobStore.misfireThreshold=4000 </pre>

    Increase the org.quartz.threadPool.threadCount to the maximum number of concurrent threads that you wish to support.

    Best regards,
    JP
    Brilliant! thanks JP