I don’t use AMQP, so this is guess - but it sounds like the AMQP endpoint is
creating a new connection to the destination for every message. I’ve hit
similar issues with camel-jms, and I resolve them by using a pooled connection
factory.
Sorry - not much help from me. Maybe an AMQP expert will chime in.
> On Apr 4, 2016, at 9:34 AM, michal1988 <michalgadzin...@gmail.com> wrote:
>
> Hi Quinn, Thanks for the response. I use the newest version 2.17 the same
> situation with 2.16.2.
>
> I cannot shared the code, my terminal is not connected to internet :/
>
> I will try to describe it.
>
> The simplified version of the code is:
>
>
> Create DefaultCamelContext().
> I create a AMQPComponent like in tutorials.
> Add it via context.addComponent("amqp", amqpComp").
>
> call addRoutes with RouteBuilder() which create a Route(with json parsing
> inside of it).
>
> Inside of it I read from queue via:
>
> from("amqp:queue:name").threads(3,7).unmarshal().json(.......).process(new
> Processor) and then:
>
> .marshal().json().to("amqp:queue:name")
>
>
> Every usage of route create a new connection to AMQP broker so the UNIX
> descriptor is reserved. In my system there is going to be high number of
> messages.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/AMQPComponent-routes-running-out-of-UNIX-descriptors-tp5780431p5780447.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
