[MGNLXAA-14] Non matching subscriber in transaction is incorrectly interpreted as failure to activate. Created: 08/Jan/09  Updated: 04/Oct/13  Resolved: 08/Jan/09

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.0.2, 1.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by MGNLXAA-16 Activation to 2 public instances fail... 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

 Description   

When activating piece of content, having active but not matching subscriber in the set of subscribers to which content is being pushed is incorrectly interpreted as an error to activate on given subscriber.



 Comments   
Comment by Jan Haderka [ 08/Jan/09 ]

done as of r21085.

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