Makes quartz create a separate threadpool for different quartz cases

I have a situation where we have multiple quartz planners. In fact I am using a third party jar file that uses the quartz scheduler and I also use the quartz scheduler in my application. The quartz.configuration file looks like this:

org.quartz.scheduler.instanceName = MyScheduler
org.quartz.scheduler.instanceId = AUTO

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 10
org.quartz.threadPool.threadPriority = 5

org.quartz.jobStore.misfireThreshold = 60000

org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore

      

        
        
        
      

    

Our application obtains a scheduler instance by calling the StdSchedulerFactory () API. getScheduler ("MyScheduler"). Third party users use the StdSchedulerFactory () call. GetScheduler () API for creating your own scheduler instance. I just wanted to know if both of these schedulers would share the same thread pool or different thread pools for each of the respective schedulers.