Re: Settings for threads per endpoint

[tomaswahlgren]

In the end I got around this by using http4 component instead of jetty, and
the component settings
 "setConnectionsPerRoute" and "setMaxTotalConnections" combined with the
"threads" setting on the route.

This seems to give me the unlimited number of parallell sessions that I was
after.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Settings-for-threads-per-endpoint-tp5774319p5774378.html
Sent from the Camel - Users mailing list archive at Nabble.com.

sFTP 'listFiles' does not work after upgrade from 2.15.x to 2.16.0

[nicoruti]

Dear camel-community

I have the following route (simplified):

RemoteFileEndpoint ftpEndpoint =
endpoint("sftp:ftp.myhost.com/?username=user&password=x&delay=4320&disconnect=true",
RemoteFileEndpoint.class);
ftpEndpoint.setFilter(new MyDownloadFileFilter());
from(ftpEndpoint)
 .to("file:{{configured.dl.dir}}")
 .log("Downloaded ${header.CamelFileName} over FTP")
 .to("direct:further-processing")
.end();


This route worked as expected and I could download all files that are
accepted by MyDownloadFileFilter.
After upgrading from 2.15.x to the latest camel version 2.16.0, I faced the
following exception:


WARN ] 2015-11-25 09:41:12.988 [Camel (camel-1) thread #2 -
sftp://ftp.myhost.com/] RemoteFilePollingConsumerPollStrategy - Trying to
recover by disconnecting from remote server forcing a re-connect at next
poll: sftp://u...@ftp.myhost.com:22
[WARN ] 2015-11-25 09:41:12.993 [Camel (camel-1) thread #2 -
sftp://ftp.myhost.com/] SftpConsumer - Consumer
Consumer[sftp://ftp.myhost.com/?delay=4320&disconnect=true&password=xx&username=user]
failed polling endpoint:
Endpoint[sftp://ftp.myhost.com/?delay=4320&disconnect=true&password=xx&username=user].
Will try again at next poll. Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException -
Cannot list directory: .]
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
list directory: .
at
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:597)
~[camel-ftp-2.16.0.jar:2.16.0]
at
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:574)
~[camel-ftp-2.16.0.jar:2.16.0]
at
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:115)
~[camel-ftp-2.16.0.jar:2.16.0]
at
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:79)
~[camel-ftp-2.16.0.jar:2.16.0]
at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:119)
~[camel-core-2.16.0.jar:2.16.0]
at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[camel-core-2.16.0.jar:2.16.0]
at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
[camel-core-2.16.0.jar:2.16.0]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[?:1.8.0_60]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
[?:1.8.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
[?:1.8.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
[?:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[?:1.8.0_60]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[?:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
Caused by: com.jcraft.jsch.SftpException: 
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1720)
~[jsch-0.1.53.jar:?]
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1526)
~[jsch-0.1.53.jar:?]
at
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:588)
~[camel-ftp-2.16.0.jar:2.16.0]
... 13 more
Caused by: java.io.IOException: Pipe closed
at java.io.PipedInputStream.read(PipedInputStream.java:307) 
~[?:1.8.0_60]
at
com.jcraft.jsch.Channel$MyPipedInputStream.updateReadSide(Channel.java:362)
~[jsch-0.1.53.jar:?]
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1543)
~[jsch-0.1.53.jar:?]
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1526)
~[jsch-0.1.53.jar:?]
at
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:588)
~[camel-ftp-2.16.0.jar:2.16.0]
... 13 more

What could be the issue here? I tried to play with the 'disconnect' and the
'stepwise' flag, but it does not resolve the issue. Thanks for your help.




--
View this message in context: 
http://camel.465427.n5.nabble.com/sFTP-listFiles-does-not-work-after-upgrade-from-2-15-x-to-2-16-0-tp5774379.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: sFTP 'listFiles' does not work after upgrade from 2.15.x to 2.16.0

[Claus Ibsen]

Maybe its jcraft version change. Try using the same version of jcraft as before.

