Hi
Use the method executeService on the split DSL.
eg
from("activemq:queue:sping-in.queue").split().method(mySplitterBean,
"splitBody")
.parallelProcessing().executeService(threadPoolExecutor).process(new
Processor() {
On Thu, Feb 25, 2010 at 11:36 PM, Andrew Chandler wrote:
> I'm hoping so
On Thu, Feb 25, 2010 at 4:03 PM, jpcook wrote:
>
> Hi,
>
> I noticed that calling start() on camel context doesn't block the thread
> anymore which it used to do in earlier versions of camel. I think this is
> the correct behavior of Camel 2.0.
>
To my knowledge invoking start() have newer blocke
Make sure MyClass implements Serializable and you may even have to
provide a fixed serialVersionId in the class so the JVM can thread it
as the same class on both JVMs.
On Thu, Feb 25, 2010 at 11:54 PM, Alexandros Karypidis
wrote:
> Thank you for your replies. I have managed to get the VM transpo
Hi,
I'm getting a strange error on one machine (desktop running WinXP with all
the recent patches). When
I run the example at apache-camel-2.2.0/examples/camel-example-jms-file with
ant, I get a strange
error every time:
BUILD FAILED
c:\applications\apache\camel\apache-camel-2.2.0\examples\camel
Alexandros,
As Claus mentions, once you get classloaders separating your contexts
you really need to experiment to get vm routes working. The class
'MyClass' is loaded by each war's classloader and though they are
essentially the same they are treated like entirely different classes.
One way to ge
Ognian wrote:
> I'm trying to use camel with activemq on karaf 1.2
>
> I've loaded the following features:
> features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
> features:addUrl
> mvn:org.apache.activemq/activemq-karaf/5.4-SNAPSHOT/xml/features
>
>
> installing camel-osgi
Thank you for your replies. I have managed to get the VM transport to
work by putting Camel (and its dependencies) in jetty/lib/ext. However,
I am only able to exchange primitive Java types. Camel complains about
not having a type converter for it. I am using POJOs like this:
The inteface (exi
I'm hoping someone can help me out - I'm relatively new to camel,
however I've googled and tried reading the documentation.What I'm
trying to do ultimately is take a message, send it through a splitter
( a custom one in the end), and send it to processors in parallel and
then use a custom aggr
There are some none-spring java examples in the Camel in Action book. So I
guess they can be found here: http://code.google.com/p/camelinaction/
This is about as simple as it gets:
http://code.google.com/p/camelinaction/source/browse/trunk/chapter1/file-copy/src/main/java/camelinaction/FileCopi
I noticed by default with spring xml the camel consumer is not
transactional...it most likely defaults to client acknowledgement which
means the message being processed (and sleeping) will be lost. To configure
transactional via spring you add the transacted property then the message is
not lost.
On 25 February 2010 16:28, Charles Moulliard wrote:
> Hi,
>
> If we investigate what Camel 2.x project proposes in terms of
> clustering/loabalancing solution, we can categorize the solutions like this
> :
>
> 1. Loadbalancing
> loadbalance() : http://camel.apache.org/load-balancer.html
>
> 2. Clu
Hi,
If we investigate what Camel 2.x project proposes in terms of
clustering/loabalancing solution, we can categorize the solutions like this
:
1. Loadbalancing
loadbalance() : http://camel.apache.org/load-balancer.html
2. Clustering
2.1. Same JVM & CamelContext
seda:// : http://camel.apache.or
Since the logged exception was the following :
2010-02-25 16:31:57,058 ERROR [Logger.java:248] - Failed delivery for
exchangeId: acaf9632-cad3-43c0-b642-cce11b2f87c7. Exhausted after delivery
attempt: 1 caught: MyException stack trace
I tried to add retriesExhaustedLogLevel(LoggingLevel.DEBUG) t
Yes. More info here : https://issues.apache.org/activemq/browse/SMX4-456
look to the zip
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedi
I already use the handled(true) in my exception route and I don't want camel
to log my functionnal exceptions.
Julien D wrote:
>
> Hi,
>
> Since the 2.1.0 Camel is logging the exceptions at ERROR level. Is there a
> way to tell Camel that it's taking care of and not log those exceptions ?
>
>
Hi Guys,
Is there a war file (that can be deployed in tomcat) for service 4.2?
kr.
--
View this message in context:
http://old.nabble.com/ServiceMix-4.2-web-tp27714458p27714458.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I noticed that calling start() on camel context doesn't block the thread
anymore which it used to do in earlier versions of camel. I think this is
the correct behavior of Camel 2.0.
But I wondered if there was a simple example of starting the context and
stopping it exiting straight away wit
Hi,
Can you try to set the second username paramerters by setting the
message header with name of Exchange.HTTP_QUERY?
Willem
Matteo Redaelli wrote:
The problem is that I should manage 2 "username" parameters!
1)the first is a query parameter add in the remote url: it will be used to
retre
On Thu, Feb 25, 2010 at 2:25 PM, Julien D wrote:
>
> Hi,
>
> Since the 2.1.0 Camel is logging the exceptions at ERROR level. Is there a
> way to tell Camel that it's taking care of and not log those exceptions ?
>
Yes. Try using code completion on onException and see which methods you got.
There
The problem is that I should manage 2 "username" parameters!
1)the first is a query parameter add in the remote url: it will be used to
retreive info about that user
2) but, for basic authentication, camel also requires a parameter with the
same name "username" ... and the username for the basi
Hi,
Since the 2.1.0 Camel is logging the exceptions at ERROR level. Is there a
way to tell Camel that it's taking care of and not log those exceptions ?
Thanks
--
View this message in context:
http://old.nabble.com/OnException-and-log-level-tp27714424p27714424.html
Sent from the Camel - Users
Hi Charles,
I think you need to send this mail to CXF user list and you should be
able to get a karma to enhance the CXF wiki document.
Willem
Charles Moulliard wrote:
Hi,
In, the Apache Wiki page of CXF, the following concepts are presented :
- PRE-STREAM
- IN-BAND
- OUT-BAND
Can we have
Thx I will update the wiki page.
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://ww
On Thu, Feb 25, 2010 at 12:32 PM, Charles Moulliard
wrote:
> Hi,
>
> The wiki page of camel SEDA component introduces the concept of SEDA queue
> size :
>
> Slide 105
> The maximum size of the SEDA queue. The default value in Camel 2.2 or older
> is 1000. From Camel 2.3 onwards the size is unbound
Hi,
The wiki page of camel SEDA component introduces the concept of SEDA queue
size :
Slide 105
The maximum size of the SEDA queue. The default value in Camel 2.2 or older
is 1000. From Camel 2.3 onwards the size is unbounded by default.
What is the meaning of this value (Memory size, number of
Hi Paul
Thanks for coming back and letting us know you have it resolved now
and sharing the solutions to the problem.
On Thu, Feb 25, 2010 at 11:19 AM, Paul Phillips wrote:
>
> I was using camel 2.1
>
> Have upgraded to 2.2 now
>
> I have since discovered that the "extra" jdbc producers were my
I was using camel 2.1
Have upgraded to 2.2 now
I have since discovered that the "extra" jdbc producers were my own fault
anyway because of a classic mistake.
During my route a was creating a new ProducerTemplate in a processor.
This meant that it had its own ProducerCache that was empty thus m
Hi
Thanks for sharing.
Let me take a look at this to see if there is a bug in there.
On Wed, Feb 24, 2010 at 6:24 PM, ychawla wrote:
>
> Hello All,
> I was unable to get the simple language to read from my environment
> variables in Windows. I did find a workaround for this that might be
> hel
The JMS header is named
JMSPriority with a big P.
So it should be
in.header.JMSPriority
And you can use instead of the AFAIR
On Thu, Feb 25, 2010 at 2:17 AM, Andrew Harvey wrote:
> Hi there,
>
> I've been battling for a few days to get a resequencer working with ActiveMQ
> based on messag
Hi,
In, the Apache Wiki page of CXF, the following concepts are presented :
- PRE-STREAM
- IN-BAND
- OUT-BAND
Can we have a clear definition or a clarification of these concepts in the
wiki page please because it is difficult to understand what they are related
to (ex : PRE_STREAM phase is remo
30 matches
Mail list logo
