[QAARQ-19] Rabbitmq-connector Created: 25/Sep/17 Updated: 06/Jun/23 |
|
| Status: | Open |
| Project: | Queued Asynchronous Activation over RabbitMQ |
| Component/s: | None |
| Affects Version/s: | 1.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Keit Tehvan | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
The startup process of the magnolia-rabbitmq-connector module has a problem:
<pause the quartz scheduler>
<do some magic>
<resume the quartz scheduler>
Now, if a runtime exception occurs in the <do some magic> phase, then starting the rabbitmq module fails (almost silently) and the scheduler stays paused. A try-finally block should be added there. Issue might be in the wrong project because the rabbitmq-connector project could not be found in here, is either hidden or does not exist? |