On Wed, Nov 25, 2015 at 10:05 AM, nicoruti
 wrote:
> Dear camel-community
>
> I have the following route (simplified):
>
> RemoteFileEndpoint ftpEndpoint =
> endpoint("sftp:ftp.myhost.com/?username=user&password=x&delay=4320&disconnect=true",
> RemoteFileEndpoint.class);
> ftpEndpoint.setFilter(new MyDownloadFileFilter());
> from(ftpEndpoint)
>  .to("file:{{configured.dl.dir}}")
>  .log("Downloaded ${header.CamelFileName} over FTP")
>  .to("direct:further-processing")
> .end();
>
>
> This route worked as expected and I could download all files that are
> accepted by MyDownloadFileFilter.
> After upgrading from 2.15.x to the latest camel version 2.16.0, I faced the
> following exception:
>
>
> WARN ] 2015-11-25 09:41:12.988 [Camel (camel-1) thread #2 -
> sftp://ftp.myhost.com/] RemoteFilePollingConsumerPollStrategy - Trying to
> recover by disconnecting from remote server forcing a re-connect at next
> poll: sftp://u...@ftp.myhost.com:22
> [WARN ] 2015-11-25 09:41:12.993 [Camel (camel-1) thread #2 -
> sftp://ftp.myhost.com/] SftpConsumer - Consumer
> Consumer[sftp://ftp.myhost.com/?delay=4320&disconnect=true&password=xx&username=user]
> failed polling endpoint:
> Endpoint[sftp://ftp.myhost.com/?delay=4320&disconnect=true&password=xx&username=user].
> Will try again at next poll. Caused by:
> [org.apache.camel.component.file.GenericFileOperationFailedException -
> Cannot list directory: .]
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> list directory: .
> at
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:597)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> at
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:574)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> at
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:115)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> at
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:79)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:119)
> ~[camel-core-2.16.0.jar:2.16.0]
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
> [camel-core-2.16.0.jar:2.16.0]
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
> [camel-core-2.16.0.jar:2.16.0]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:1.8.0_60]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [?:1.8.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> [?:1.8.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> [?:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
> Caused by: com.jcraft.jsch.SftpException:
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1720)
> ~[jsch-0.1.53.jar:?]
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1526)
> ~[jsch-0.1.53.jar:?]
> at
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:588)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> ... 13 more
> Caused by: java.io.IOException: Pipe closed
> at java.io.PipedInputStream.read(PipedInputStream.java:307) 
> ~[?:1.8.0_60]
> at
> com.jcraft.jsch.Channel$MyPipedInputStream.updateReadSide(Channel.java:362)
> ~[jsch-0.1.53.jar:?]
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1543)
> ~[jsch-0.1.53.jar:?]
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1526)
> ~[jsch-0.1.53.jar:?]
> at
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:588)
> ~[camel-ftp-2.16.0.jar:2.16.0]
> ... 13 more
>
> What could be the issue here? I tried to play with the 'disconnect' and the
> 'stepwise' flag, but it does not resolve the issue. Thanks for your help.
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/sFTP-listFiles-does-not-work-after-upgrade-from-2-15-x-to-2-16-0-tp5774379.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: sFTP 'listFiles' does not work after upgrade from 2.15.x to 2.16.0

[nicoruti]

Thanks, Claus, for your quick response. 

Indeed, jcraft went up from 0.1.51 to 0.1.53. But switching back to the old
version leads to the same error.



--
View this message in context: 
http://camel.465427.n5.nabble.com/sFTP-listFiles-does-not-work-after-upgrade-from-2-15-x-to-2-16-0-tp5774379p5774382.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: sFTP 'listFiles' does not work after upgrade from 2.15.x to 2.16.0

[Claus Ibsen]

What is the latest working 2.15.x version you can use? And mind that
2.15.5 is on the way, so maybe give that a test too.
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-15-5-td5774324.html

Then we/you can do some source code compare, and commit history to
track down what changes may cause a problem for you.

