[MGNLXAA-26] TransactionalSyndicator incorrectly reports a "Non EE subscriber detected" when the subscriber in question is not installed/ready Created: 02/Feb/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

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

Attachments: Text File MGNLXAA-26.stacktrace.txt    
Issue Links:
Relates
relates to MGNLACTIVATION-74 Wrong configuration of XAA after upgr... Closed
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   

Not sure this still happens with 1.2, to be verified:

If I start a regular ee bundle, let the install process run for the author instance, and try to activate content to the public before is go through the install process of the public instance, TransactionalSyndicator reports "Non EE subscriber detected". Ideally, it should be a little more precise than that, the error message is quite misleading. (we're not even sure if the url we're taping into is a Magnolia instance at all)



 Comments   
Comment by Jan Haderka [ 02/Feb/11 ]

likely culprit is the if/else block at TransactionalSyndicator.java:154-159 assuming that lack of response is non EE installation. OTOH it has no means to check the response, so it's the activate method itself that should throw an exception rather then failing silently.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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