Another problem that I am having is if I try to have the scheduler startup on server startup. The constructor of my MBean is getting a database connection from a JNDI pool, but it is starting before the JNDI database pools have been set up. Can I change the startup order so schedules start after the datasources are started?
im not sure if is a way to synchronize the deployment. i solved this problem straight forward:
- then i wrote a mbean which adds a notificationlistener / the handlenotification-method of this mbean will be called, when the server is started (JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231751)] Started in 50s:109ms)
- in this method, i start "all" the mbeans programmatically