On Wed, Nov 25, 2015 at 10:30 AM, nicoruti
 wrote:
> Thanks, Claus, for your quick response.
>
> Indeed, jcraft went up from 0.1.51 to 0.1.53. But switching back to the old
> version leads to the same error.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/sFTP-listFiles-does-not-work-after-upgrade-from-2-15-x-to-2-16-0-tp5774379p5774382.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

question how to asynchronous processing

[廣木康二]

I have a question about asynchronous processing.
I want to use same thread  for same data
 when I use multiple camel components and multiple threads
 because I want to prevent from overtaking.
So,how could I use multicast() or could I use some other methods?

For example,
  Data1(first dat to come),
  Data2(second data),
  Data3(third data),
  Data1 and Data3 are same data but are not same with Data2.
In this situation, I want to use same thread for Data1 and Data3
 bacause I want to avoid the situation which processing Data3 finishes
 faster than Data1.

-
hiiir...@gmail.com
-

Re: How to improve throughput by grouping messages in a Transaction (in JMS)

[prajath]

Hi ,
I tried to use BatchMessageListenerContainer  with camel still it is picking
up single message from queue per transaction, could you please let me know
what I am doing wrong here.
Here is my code snippet 

 Look like BatchMessageListenerContainer   not deployed in Maven central.

 I have copied source code  from spring-batch-infrastructure-tests module
And setup TransactionInterceptor and RepeatOperationsInterceptor as per
there documentation 














 

I was expecting 100 message per transaction .

BatchListenerContainerFactory---

public AbstractMessageListenerContainer createMessageListenerContainer(
JmsEndpoint arg0) {
BatchMessageListenerContainer batchMessageListenerContainer=new
BatchMessageListenerContainer();

batchMessageListenerContainer.setTransactionManager(transactionManager);

batchMessageListenerContainer.setConnectionFactory(connectionFactory);

batchMessageListenerContainer.setMessageListener(messageListener);

batchMessageListenerContainer.setDestinationName(destinationName);
batchMessageListenerContainer.setConcurrentConsumers(1);
batchMessageListenerContainer.setReceiveTimeout(3000);
batchMessageListenerContainer.setSessionTransacted(true);
Advice[] advices = new Advice[2];
advices[0]=transactionInterceptor;
advices[1]=repeatOperationsInterceptor;
batchMessageListenerContainer.setAdviceChain(advices);
return batchMessageListenerContainer;
}

--Camel root




regards,
pp




--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-improve-throughput-by-grouping-messages-in-a-Transaction-tp5773344p5774390.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Am I using headers right?

[Joakim Bjørnstad]

Hello,

If you need metadata or a value on multiple endpoints, or to be used
internally in your routes, it is better to put them in the
exchangeProperties. Then copy them out to headers, when needed. Since
headers are meant to be used at the protocol/component in/out, there
is no guarantee they persist or be unchanged when the message returns.
Also reduces unwanted metadata leaking out of your routes, for example
to JMS, HTTP/SOAP as you mentioned.



On Wed, Nov 25, 2015 at 12:52 AM, Matt Sicker  wrote:
> I filter out what headers to send when making REST calls through http4 for
> instance, so that's not an issue. When I make internal calls to networked
> services (e.g., Kafka, Hazelcast, or pretty much anything other than the
> message brokering components), I lose all my headers until the response
> message is handled (and only some components save those headers).
>
> On 24 November 2015 at 16:36, ychawla  wrote:
>
>> That sounds sensible to me.  The headers are for message and exchange
>> metadata.  Just be careful to not send them over the wire when you call an
>> external component.
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Am-I-using-headers-right-tp5774363p5774365.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Matt Sicker 



-- 
Kind regards
Joakim Bjørnstad

Prevent FailedToCreateRouteException to cause application stop

[Brossard]

Hi,

