Well, Here is one usecase we are currently facing. We have lots and lots of timers spread around over many processinstances. The timers are pretty much only expring once every few months so are long outstanding timers. We started of with EJB timers untill recently i discovered exactly this, that they are instantiating one thread per timer/job. In my specific scenario I am also currently investigating not using EJB timers as the jobScheduler because this causes way to much threads open in the application server and eventually performance will decrease dramatically dependant upon the resources of the machine... Not really sure wich route we will take though... As allways any ideas appreciated ;-) Regards, leo "kukeltje" wrote : I miss your point... | | They are different because in JEE we can use something that is already there and is proven. For the other envs the jobexecutor is there | | Making a new JEE jobexecutor seems illogical to me View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187685#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...