Re: [DISCUSS] - JmsConsumer support for asynchronous routing engine - Higher scalability

I think one more important downside point of using user threads to dispatch messages from a JMS provider is that you loose guaranteed order of delivery and the onus of sorting them and guaranteeing message delivery to recipients is now put onto application code. I think you would only want to do t

Re: Camel JMS InOut Performance Issues with Correlation Mechanism

Use Camel JMS Component's configuration parameter: useMessageIDAsCorrelationID=true from(amq:...).inOut(jms:...?useMessageIDAsCorrelationID=true) Marat On Tue, Jan 25, 2011 at 11:32 AM, Christian Mueller < christian.muel...@gmail.com> wrote: > > Thanks for your response Claus. I had already a

Re: Camel JMS InOut Performance Issues with Correlation Mechanism

messages that match that unique value, thus getting only the reply messages destined to this producer. http://issues.apache.org/activemq/browse/CAMEL-490 Thanks, Marat On Mon, Feb 1, 2010 at 1:46 PM, Marat Bedretdinov < marat.bedretdi...@gmail.com> wrote: > It's been a while since I

Re: Camel JMS InOut Performance Issues with Correlation Mechanism

It's been a while since I looked at this code. I would verify that your changes will not break local transaction support. I suspect that this could be an issue if you were to simply block the producer with a timed receive call. There is a bunch of tests in Camel unit tests. Are they all passing?

[jira] Commented: (CAMEL-1837) camel-ftp - Add support for FTPS

[ https://issues.apache.org/activemq/browse/CAMEL-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56306#action_56306 ] Marat Bedretdinov commented on CAMEL-1837: -- Hi Christian, Claus, Take a loo

[jira] Commented: (CAMEL-2249) Wrong handling of useMessageIDAsCorrelationID

[ https://issues.apache.org/activemq/browse/CAMEL-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56232#action_56232 ] Marat Bedretdinov commented on CAMEL-2249: -- Hi Christian, I generally agree

[jira] Issue Comment Edited: (CAMEL-2249) Wrong handling of useMessageIDAsCorrelationID

[ https://issues.apache.org/activemq/browse/CAMEL-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56232#action_56232 ] Marat Bedretdinov edited comment on CAMEL-2249 at 12/2/09 5:2

[jira] Commented: (CAMEL-2001) Transactions do not work properly with JMS producer endpoint when processing InOut exchanges

[ https://issues.apache.org/activemq/browse/CAMEL-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54110#action_54110 ] Marat Bedretdinov commented on CAMEL-2001: -- Fintan, I haven't looked a

[jira] Issue Comment Edited: (CAMEL-2001) Transactions do not work properly with JMS producer endpoint when processing InOut exchanges

[ https://issues.apache.org/activemq/browse/CAMEL-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54110#action_54110 ] Marat Bedretdinov edited comment on CAMEL-2001 at 9/9/09 8:3

Re: JMS queue / JNDI instead of physical name

May be this will help? http://fusesource.com/docs/router/1.6/component_ref/JMSComp.html Marat On Tue, Jul 14, 2009 at 2:18 PM, fjaouen wrote: > > Hi, > > I try to use Apache camel JMS (http://camel.apache.org/jms.html). And it > works fine if I use physical name. But I would like to use a logic

Re: [DISCUSS - Camel 2.0 - Internal API reworkings] - Channel and AsyncProcessor

A while ago (last year) I've been chatting with Hiram, and we've agreed that we could extend the Camel to support TX for InOut Exchanges, where we would employ an AsynchProcessor for the IN message exchange flow and then deliver the OUT message flow via a separate thread. This effectively would ac

[jira] Commented: (CAMEL-1543) Apply removeHeader also to the underying JMS message delegate

[ https://issues.apache.org/activemq/browse/CAMEL-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51283#action_51283 ] Marat Bedretdinov commented on CAMEL-1543: -- Good point. If I recall correctly

[jira] Commented: (CAMEL-1541) Provide constants for headers CamelFilePath and CamelFileParent

[ https://issues.apache.org/activemq/browse/CAMEL-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51282#action_51282 ] Marat Bedretdinov commented on CAMEL-1541: -- may be use ExchangeProperty f

[jira] Commented: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51051#action_51051 ] Marat Bedretdinov commented on CAMEL-1461: -- Claus, Thanks for applying the p

[jira] Commented: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51030#action_51030 ] Marat Bedretdinov commented on CAMEL-1461: -- Claus, Yes I did manage to get al

[jira] Updated: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Bedretdinov updated CAMEL-1461: - Attachment: CAMEL-1461-2009-04-05-01-58.patch > A request route with a topic n

[jira] Commented: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51027#action_51027 ] Marat Bedretdinov commented on CAMEL-1461: -- Claus, Ok I think there are a co

[jira] Issue Comment Edited: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51022#action_51022 ] Marat Bedretdinov edited comment on CAMEL-1461 at 4/4/09 10:4

[jira] Issue Comment Edited: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51022#action_51022 ] Marat Bedretdinov edited comment on CAMEL-1461 at 4/4/09 10:4

[jira] Issue Comment Edited: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51022#action_51022 ] Marat Bedretdinov edited comment on CAMEL-1461 at 4/4/09 10:3

[jira] Commented: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51022#action_51022 ] Marat Bedretdinov commented on CAMEL-1461: -- Claus, I disagree. > The pro

[jira] Commented: (CAMEL-1461) A request route with a topic node incurs a 20 second wait and refers to the wrong MEP.

[ https://issues.apache.org/activemq/browse/CAMEL-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51018#action_51018 ] Marat Bedretdinov commented on CAMEL-1461: -- Michael, I think your analysi

[jira] Commented: (CAMEL-1509) DefaultCamelContext.isStarting returns incorrect status

[ https://issues.apache.org/activemq/browse/CAMEL-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50974#action_50974 ] Marat Bedretdinov commented on CAMEL-1509: -- The logic in the ServiceSuppor

Re: Need Camel Wiki edit karma

Thanks. On Mon, Mar 23, 2009 at 2:53 PM, Claus Ibsen wrote: > On Mon, Mar 23, 2009 at 7:49 PM, Marat Bedretdinov > wrote: > > My username is 'marat' > Karma granted. > > > > > Thanks, > > Marat > > > > On Mon, Mar 23, 2009 at 2:36 PM, C

Re: Need Camel Wiki edit karma

My username is 'marat' Thanks, Marat On Mon, Mar 23, 2009 at 2:36 PM, Claus Ibsen wrote: > On Mon, Mar 23, 2009 at 7:31 PM, Marat Bedretdinov > wrote: > > Claus, > > > > Could you give me Camel wiki edit karma so that I can document my latest > > pa

Need Camel Wiki edit karma

Claus, Could you give me Camel wiki edit karma so that I can document my latest patch? Thanks, Marat

[jira] Updated: (CAMEL-1474) On the wire headers are dropped inside camel route between two CxfEndpoints

[ https://issues.apache.org/activemq/browse/CAMEL-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Bedretdinov updated CAMEL-1474: - Attachment: camel-cxf-CAMEL-1474-2009-03-20.patch.txt > On the wire headers

[jira] Created: (CAMEL-1474) On the wire headers are dropped inside camel route between two CxfEndpoints

Issue Type: Bug Components: camel-cxf Affects Versions: 1.6.0 Reporter: Marat Bedretdinov Fix For: 1.6.1 Currently if there is a Camel route that involves two or more cxf endpoints, then the on the wire message headers such as SOAP headers are