I am currently using Camel 2.16 in a web application, starting it with a
*ContextLoaderListener* in my *web.xml*.
Is there a way to prevent my webapp being stopped in case of exception like
*FailedToCreateRouteException* ?
In other words, i would like to isolate one (or more) route, and say to
Camel "it doesn't matters if this route doesn't starts up, i want to start
my application anyway".

Thanks for your help.

Regards,
Brossard



--
View this message in context: 
http://camel.465427.n5.nabble.com/Prevent-FailedToCreateRouteException-to-cause-application-stop-tp5774408.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Prevent FailedToCreateRouteException to cause application stop

[Claus Ibsen]

Mark all routes to not auto startup, and then start them yourself one
by one from some Java code etc.

On Wed, Nov 25, 2015 at 3:23 PM, Brossard  wrote:
> Hi,
>
> I am currently using Camel 2.16 in a web application, starting it with a
> *ContextLoaderListener* in my *web.xml*.
> Is there a way to prevent my webapp being stopped in case of exception like
> *FailedToCreateRouteException* ?
> In other words, i would like to isolate one (or more) route, and say to
> Camel "it doesn't matters if this route doesn't starts up, i want to start
> my application anyway".
>
> Thanks for your help.
>
> Regards,
> Brossard
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Prevent-FailedToCreateRouteException-to-cause-application-stop-tp5774408.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Prevent FailedToCreateRouteException to cause application stop

[Brossard]

Doesn't Camel try to resolve endpoint even if route isn't autostarted ?
If not, how can i start my route(s) only when my application's context is
started?

Thx
Arnaud



--
View this message in context: 
http://camel.465427.n5.nabble.com/Prevent-FailedToCreateRouteException-to-cause-application-stop-tp5774408p5774410.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Am I using headers right?

[Matt Sicker]

Properties get lost even more often than headers, though. They're only
copied when the entire Exchange is used instead of the message body or the
Message object. I use them for temporary metadata between Processors,
beans, etc.

On 25 November 2015 at 06:54, Joakim Bjørnstad  wrote:

> Hello,
>
> If you need metadata or a value on multiple endpoints, or to be used
> internally in your routes, it is better to put them in the
> exchangeProperties. Then copy them out to headers, when needed. Since
> headers are meant to be used at the protocol/component in/out, there
> is no guarantee they persist or be unchanged when the message returns.
> Also reduces unwanted metadata leaking out of your routes, for example
> to JMS, HTTP/SOAP as you mentioned.
>
>
>
> On Wed, Nov 25, 2015 at 12:52 AM, Matt Sicker  wrote:
> > I filter out what headers to send when making REST calls through http4
> for
> > instance, so that's not an issue. When I make internal calls to networked
> > services (e.g., Kafka, Hazelcast, or pretty much anything other than the
> > message brokering components), I lose all my headers until the response
> > message is handled (and only some components save those headers).
> >
> > On 24 November 2015 at 16:36, ychawla 
> wrote:
> >
> >> That sounds sensible to me.  The headers are for message and exchange
> >> metadata.  Just be careful to not send them over the wire when you call
> an
> >> external component.
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/Am-I-using-headers-right-tp5774363p5774365.html
> >> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>
> >
> >
> >
> > --
> > Matt Sicker 
>
>
>
> --
> Kind regards
> Joakim Bjørnstad
>



-- 
Matt Sicker 

How do I pass on my query parameters?

[tomaswahlgren]

I have a consumer :
/jetty:http://localhost:6080/say/hello1?matchOnUriPrefix=true&enableMultipartFilter=false/

And a producer:
/http4://localhost:6080/mdp/api/ifmdp/map?bridgeEndpoint=true&throwExceptionOnFailure=false&disableStreamCache=true/

When my application calls the URL may look like:
/http://127.0.0.1:7076/mdr/api/ifmdr?hepp=22&number=34/

But my parameters hepp and number are not sent through, and are not present
if I search for them in the loadbalancer either (/String n =
exchange.getIn().getHeader("number", String.class)/; will be null).

What am I missing?



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-do-I-pass-on-my-query-parameters-tp5774413.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[ANNOUNCE] CFP open for ApacheCon North America 2016

