>It wont be as good as a jms solution. such a good jms solution that you ask for help on your problems... :-)
Ok, different approach. I guess (as you talk about 'user that its polling time is reached' ) that you have some kind of persistent user record with attributes like email address, polling time, .... Add a state flag like 'SynchronizationScheduled', check/set this flag before sending a message and schedule message only if it's not already set. Reset flag fom within the mdb after synchronization. Don't try to misuse a JMS message as state information "synchronization already on its way" as it will fail by design ! As soon as an mdb has picked the triggering message from the queue for a longer running synchronization (I guess that's why you want to use mdb's) there is no more indication to your jms sender that a synchronization is already currently running. Sounds like the old problem... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888452#3888452 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3888452 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
