[MGNLXAA-18] XASyndicator is not able to properly report failed activation if logging stream is lost or not configured Created: 25/Jun/09  Updated: 04/Oct/13  Resolved: 25/Jun/09

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

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

Attachments: Text File stacktrace.txt    
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   

Attempt to write to an error log ends with NPE and exception is not further handled by the Syndicator due to Thread executor swallowing exceptions silently. See attached stacktrace for exception.



 Comments   
Comment by Jan Haderka [ 25/Jun/09 ]

Make sure we capture error first and log it later so that logging configuration doesn't affect UI reporting of the errors.
Done as of r26417.

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