[Rich Bowen]

Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?

We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
for big data talks and
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
for all other topics.

ApacheCon North America will be held in Vancouver, Canada, May 9-13th
2016. ApacheCon has been running every year since 2000, and is the place
to build your project communities.

While we will consider individual talks we prefer to see related
sessions that are likely to draw users and community members. When
submitting your talk work with your project community and with related
communities to come up with a full program that will walk attendees
through the basics and on into mastery of your project in example use
cases. Content that introduces what's new in your latest release is also
of particular interest, especially when it builds upon existing well
know application models. The goal should be to showcase your project in
ways that will attract participants and encourage engagement in your
community, Please remember to involve your whole project community (user
and dev lists) when building content. This is your chance to create a
project specific event within the broader ApacheCon conference.

Content at ApacheCon North America will be cross-promoted as
mini-conferences, such as ApacheCon Big Data, and ApacheCon Mobile, so
be sure to indicate which larger category your proposed sessions fit into.

Finally, please plan to attend ApacheCon, even if you're not proposing a
talk. The biggest value of the event is community building, and we count
on you to make it a place where your project community is likely to
congregate, not just for the technical content in sessions, but for
hackathons, project summits, and good old fashioned face-to-face networking.

-- 
rbo...@apache.org
http://apache.org/

Re: Am I using headers right?

[Joakim Bjørnstad]

Yes, you typically use them for route internal metadata.

But they are not lost when they enter and return from an endpoint,
unless you or the component creates a fresh new exchange.

Please also see this SO:
http://stackoverflow.com/questions/10330998/passing-values-between-processors-in-apache-camel


On Wed, Nov 25, 2015 at 4:00 PM, Matt Sicker  wrote:
> Properties get lost even more often than headers, though. They're only
> copied when the entire Exchange is used instead of the message body or the
> Message object. I use them for temporary metadata between Processors,
> beans, etc.
>
> On 25 November 2015 at 06:54, Joakim Bjørnstad  wrote:
>
>> Hello,
>>
>> If you need metadata or a value on multiple endpoints, or to be used
>> internally in your routes, it is better to put them in the
>> exchangeProperties. Then copy them out to headers, when needed. Since
>> headers are meant to be used at the protocol/component in/out, there
>> is no guarantee they persist or be unchanged when the message returns.
>> Also reduces unwanted metadata leaking out of your routes, for example
>> to JMS, HTTP/SOAP as you mentioned.
>>
>>
>>
>> On Wed, Nov 25, 2015 at 12:52 AM, Matt Sicker  wrote:
>> > I filter out what headers to send when making REST calls through http4
>> for
>> > instance, so that's not an issue. When I make internal calls to networked
>> > services (e.g., Kafka, Hazelcast, or pretty much anything other than the
>> > message brokering components), I lose all my headers until the response
>> > message is handled (and only some components save those headers).
>> >
>> > On 24 November 2015 at 16:36, ychawla 
>> wrote:
>> >
>> >> That sounds sensible to me.  The headers are for message and exchange
>> >> metadata.  Just be careful to not send them over the wire when you call
>> an
>> >> external component.
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://camel.465427.n5.nabble.com/Am-I-using-headers-right-tp5774363p5774365.html
>> >> Sent from the Camel - Users mailing list archive at Nabble.com.
>> >>
>> >
>> >
>> >
>> > --
>> > Matt Sicker 
>>
>>
>>
>> --
>> Kind regards
>> Joakim Bjørnstad
>>
>
>
>
> --
> Matt Sicker 



-- 
Kind regards
Joakim Bjørnstad

Routing Slip not executing full routes

[biphasic]

