Re: JMS Component WITHOUT Spring

On 7/19/2010 8:13 AM, Claus Ibsen wrote: Hi On Mon, Jul 19, 2010 at 8:06 PM, Ron Smith wrote: Where I work, Spring has been declared "evil" so I am attempting to use camel without any of the Spring JARs but I can't find any examples of how to setup a JMS component without a Spring dependency

propagate bean invocation exception back to remote caller

I'm pretty new to Camel, and I'm a little confused about exception handling. I'm working on a client/server application whose communication happens over camel/jms. I'm taking advantage of Camel's bean invocation support so that the client can invoke remote services which are exported by the

Re: propagate bean invocation exception back to remote caller

p://twitter.com/willemjiang Jim Newsham wrote: I'm pretty new to Camel, and I'm a little confused about exception handling. I'm working on a client/server application whose communication happens over camel/jms. I'm taking advantage of Camel's bean invocation support so tha

Re: propagate bean invocation exception back to remote caller

On 8/3/2010 9:08 PM, Claus Ibsen wrote: On Wed, Aug 4, 2010 at 6:19 AM, Jim Newsham wrote: Hi Willem, Thanks for the fast reply. After adding the transferException option to the jms url on both the client and the server, I am now seeing the exception propagate to the client. The only

how to use jms temporary queue (without jmsreplyto)

The documentation on jms temporary destinations is very sparse. I'm struggling to understand how I can use a jms temporary queue with Camel, outside the use case of request/reply, which Camel already handles automatically. I want to create a route which receives messages on a temporary jms

Re: how to use jms temporary queue (without jmsreplyto)

We wanted a queue scoped to the lifetime of the connection, and scoped to a single jms client, so temporary jms queues are a pretty good fit. When the connection dies, the queue and its contents can be automatically discarded. No ACL needed for the queue. etc. It's essentially a one-way e

long-running requests over jms

Hi everyone, We are using Camel + ActiveMQ, with InOut messages and bean() routes, as a form of flexible remoting (remote service invocation). This has been working out quite well for us so far. One issue that we've run into is that while most service requests complete very quickly, some pa

Re: long-running requests over jms

e JIRA. If not create a new one and refer to this thread (using nabble etc.) On Tue, Dec 21, 2010 at 12:27 AM, Jim Newsham wrote: Hi everyone, We are using Camel + ActiveMQ, with InOut messages and bean() routes, as a form of flexible remoting (remote service invocation). This has been working

Re: long-running requests over jms

blocking thread to wait for the response. Willem On 12/21/10 7:27 AM, Jim Newsham wrote: Hi everyone, We are using Camel + ActiveMQ, with InOut messages and bean() routes, as a form of flexible remoting (remote service invocation). This has been working out quite well for us so far. One issue

Re: long-running requests over jms

ly routes). I was hoping that communication layer could handle the complexity internally and expose a uniform model to the service layer. Seems like I don't have a lot of agreement on this idea, though. Thanks for the alternative suggestions. Regards, Jim Best regards Christian Am 22

Re: Cannot handle Exception thrown from Splitter Expression

On 2/10/2011 9:41 AM, rmorris wrote: I think I've found a similar case when the exception occurs within a split().method() In this case, the exception is thrown inside the method() and doesn't make it to the onException() handler. Adding a .onException() into the direct://testsplitter route does

exception handlers and jms (connection pool) failure

Hi, We are using Camel 2.5.0 and ActiveMQ 5.4.1. In our application, we see that failure to obtain a jms connection from the connection pool results in an unhandled exception which bubbles up to the caller, instead of it being handled by one of the global exception handlers that we have con

Re: exception handlers and jms (connection pool) failure

ssage, and there is no any camel route involved. If you want to test the camel route with the error handler you can add route like this from("direct:start").to("activemq:queue:myqueue"); Willem On 4/19/11 6:03 AM, Jim Newsham wrote: Hi, We are using Camel 2.5.0 and ActiveMQ

