Sorry, by http-endpoint I meant an smtp-endpoint, not that it matters much to
my problem, but it might cause some confusement as to what I'm trying to do.
--
View this message in context:
http://camel.465427.n5.nabble.com/onException-and-process-tp2740331p2740337.html
Sent from the Camel - Users
Hi,
I'm having a problem using a .process inside my onException handling. I
enter the Processor just fine, but exiting it, causes the original exception
to be thrown.
What I want to do is basicly;
onException(ExceptionType.class)
.useOriginalBody()
.handled(true)
.setHeader("subject", constant(
This is insane. Having 5000 threads is not idea for the JVM to handle.
Its not like you got a CPU with 5000 cores (at least not yet).
On Fri, Aug 27, 2010 at 3:20 PM, Charles Moulliard wrote:
> Hi,
>
> To be able to allow 5000 concurentConsumers to consume message from a jms
> queue
> ("jmsCon
Hi,
To be able to allow 5000 concurentConsumers to consume message from a jms
queue
("jmsConsumer:queue:VirtualQueueConsumer.highVolume?concurrentConsumers=5000"),
I have created a threadPool in camel of 2000 threads.
Maybe this value is too high but I would like to see if I can consume more
quick
@Claus Ibsen
I used this archetype : camel-archetype-java ..Thanks for all the support.
--
View this message in context:
http://camel.465427.n5.nabble.com/XPath-Scala-DSL-Problem-tp2739867p2739926.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hello friends ,
That was a silly mistake. A properties file was copied in the folder which
was causing the error.
--
View this message in context:
http://camel.465427.n5.nabble.com/XPath-Scala-DSL-Problem-tp2739867p2739923.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Fri, Aug 27, 2010 at 1:58 PM, mitul1411 wrote:
>
> Hello all, I am using the Camel Scala example which comes with the default
> camel java archetype
Which java archetype? Don't you mean scala archetype?
Can you show the mvn command you run.
And what do you do next? To get this failure?
> I
Hello all, I am using the Camel Scala example which comes with the default
camel java archetype
I am getting the following error : ERROR Failed delivery for exchangeId:
ad7d5070-54a5-4e0d-a6c3-e97c86b5b739. Exhausted after delivery attempt: 1
caught: org.apache.camel.builder.xml.InvalidXPathExpres
Hi Charles
Learn to look in the unit tests.
See JmsAutoStartupTest
On Fri, Aug 27, 2010 at 1:48 PM, Charles Moulliard wrote:
> Hi,
>
> Using the following JMS option (autoStartup), it is possible to start/stop
> the connection with the JMS broker. So using the following uri definition,
> we ca
Hi,
Using the following JMS option (autoStartup), it is possible to start/stop
the connection with the JMS broker. So using the following uri definition,
we can stop the listener when we create the route
"uri="activemq:queue:toto?autoStartup=false". Is there a way to change this
attribute later on
Try with Camel 2.5
On Fri, Aug 27, 2010 at 12:42 PM, Charles Moulliard
wrote:
> Hi,
>
> When we configure a route to connect to a queue through a JMSListener, the
> route starts to consume messages even if we add the option .noAutoStartup()
> in the route definition ?
>
> from(activemq:queue:tot
Hi,
When we configure a route to connect to a queue through a JMSListener, the
route starts to consume messages even if we add the option .noAutoStartup()
in the route definition ?
from(activemq:queue:toto).noAuToStartup().to()
Regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET
Hi
I am using Camel-2.2.0 and camel-ftp-2.2.0.
The issue is that i am using camel-ftp to create file on a windows FTP
server and the file must be in windows-1252 :-(
My code is running on a Linux server (running
apache-servicemix-4.2.0-fuse-01-00).
I have tried to set parameter on the endpoi
On Fri, Aug 27, 2010 at 11:56 AM, Charles Moulliard
wrote:
> Thx. For the future, it could be interesting that the message (exchange) is
> intercepted and processed asynchronously without impacting the existing
> route.
That is what wiretap EIP can do.
And you are free to write your own code to
Thx. For the future, it could be interesting that the message (exchange) is
intercepted and processed asynchronously without impacting the existing
route.
On Fri, Aug 27, 2010 at 11:49 AM, Yiannis Mavroukakis <
imavrouka...@gameaccount.com> wrote:
> Hmm according to this
> http://camel.apache.org
Hmm according to this
http://camel.apache.org/intercept.html
It emulates AOP, as it applies to all the From routes. In your instance it
will be intercepted once as the page for Intercept details, right after the
from("direct").
On 27 August 2010 10:36, Charles Moulliard wrote:
> Hi,
>
> I would
On Fri, Aug 27, 2010 at 11:36 AM, Charles Moulliard
wrote:
> Hi,
>
> I would like to know when we use the InterceptFrom strategy if we create two
> exchanges (one for the interceptor and the other for the route) and if the
> processing of the two exchanges is done in parallel or in
> asynchronous
Hi,
I would like to know when we use the InterceptFrom strategy if we create two
exchanges (one for the interceptor and the other for the route) and if the
processing of the two exchanges is done in parallel or in
asynchronous way ?
ex :
InterceptFrom().to(log)
from("direct").to("bean:service")
Please ignore my answer, I didn't go through the stack trace carefully.
It's the seda components issue, not the activemq component issue.
Willem
Willem Jiang wrote:
Hi,
I think this can be configure from ActiveMQ, and Camel has nothing to do
with it.
Can you go through the ActiveMQ site for
I did bit of investigation at eclipse side and noticed that Eclipse only
invokes terminate and doesn't call Ctr C equivalent shutdown. There is an
existing bug in eclipse as shown below which won't be fixed.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=38016
So, i have found a way to initiat
20 matches
Mail list logo