Hello,
I'm currently trying to get a Routing Slip EIP to work. I can successfully
route the inflight message to various endpoints, but the routes are never
fully executed. Meaning the following: when the routing slip includes the
URIs "direct:updateOrCreatePatient, direct:admit", my expectedMessageCounts
in the tests for these routes are fulfilled. However, whatever is part of
either of these routes, is not executed (until now only a transform to
itself, but now I want to implement processors etc). Whole project can be
found on Github:
https://github.com/NeovaHealth/ARNIE/blob/master/src/main/groovy/uk/co/neovahealth/ARNIE/ADTRouting.groovy

Thankful for any sort of input and/or feedback to the code!
Regards,
Greg



--
View this message in context: 
http://camel.465427.n5.nabble.com/Routing-Slip-not-executing-full-routes-tp5774423.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

[Mullally, Mark]

Immense gratitude for this post as I am now not obligated to work
Thanksgiving Day to resolve the issue ... years later I am witnessing
exactly the same behavior as you described and the remedy of removing the
update-strategy="reload" attribute also resolved the issue.

The only insight I can contribute at the moment is that the undesirable
behavior is only exhibited when more than one bundle accesses a particular
property persistence id; if a property persistence id is unique per bundle,
all is copacetic.

This seemingly innocent defect causes catastrophic failure without even so
much as a single log statement as to why every Camel Context in every
bundle is being bounced over and over again.


   -

   Version 3.0.4
   
   of Apache Karaf 
   -

   Version 5.11.1 
   of ActiveMQ 
   -

   Version 2.15.2  of Camel
   
   -

   Version 3.0.4  of CXF
   


-- 
Mark P. Mullally
Cherokee Nation Technologies, LLC (CNT)
Contractor to DOI, U.S. Fish & Wildlife Service
ECOS applications for USFWS
2150 Centre Ave., Bldg C
Fort Collins, CO 80526

Exception on camel-example-spring-ws

[James Wong1]

I'm trying to run the Spring Web Services Example (camel-example-spring-ws)
with the SOAP UI project examples/camel-example-spring-ws/client, I have
noticed that there are some exceptions on the console.
Although I can see the SOAP response. Please help.

2015-11-26 10:08:07,195 [tp1573356572-29] WARN  EventHelper   
-
 Error notifying event ID-HP-PC-64715-1448502703025-0-5 exchange created:
Exchan
ge[ID-HP-PC-64715-1448502703025-0-5][SpringWebserviceMessage[SaajSoapMessage
{ht
tp://camel.apache.org/example/increment}incrementRequest]]. This exception
will
be ignored.
java.lang.NullPointerException
at
org.apache.camel.impl.DefaultRuntimeEndpointRegistry.notify(DefaultRu
ntimeEndpointRegistry.java:245)
at
org.apache.camel.util.EventHelper.doNotifyEvent(EventHelper.java:805)

at
org.apache.camel.util.EventHelper.notifyExchangeCreated(EventHelper.j
ava:411)
at
org.apache.camel.impl.DefaultUnitOfWork.(DefaultUnitOfWork.java
:123)
at
org.apache.camel.impl.DefaultUnitOfWork.(DefaultUnitOfWork.java
:72)
at
org.apache.camel.impl.DefaultUnitOfWorkFactory.createUnitOfWork(Defau
ltUnitOfWorkFactory.java:34)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
Advice.createUnitOfWork(CamelInternalProcessor.java:663)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
Advice.before(CamelInternalProcessor.java:631)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
Advice.before(CamelInternalProcessor.java:608)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelIntern
alProcessor.java:138)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelp
er.java:109)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsy
ncProcessor.java:87)
at
org.apache.camel.component.spring.ws.SpringWebserviceConsumer.invoke(
SpringWebserviceConsumer.java:61)
at
org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter
.invoke(MessageEndpointAdapter.java:43)
at
org.springframework.ws.server.MessageDispatcher.dispatch(MessageDispa
tcher.java:236)
at
org.springframework.ws.server.MessageDispatcher.receive(MessageDispat
cher.java:176)
at
org.springframework.ws.transport.support.WebServiceMessageReceiverObj
ectSupport.handleConnection(WebServiceMessageReceiverObjectSupport.java:89)
at
org.springframework.ws.transport.http.WebServiceMessageReceiverHandle
rAdapter.handle(WebServiceMessageReceiverHandlerAdapter.java:61)
at
org.springframework.ws.transport.http.MessageDispatcherServlet.doServ
ice(MessageDispatcherServlet.java:293)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(Frame
workServlet.java:966)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServ
let.java:868)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkSer
vlet.java:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684
)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
:503)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav
a:557)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
er.java:231)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
er.java:1086)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
429)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle
r.java:193)



