1 Reply Latest reply on Dec 5, 2012 2:44 AM by Claus Ibsen

    Camel idempotent consumer degeneration

    Paweł Gdula Newbie

      Hey

       

      For some reason camel idempotent consumer slows down processing after some time. We use persistent broker on top of JDBC persistence adapter. Also camel uses JdbcMessageIdRepository. At the beginning speed is constant to ~ 30 mgs/s but after couple of hours drops to 3. We use default limitations for memory and storage (config xml in attachment). Any hint? Right now we are forced to restart ours AMQ instances to stabilize processing of messages. 

       

      watcher.queue.source

      prioritizedMessages="true"

      queuePrefetch="50000"

      prioritizedMessages="true"

      producerFlowControl="false"

      pendingSubscriberPolicy=vmCursor

       

      watcher.queue.sink

      queuePrefetch="50000"

      prioritizedMessages="true"

      producerFlowControl="false"

       

      between them we have route

       

       

       

      Edited by: gdulus on Nov 2, 2012 8:08 AM

        • 1. Re: Camel idempotent consumer degeneration
          Claus Ibsen Master

          Are you sure its related to Camel's JDBC idempotent repository? If you take it out, or switch it to a memory based etc (though its limited in # of ids it can track). But just want to get it out of the picture.

           

          Also have you setup indexes and whatnot on the JDBC schema/table you use for the JDBC idempotent. So the SQL's still perform?

           

          And if you got any SQL tool that can measure/display the performance then you can see if the SQL gets slower.