<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache-Camel on Tushar Choudhary</title><link>https://tushar-c23.github.io/tags/apache-camel/</link><description>Recent content in Apache-Camel on Tushar Choudhary</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 15 Aug 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://tushar-c23.github.io/tags/apache-camel/index.xml" rel="self" type="application/rss+xml"/><item><title>Camel sorts your URI parameters — except when it doesn't</title><link>https://tushar-c23.github.io/posts/camel-uri-normalization/</link><pubDate>Sat, 15 Aug 2026 10:00:00 +0530</pubDate><guid>https://tushar-c23.github.io/posts/camel-uri-normalization/</guid><description>&lt;p&gt;We recently shipped a fix at work for a Kafka producer leak: a URI was being built with the record key baked into it, so every distinct key produced a distinct Camel endpoint, and every endpoint got its own &lt;code&gt;KafkaProducer&lt;/code&gt;, its own network thread, and its own 10-thread worker pool. One string, hundreds of producers.&lt;/p&gt;
&lt;p&gt;Fixing it was easy. Understanding &lt;em&gt;why&lt;/em&gt; Camel behaved that way sent me into &lt;code&gt;camel-core&lt;/code&gt;, and on the way I tripped over something I haven&amp;rsquo;t seen written down anywhere.&lt;/p&gt;</description></item></channel></rss>