set jms reply to in message header

Hi, I'm using Camel 2.7.1 and ActiveMQ 5.5.0. I've been trying to set the jms reply-to destination by message header and have had no luck. The documentation at http://camel.apache.org/jms.html seems to imply this is possible, so perhaps I'm not doing it quite correctly. I created a very s

Re: set jms reply to in message header

P.S. I see that the header name I used in the example I pasted was "replyTo". Note that I have also tried "JMSReplyTo" with the same result. Jim On 5/23/2011 4:07 PM, Jim Newsham wrote: Hi, I'm using Camel 2.7.1 and ActiveMQ 5.5.0. I've been trying to set

Re: set jms reply to in message header

Thank you for the response Willem, however the result is the same using "JMSReplyTo" as the header name. Regards, Jim On 5/23/2011 4:19 PM, Willem.Jiang wrote: Hi The header name should be "JMSReplyTo". Willem

Re: set jms reply to in message header

ue:bar") .to("mock:result"); from("activemq:queue:foo") .transform(body().prepend("Hello ")); } On 5/24/11 10:31 AM, Jim Newsham wrote: Thank you for the response Willem, however the result is the

Re: set jms reply to in message header

myqueue"); Thanks, Jim On 5/23/2011 5:21 PM, Willem Jiang wrote: Hi, Can you change the queue name to queue:myqueue? On 5/24/11 11:13 AM, Jim Newsham wrote: Hi Willem, Unfortunately I do not know the reply-to queue name at the time the route is created, which is why I hoped to set the re

Re: set jms reply to in message header

using header name "camelJmsReplyTo" to set the jms replyTo property. [1]https://issues.apache.org/jira/browse/CAMEL-4008 On 5/24/11 12:47 PM, Willem Jiang wrote: I can reproduce the error and will dig the code for it. On 5/24/11 11:29 AM, Jim Newsham wrote: I have tried "que

Re: set jms reply to in message header

wse/CAMEL-4008 On 5/24/11 12:47 PM, Willem Jiang wrote: I can reproduce the error and will dig the code for it. On 5/24/11 11:29 AM, Jim Newsham wrote: I have tried "queue:myqueue" and the result is the same. I tried both: //exchange.getIn().setHeader("JMSReplyTo", ActiveMQCo

TypeConverterLoaderException in webstart

We've come across a problem in Camel 2.7.1 where Camel fails to start up due to a TypeConverterLoaderException. This is a regression, as we've had no such problem in Camel 2.5.0. Is this a known issue? Googling around, I've found [1], which states: My second problem is that it's current

Re: TypeConverterLoaderException in webstart

