expected_status_codes is not honored when there is an exception in the transaction
See original GitHub issueDescription
Setting a expected_status_code
will not mark an error as expected when there is an exception in the transaction.
Expected Behavior
If a transaction returns with a status code that is in the expected_status_code
an error from this transaction should be marked as expected regardless of the existence of an exception.
This is how ignored_status_code
works.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
[Java] Expected errors do not get marked with error.expected ...
You can follow the issue here: expected_status_codes is not honored when there is an exception in the transaction · Issue #376 ...
Read more >spring data - @Transactional noRollbackFor ...
It seems that since EmptyResultDataAccessException is a RuntimeException trying not to rollback upon hitting it is not a case, ...
Read more >10 Handling PL/SQL Errors
Carefully consider whether each exception handler should commit the transaction, roll it back, or let it continue. Remember, no matter how severe the...
Read more >Transactions with Spring and JPA - Baeldung
How to best set up Transactions in Spring - the configuration, ... The checked exception does not trigger a rollback of the transaction....
Read more >7 Common Mistakes You Should Avoid When Handling Java ...
Handling an exception is one of the most common but not necessarily one of the easiest tasks. It is still one of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes. Agent 7.5.0 has the fix.
Do we need to update our New Relic Agent to apply the fix?