Croway commented on PR #26311: URL: https://github.com/apache/camel/pull/26311#issuecomment-5636360281
Thanks. In 596fde80b580 the compile path is inside the lock and the monitor is a private object in both classes. On the per-thread interpreter: I kept the lock deliberately. `threadLocalStateInterpreter` would remove the serialization, but it changes what a script sees across messages on the same thread (globals written by one evaluation stay visible to the next on that thread, where `cleanup()` currently resets them), and camel-python is the legacy Jython binding while camel-python3 is where throughput work belongs. The PR description now records that trade-off; if throughput on this component matters to someone, the thread-local interpreter is the next step and the new test is the guard for it. Also added to the JIRA, as you suggested, that the test fails hard on main: every thread was reading another exchange's body and headers, so this is a correctness bug, not a tidy-up. _Claude Code on behalf of Croway_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
