[MGNLOBS-10] Automatic activation of user details (using observation module listener) blocks system by just logging Created: 08/Jul/10  Updated: 08/Jul/10  Resolved: 08/Jul/10

Status: Closed
Project: Observation
Component/s: None
Affects Version/s: 1.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Michael Rauch Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: activation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File config.modules.observation.config.listenerConfigurations.activateUserChanges.xml    
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   

To automatically activate user changes of user details, we configured a listener at author instance as explained on the following wiki page:
http://wiki.magnolia-cms.com/display/WIKI/Auto+activation+of+user+details

The auto-activation actually works, changes to details are immediately propagated to the public instance. But the issue we
are facing is, that an endless-loop creates log messages multiple times a second at author and public instance. This leads to
a system that is blocked by just logging.

CATALINA.OUT at Author instance
2010-06-28 12:57:50,541 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
2010-06-28 12:57:50,740 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
2010-06-28 12:57:50,967 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
2010-06-28 12:57:51,198 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
2010-06-28 12:57:51,391 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
2010-06-28 12:57:51,612 INFO .magnolia.module.exchangesimple.BaseSyndicatorImpl: Exchange: activation succeeded [/admin/editors/supereditor]
...

CATALINA.OUT at Public instance
2010-06-28 12:55:22,095 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:22,364 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:22,632 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:22,901 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:23,215 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:23,564 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
2010-06-28 12:55:23,770 INFO nolia.module.exchangetransactional.XAReceiveFilter: User superuser successfuly activated /admin/editors/supereditor on ROOT.
...



 Comments   
Comment by Jan Haderka [ 08/Jul/10 ]

The problem is not a logging, but your listener reacting too eagerly. After piece any content is activated, it's meta data are updated with the timestamp of last activation, which your listener treats as a change and initiates yet another activation and so on. What you need to do is to make sure you exclude MetaData updates from the trigger. It have been discussed in the user list in the past. Feel free to update the wiki page with the info and correct settings to exclude the MetaData from triggering the update once you sort it out.

Generated at Mon Feb 12 10:23:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.