I have an interesting problem concerning the QuartzScheduler running in JBoss and activated by Seam.
My application submits jobs to run in background threads by issuing the following command:
Object handle = this.dispatcher.scheduleAsynchronousEvent("runQuery", packet);
(this after creating a dispatcher via org.jboss.seam.async.AbstractDispatcher.instance() method)
A 'run' method is then executed by the background thread:
@Observer("runQuery") public void run(AbstractQueryPacket packet) ...
This works fine when I have ONE or TWO copies of the webapp running in my JBoss but when I have THREE or more, the background thread simply doesn't get scheduled: It is as if the work I give it to do vanishes into thin air. There are no exceptions and nothing to indicate what is going wrong.
Set the Quartz log level (org.quartz) to debug/tace, and see what that gives you. Are you using a DB store for quartz?
If so, you can inspect the tables and see what jobs and triggers are created. If, on the other hand,
you are using the RAM job store, all applications should be independent, and it shouldn't matter how many you have deployed.