I'm having the same problem on 4.0.5. At first I thought each mbean needed its own Timer instance but that didn't work anyway. I'm trying to upgrade from 3.2.6 and this is the last piece of the puzzle for me...running multiple mbeans worked just fine on 3.2.6.
Any help is much appreciated!
I don't know if this will help you or not but I found this in the Scheduler JavaDocs:
Scheduler Instance to allow clients to run this as a scheduling service for any Schedulable instances.
ATTENTION: The scheduler instance only allows to run one schedule at a time. Therefore when you want to run two schedules create to instances with this MBean. Suggested Object Name for the MBean are:
This way you should not run into a name conflict.