[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: |
|
| 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: The auto-activation actually works, changes to details are immediately propagated to the public instance. But the issue we CATALINA.OUT at Author instance CATALINA.OUT at Public instance |
| 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. |