PiotrKlimczak commented on pull request #6113: URL: https://github.com/apache/camel/pull/6113#issuecomment-923935026
I think there might be misunderstanding in all above. The problem is not with proxy itself but rather with the fact that camel spring is creating multiple CamelContext instances and then is getting confused with them. It only involves proxy because it is where the problem manifested itself for us. The same problem might possibly occur without using proxies. My problem with making the change to main branch was mostly with inability to reproduce the problem + there are so many changes that the problem might not be there anymore. Regardless of above, 3.7 is LTS so even if proxy specific, I would still expect fix as a user for it. Personally I don’t mind as we have it fixed internally this way and it works for us. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
