camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-2970) JmsProducer should support non blocking routing engine
Date Sun, 25 Jul 2010 07:35:52 GMT


Claus Ibsen commented on CAMEL-2970:

trunk: 978995.

This was tough work to implement. Had to rework the request-reply logic due the async routing.
I also made the logic more easy to understand with better code comments, javadoc, and class/method
names etc.

There is a high performance {{JmsRouteRequestReplyTest}} which tests with option {{useMessageIDasCorrelationID}}
enabled. This puts a burden on the test, because it's in memory only and uses 100+ threads.
This means that in some situations a reply could be received, before Camel itself have updated
its internal correlation mapping table, with the actual JMSCorrelationID that was used (have
to get this information *after* the message has been sent). So some waiting logic is needed
so we can lookup the correlation.

> JmsProducer should support non blocking routing engine
> ------------------------------------------------------
>                 Key: CAMEL-2970
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.5.0
> The JMS component is the most complex, and we left out improvements on purpose as we
wanted 2.4 out before.
> Now its time to let the JmsProducer in request/reply mode leverage async processing so
threads are not blocked while waiting for reply.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message