geScanFilter filter) { // do nothing here } } [1] http://camel.apache.org/advanced-configuration-of-camelcontext-using-spr ing.html -Original Message- From: Jim Newsham [mailto:jnews...@referentia.com] Sent: Freitag, 27. Mai 2011 04:55 To: users@camel.apache.org Subje

Re: TypeConverterLoaderException in webstart

void removeFilter(PackageScanFilter filter) { // do nothing here } } [1] http://camel.apache.org/advanced-configuration-of-camelcontext-using-spr ing.html -----Original Message- From: Jim Newsham [mailto:jnews...@referentia.com] Sent: Freitag, 27. Mai 2011 04:55 To: users@camel.apache.or

Re: TypeConverterLoaderException in webstart

lcontext-using-spr ing.html -Original Message- From: Jim Newsham [mailto:jnews...@referentia.com] Sent: Freitag, 27. Mai 2011 04:55 To: users@camel.apache.org Subject: TypeConverterLoaderException in webstart We've come across a problem in Camel 2.7.1 where Camel fails to start up due t

async send with preserved order

Is it possible to send asynchronously while preserving order? For example: for (int i = 0; i <= COUNT; i++) { Object body = Integer.valueOf(i); producerTemplate.asyncCallbackRequestBody(URL, body, callback); } Assuming that "URL" is a FIFO queue, is there some way f

Re: async send with preserved order

. See the org.apache.camel.util.concurrent package. On Wed, Jun 1, 2011 at 7:04 AM, Jim Newsham wrote: Is it possible to send asynchronously while preserving order? For example: for (int i = 0; i<= COUNT; i++) { Object body = Integer.valueO

Re: TypeConverterLoaderException in webstart

Thanks Andreas, this fix worked for me. Appreciate the help! Regards, Jim On 6/6/2011 12:12 AM, Andreas Kuhtz wrote: Found out that you must return at least one converter to make camel happy ... Use this updated method: public Set> findAnnotated(Class annotation,

slow reply for jms component when url contains replyTo

I'm using Camel 2.7.1 on top of ActiveMQ 5.5.0. For some reason, when I specify a custom replyTo destination on the endpoint url, the time it takes for the producer to receive a reply increases drastically. The curious thing is that the time to receive a reply is almost exactly 1 second. W

Re: slow reply for jms component when url contains replyTo

the Camel route? Or is the queue used for other purposes as well? Is there a special reason why you want to use a fixed reply to queue? On Fri, Jul 8, 2011 at 11:14 PM, Jim Newsham wrote: Hi Claus, I enabled trace logging. I'm attaching the logs (for both client and server; both wit

Re: slow reply for jms component when url contains replyTo

On 7/11/2011 7:25 PM, Claus Ibsen wrote: On Mon, Jul 11, 2011 at 10:12 PM, Jim Newsham wrote: Hi Claus, Thanks for opening the jira issue, and for your comments. To answer your questions: 1. We use fixed reply-to queues which are exclusive to Camel. 2. We need a fixed reply-to queue to

jms concurrentConsumers is not competing consumers

We are using Camel 2.9.0. We are using the "concurrentConsumers=n" option on our jms consumer endpoint so that we can handle numerous InOut requests concurrently. In Camel documentation, this option is described as supporting competing consumers, which I interpret to mean a pool of threads

Re: jms concurrentConsumers is not competing consumers

in here: http://camel.apache.org/jms.html no matter how many concurrentConsumer you set. Regards, Ngoc Hai. ________ From: Jim Newsham To: users@camel.apache.org Sent: Saturday, February 4, 2012 10:55 AM Subject: jms concurrentConsumers is not competing consumers We

Re: jms concurrentConsumers is not competing consumers

, David Karlsen wrote: Read the section on "Request-reply over JMS" - you're looking for the threads option. 2012/2/6 Jim Newsham: Hi Ngoc Hai, I'm not talking at all about the producer side where replies are processed, but the consumer side where requests are being re

Re: jms concurrentConsumers is not competing consumers

I'm attaching a simplified test case in case anybody wants to have a look (code attached at bottom). For the following test case, 12 requests are made. In the client, we log when a request is sent, and when the reply is received. Each request completes instantaneously, except for request 0

Re: jms concurrentConsumers is not competing consumers

option on our jms consumer endpoint so that we can handle numerous InOut requests" which I read as Producer with InOut MEP - and from the docs I read that should use the threads options. If you only have incoming (e.g. InOnly) then I read the docs as concurrentConsumers should do it. Maybe

Re: jms concurrentConsumers is not competing consumers

Well, I haven't gotten a satisfactory response to this inquiry. Really looks like a bug to me. Any Camel contributors care to comment? Thanks, Jim On 2/6/2012 2:22 PM, Jim Newsham wrote: The MEP is InOut ("request/reply"). There are two participants, a consumer and a pro

Re: jms concurrentConsumers is not competing consumers

message's order, I have not tested that myself though. Regards, Ngoc Hai. From: Jim Newsham To: users@camel.apache.org Sent: Wednesday, February 15, 2012 8:15 AM Subject: Re: jms concurrentConsumers is not competing consumers Well, I haven't gotten a