[esb-issues] [JBoss JIRA] Updated: (JBESB-851) in .esb dependency problem

[ http://jira.jboss.com/jira/browse/JBESB-851?page=all ] Kurt Stam updated JBESB-851: ---------------------------- Summary: in .esb dependency problem (was: in .esb depency problem) Description: The scheduled listeners have surfaced a sneaky dependency issue in the deployment of esb archives. For instance in the jbossesb.esb we have an mbean to create the MessageStore schema if it does not already exist. Now that we have the RedeliveryService, it goes and checks for messages every 5 min according to the schedule: [code]<simple-schedule scheduleid="5-min-trigger" frequency="300" repeatCount="-1"/>[/code] Now this schedule fires right away on deployment of the esb archive. Even before the mbean was was run. And so the hsqldb for the MessageStore was not created yet: [url]http://jira.jboss.com/jira/browse/JBESB-846[/url] I have no way of specifying this "in esb dependency", and I think that is ok, as long as we do not start the listeners until the entire esb archive is deployed. I think Kev worked on something very similar a few months back and I think the problem just resurfaced in a slightly different way now that we have the scheduled listeners. was: The scheduled listeners have surfaced a sneaky dependency issue in the deployment of esb archives. For instance in the jbossesb.esb we have an mbean to create the MessageStore schema if it does not already exist. Now that we have the RedeliveryService, it goes and checks for messages every 5 min according to the schedule: [code]<simple-schedule scheduleid="5-min-trigger" frequency="300" repeatCount="-1"/>[/code] Now this schedule fires right away on deployment of the esb archive. Even before the mbean was was run. And so the hsqldb for the MessageStore was not created yet: [url]http://jira.jboss.com/jira/browse/JBESB-846[/url] I have no way of specifying this "in esb dependency", and I that is ok, as long as we do not start the listeners until the entire esb archive is deployed. I think Kev worked on something very similar a few months back and I think the problem just resurfaced in a slightly different way now that we have the scheduled listeners. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira