[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: |
|
||||||||
| Issue Links: |
|
||||||||
| 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. |