title: when a quartz job fires, is it a new job class instance?
body: <p>I am very new to Quartz and I have some doubts about the jobs lifecycle.</p>
  
  <p>Let's suppose I have a single job configured to do some stuff.</p>
  
  <p>The job fires and ends its work. When it fires again is it the same instance (maybe set to sleep and awaken by the scheduler) or is it a new job instance (once the job ends it is killed and when the trigger condition is met again a new job instance is created)?</p>
  
  <p>I ask such question because when I debug my application (spring 3 mvc with quartz support) I see new instances of the job and new threads with SimpleThreadPool$WorkerThreadRun() opened for every time the job is fired so that the SimpleThreadPool$WorkerThreadRun() threads are piled up and never terminated.</p>
  
  <p>I just want to know if this behaviour is allright or I'm bound to fill the memory ;-)</p>
  
  <p>Can anyone give me some explanation? Thanks in advance.</p>