[CAMEL-19456] The invocation of the removeRoute() method is too slow …

[Luke-hbk]

…when using RAW().

Description

Working on that issue about "The invocation of the removeRoute() method is too slow when using RAW()."

Target

• I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I formatted the code using mvn -Pformat,fastinstall install && mvn -Psourcecheck

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🐫 Maintainers, please note that first-time contributors require manual approval for the GitHub Actions to run.

⚠️ Please note that the changes on this PR may be tested automatically if they change components.

🤖 Use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

If necessary Apache Camel Committers may access logs and test results in the job summaries!

[oscerd]

Minor findings.

[github-actions]

Components test results:

Total	Tested	Failed ❌	Passed ✅
7	7	1	6

[github-actions]

Core test results:

Tested	Failed ❌	Passed ✅
1	1	0

[orpiske]

Thanks for your contribution. Performance changes are always interesting.

I am requesting just a minor set of fixes.

[orpiske]

Also, out of curiosity: do you have any numbers? A JMH test, maybe?

[Luke-hbk]

I apologize, but I am currently in the process of making some changes to the code. I will commit it again after the modifications are complete.

[orpiske]

I apologize, but I am currently in the process of making some changes to the code. I will commit it again after the modifications are complete.

No worries, we are happy to receive contributions! Looking forward to the updated one!

[orpiske]

Thanks for doing the changes. There's one problem with star imports, but I am fine with the rest of the approach.

So, please, just adjust the star imports I mentioned and, IMHO, it should be good to go.

[github-actions]

Components test results:

Total	Tested	Failed ❌	Passed ✅
7	7	7	0

[github-actions]

Core test results:

Tested	Failed ❌	Passed ✅
1	1	0

[github-actions]

Components test results:

Total	Tested	Failed ❌	Passed ✅
7	7	7	0

[github-actions]

Core test results:

Tested	Failed ❌	Passed ✅
1	1	0

[github-actions]

Components test results:

Total	Tested	Failed ❌	Passed ✅
7	7	7	0

[github-actions]

Core test results:

Tested	Failed ❌	Passed ✅
1	1	0

[Luke-hbk]

Unfortunately, the tests keep failing, so I decided to check the main branch without making any modifications, and it turns out that an error occurs in camel-core.

[ERROR] Failures:
[ERROR] RecipientListWithSimpleExpressionTest.testRecipientList:66->ContextTestSupport.assertMockEndpointsSatisfied:357 mock://0 Received message count. Expected: <50> but was: <49>
[ERROR] RecipientListWithSimpleExpressionTest.testStatic:119->ContextTestSupport.assertMockEndpointsSatisfied:357 mock://8 Received message count. Expected: <50> but was: <48>
[INFO]
[ERROR] Tests run: 6100, Failures: 2, Errors: 0, Skipped: 36

[INFO] Camel :: Core ...................................... FAILURE [03:47 min]

@orpiske
Can I assist you in resolving the test failures?

[orpiske]

@Luke-hbk yes, I will take a look today.

[orpiske]

@Luke-hbk It looks fine here. It seems like a flaky test - We still have a few as we are working on the final bits of Camel 4.

The PR should be ready to go (c/c @oscerd).

[orpiske]

Let's get this one in. It would be good to have some tests for it on the CI. Merging ...

[orpiske]

Thanks for your contribution @Luke-hbk