Details
-
Bug
-
Resolution: Won't Do
-
Neutral
-
None
-
2.2.2
-
None
Description
In a development situation we sometimes have a subscriber configured, but not running.
When you try to delete a node in the configuration workspace, Magnolia shows a banner message saying the node has been successfully deleted, but actually it's still there and something like this can be found in the logs:
ERROR info.magnolia.module.scheduler.CommandJob 12.06.2015 14:43:04 -- Cannot execute command delete-default. info.magnolia.cms.exchange.ExchangeException: 1 error detected: Not able to send the deactivation request [http://localhost:8080/magnoliaPublic/.magnolia/activation]: Connection refused on magnoliaPublic8080 at info.magnolia.module.exchangetransactional.TransactionalSyndicator.syndicate(TransactionalSyndicator.java:134) at info.magnolia.module.exchangetransactional.TransactionalSyndicator.doDeactivate(TransactionalSyndicator.java:164) at info.magnolia.module.activation.BaseSyndicatorImpl.deactivate(BaseSyndicatorImpl.java:521) at info.magnolia.module.activation.commands.DeactivationCommand.execute(DeactivationCommand.java:64) at info.magnolia.commands.MgnlCommand.executeSynchronized(MgnlCommand.java:81) at info.magnolia.commands.MgnlCommand.execute(MgnlCommand.java:70) at info.magnolia.commands.chain.ChainBase.execute(ChainBase.java:101) at info.magnolia.module.scheduler.CommandJob.execute(CommandJob.java:135) at org.quartz.core.JobRunShell.run(JobRunShell.java:223) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Magnolia should detect this and not tell the user the node has been successfully deleted, when the deletion failed.
Checklists
Acceptance criteria