-
Notifications
You must be signed in to change notification settings - Fork 5.1k
CAMEL-20722 new log entry to log the exception #14344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Original exception is currently not being logged, as another exception gets raised from the next line within the catch block
...-test-infra-kafka/src/test/java/org/apache/camel/test/infra/kafka/services/KafkaService.java
Outdated
Show resolved
Hide resolved
|
/component-test camel-kafka Result ✅ The tests passed successfully |
|
🤖 The Apache Camel test robot will run the tests for you 👍 |
|
Functionality-wise, looks OK. Just needs the fixing that @davsclaus mentioned and it should be ready to merge. |
I pushed another commit for this already. Edit: Now realised @davsclaus meant the whitespace before the word 'Unexpected', and fixed that |
Description
This particular exception is not getting logged because another exception arises in the CATCH block.
So, this log entry will be useful to determine the particular symptom seen in builds 96, 113 (only occurs in CI but not in local)
The main test case for KafkaBreakOnFirstErrorSeekIssueIT actually works fine except for this random symptom seen only on CI.
Target
camel-3.x, whereas Camel 4 uses themainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally and I have committed all auto-generated changes