Maybe there is a bug and the subscriptionSpecs are not unregistered when the SA is undeployed. I guess this would cause some errors to be printed in the console without really disturbing the process more than that. If you confirm that this is the problem, please raise a JIRA. If you want to try and fix it, I'd say the problem is the core container when an ActivationSpec is unregistered (this should be done from the lwcontainer), the associated subscriptionSpecs should be removed from the registry too.
On 5/30/07, kitplummer <[EMAIL PROTECTED]> wrote:
...because a subscriptionSpec in the servicemix.xml config file for the SA links to another component. The "other" component continues to attempt to deliver messages to the undeployed service. Any ideas? Kit -- View this message in context: http://www.nabble.com/Undeploying-SA-Causes-Undeliverable-Messages...-tf3841922s12049.html#a10879094 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