--
View this message in context: 
http://camel.465427.n5.nabble.com/Exception-on-camel-example-spring-ws-tp5774427.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Exception on camel-example-spring-ws

[Claus Ibsen]

Upgrade Camel to 2.16.1 as it was a bug in camel and camel-spring-ws
in that version.

On Thu, Nov 26, 2015 at 3:15 AM, James Wong1  wrote:
> I'm trying to run the Spring Web Services Example (camel-example-spring-ws)
> with the SOAP UI project examples/camel-example-spring-ws/client, I have
> noticed that there are some exceptions on the console.
> Although I can see the SOAP response. Please help.
>
> 2015-11-26 10:08:07,195 [tp1573356572-29] WARN  EventHelper
> -
>  Error notifying event ID-HP-PC-64715-1448502703025-0-5 exchange created:
> Exchan
> ge[ID-HP-PC-64715-1448502703025-0-5][SpringWebserviceMessage[SaajSoapMessage
> {ht
> tp://camel.apache.org/example/increment}incrementRequest]]. This exception
> will
> be ignored.
> java.lang.NullPointerException
> at
> org.apache.camel.impl.DefaultRuntimeEndpointRegistry.notify(DefaultRu
> ntimeEndpointRegistry.java:245)
> at
> org.apache.camel.util.EventHelper.doNotifyEvent(EventHelper.java:805)
>
> at
> org.apache.camel.util.EventHelper.notifyExchangeCreated(EventHelper.j
> ava:411)
> at
> org.apache.camel.impl.DefaultUnitOfWork.(DefaultUnitOfWork.java
> :123)
> at
> org.apache.camel.impl.DefaultUnitOfWork.(DefaultUnitOfWork.java
> :72)
> at
> org.apache.camel.impl.DefaultUnitOfWorkFactory.createUnitOfWork(Defau
> ltUnitOfWorkFactory.java:34)
> at
> org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
> Advice.createUnitOfWork(CamelInternalProcessor.java:663)
> at
> org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
> Advice.before(CamelInternalProcessor.java:631)
> at
> org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessor
> Advice.before(CamelInternalProcessor.java:608)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelIntern
> alProcessor.java:138)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelp
> er.java:109)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsy
> ncProcessor.java:87)
> at
> org.apache.camel.component.spring.ws.SpringWebserviceConsumer.invoke(
> SpringWebserviceConsumer.java:61)
> at
> org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter
> .invoke(MessageEndpointAdapter.java:43)
> at
> org.springframework.ws.server.MessageDispatcher.dispatch(MessageDispa
> tcher.java:236)
> at
> org.springframework.ws.server.MessageDispatcher.receive(MessageDispat
> cher.java:176)
> at
> org.springframework.ws.transport.support.WebServiceMessageReceiverObj
> ectSupport.handleConnection(WebServiceMessageReceiverObjectSupport.java:89)
> at
> org.springframework.ws.transport.http.WebServiceMessageReceiverHandle
> rAdapter.handle(WebServiceMessageReceiverHandlerAdapter.java:61)
> at
> org.springframework.ws.transport.http.MessageDispatcherServlet.doServ
> ice(MessageDispatcherServlet.java:293)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(Frame
> workServlet.java:966)
> at
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServ
> let.java:868)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkSer
> vlet.java:842)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684
> )
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
> :503)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
> ava:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav
> a:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
> er.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
> er.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
> 429)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle
> r.java:193)
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Exception-on-camel-example-spring-ws-tp5774427.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2