[MGNLXAA-91] Magnolia says it succesfully deleted a node while it didn't because a subscriber was unavailable Created: 12/Jun/15  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Nils Breunese Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 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.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 11:06:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.