[jira] [Updated] (CAMEL-9675) Improve loop EIP to act like a while loop

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9675:
---
Fix Version/s: (was: Future)
   2.17.0

> Improve loop EIP to act like a while loop
> -
>
> Key: CAMEL-9675
> URL: https://issues.apache.org/jira/browse/CAMEL-9675
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
>
> So instead of a hardcoded number, you can specify a predicate that allows to 
> loop until its false.
> See for example
> http://camel.465427.n5.nabble.com/Polling-http-endpoints-tp5778533.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9675) Improve loop EIP to act like a while loop

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-9675:
--

Assignee: Claus Ibsen

> Improve loop EIP to act like a while loop
> -
>
> Key: CAMEL-9675
> URL: https://issues.apache.org/jira/browse/CAMEL-9675
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: Future
>
>
> So instead of a hardcoded number, you can specify a predicate that allows to 
> loop until its false.
> See for example
> http://camel.465427.n5.nabble.com/Polling-http-endpoints-tp5778533.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CAMEL-9606) SJMS Consumer-Producer in transaciton

[JIRA]

[ 
https://issues.apache.org/jira/browse/CAMEL-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190583#comment-15190583
 ] 

Zdeněk Obst edited comment on CAMEL-9606 at 3/11/16 7:41 AM:
-

Can anyone please come with any statement please?
Whether it is a bug and if any fix can be expected (sooner or later)?


was (Author: d1x):
Can anyone please come with any statement please?
Whether is a bug and if any fix can be expected (sooner or later)?

> SJMS Consumer-Producer in transaciton
> -
>
> Key: CAMEL-9606
> URL: https://issues.apache.org/jira/browse/CAMEL-9606
> Project: Camel
>  Issue Type: Bug
>  Components: camel-sjms
>Affects Versions: 2.15.4, 2.16.2
>Reporter: Zdeněk Obst
>
> I'm not 100% sure this is a bug but it feels that way from conversation I had 
> via mailing lists.
> I'm trying to ensure transactional processing between SJMS consumer and 
> producer (e.g. using same JMS session). 
> In other words this simple case:
> 1. prepare higher amount of JMS messages in broker (e.g. ActiveMQ with 1000 
> messages) 
> 2. use Camel route from input queue to output queue using trasacted=true 
> 3. start context (starts consuming messages) and in any time kill java 
> process 
> When I kill process, I would expect that sum of messages in input and output 
> queue will be 1000 - so the transaction works. But what happens is that I 
> always end up with 1001+ messages. Maybe it is misconfiguration of routes or 
> misunderstanding how SJMS can work.
> Here is the sample code I used for reproduction (using ActiveMQ):
> {code:java}
> public class SjmsTransaction {
> public static void main(String[] args) throws Exception {
> RouteBuilder rb = new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> onException(Exception.class)
> .process(systemOut("Exception!!"));
> from("sjms:queue:test-in?transacted=true=5")
> .process(systemOut("Processing"))
> .to("sjms:queue:test-out?transacted=true")
> .process(systemOut("Processed"));
> }
> };
> CamelContext context = new DefaultCamelContext();
> addJmsComponent(context);
> context.addRoutes(rb);
> System.out.println("=> Starting context");
> context.start();
> // Now the context will run and consume messages, when I kill 
> application by force in any time
> // I expect this to be true: <#messagesInInputAtBeginning> == 
> <#messagesInInputNow> + <#messagesInOutputNow>
> // What happens is that there is always < (e.g. I submitted 1000 
> messages, out has 500, in has 501)
> }
> private static void addJmsComponent(CamelContext context) {
> ConnectionFactory factory = new 
> ActiveMQConnectionFactory("tcp://localhost:61616");
> ConnectionFactoryResource connResource = new 
> ConnectionFactoryResource(5, factory);
> SjmsComponent comp = new SjmsComponent();
> comp.setConnectionResource(connResource);
> context.addComponent("sjms", comp);
> }
> private static Processor systemOut(final String message) {
> return new Processor() {
> @Override
> public void process(Exchange exchange) throws Exception {
> System.out.println(exchange.getExchangeId() + ": " + message);
> }
> };
> }
> }
> {code}
> Note that I tried to use it with various combinations of acknowledgeMode and 
> In/InOut exchange pattern - but without luck.
> I'm not that much oriented in Camel source code but I found that JMS session 
> is held within the exchange so probably when producer finds in an exchange 
> existing JMS session and is configured to be transacted, then maybe it can 
> participate this session? Or maybe there are other hooks (like 
> Synchronization objects) in some registry that take care of this issue?
> Here is the link to the previous mailing list conversation: 
> http://camel.465427.n5.nabble.com/SJMS-transaction-td5777522.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9606) SJMS Consumer-Producer in transaciton

[JIRA]

[ 
https://issues.apache.org/jira/browse/CAMEL-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190583#comment-15190583
 ] 

Zdeněk Obst commented on CAMEL-9606:


Can anyone please come with any statement please?
Whether is a bug and if any fix can be expected (sooner or later)?

> SJMS Consumer-Producer in transaciton
> -
>
> Key: CAMEL-9606
> URL: https://issues.apache.org/jira/browse/CAMEL-9606
> Project: Camel
>  Issue Type: Bug
>  Components: camel-sjms
>Affects Versions: 2.15.4, 2.16.2
>Reporter: Zdeněk Obst
>
> I'm not 100% sure this is a bug but it feels that way from conversation I had 
> via mailing lists.
> I'm trying to ensure transactional processing between SJMS consumer and 
> producer (e.g. using same JMS session). 
> In other words this simple case:
> 1. prepare higher amount of JMS messages in broker (e.g. ActiveMQ with 1000 
> messages) 
> 2. use Camel route from input queue to output queue using trasacted=true 
> 3. start context (starts consuming messages) and in any time kill java 
> process 
> When I kill process, I would expect that sum of messages in input and output 
> queue will be 1000 - so the transaction works. But what happens is that I 
> always end up with 1001+ messages. Maybe it is misconfiguration of routes or 
> misunderstanding how SJMS can work.
> Here is the sample code I used for reproduction (using ActiveMQ):
> {code:java}
> public class SjmsTransaction {
> public static void main(String[] args) throws Exception {
> RouteBuilder rb = new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> onException(Exception.class)
> .process(systemOut("Exception!!"));
> from("sjms:queue:test-in?transacted=true=5")
> .process(systemOut("Processing"))
> .to("sjms:queue:test-out?transacted=true")
> .process(systemOut("Processed"));
> }
> };
> CamelContext context = new DefaultCamelContext();
> addJmsComponent(context);
> context.addRoutes(rb);
> System.out.println("=> Starting context");
> context.start();
> // Now the context will run and consume messages, when I kill 
> application by force in any time
> // I expect this to be true: <#messagesInInputAtBeginning> == 
> <#messagesInInputNow> + <#messagesInOutputNow>
> // What happens is that there is always < (e.g. I submitted 1000 
> messages, out has 500, in has 501)
> }
> private static void addJmsComponent(CamelContext context) {
> ConnectionFactory factory = new 
> ActiveMQConnectionFactory("tcp://localhost:61616");
> ConnectionFactoryResource connResource = new 
> ConnectionFactoryResource(5, factory);
> SjmsComponent comp = new SjmsComponent();
> comp.setConnectionResource(connResource);
> context.addComponent("sjms", comp);
> }
> private static Processor systemOut(final String message) {
> return new Processor() {
> @Override
> public void process(Exchange exchange) throws Exception {
> System.out.println(exchange.getExchangeId() + ": " + message);
> }
> };
> }
> }
> {code}
> Note that I tried to use it with various combinations of acknowledgeMode and 
> In/InOut exchange pattern - but without luck.
> I'm not that much oriented in Camel source code but I found that JMS session 
> is held within the exchange so probably when producer finds in an exchange 
> existing JMS session and is configured to be transacted, then maybe it can 
> participate this session? Or maybe there are other hooks (like 
> Synchronization objects) in some registry that take care of this issue?
> Here is the link to the previous mailing list conversation: 
> http://camel.465427.n5.nabble.com/SJMS-transaction-td5777522.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9682) camel-rxjava module should extend Bean Binding to support methods returning Observable

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9682:
---
Fix Version/s: 2.18.0

> camel-rxjava module should extend Bean Binding to support methods returning 
> Observable
> -
>
> Key: CAMEL-9682
> URL: https://issues.apache.org/jira/browse/CAMEL-9682
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-rx
>Reporter: james strachan
> Fix For: 2.18.0
>
>
> when making asynchronous InOut requests it'd be nice if methods could return 
> Observable so that we could use the RxJava async programming model to 
> process async requests & responses.
> e.g. kinda like how folks can use Retrofit for HTTP: 
> http://joluet.github.io/blog/2014/07/07/rxjava-retrofit/
> {code}
> public interface MyThing {
> @GET("/session.json")
> Observable login();
> @GET("/user.json")
> Observable getUserState();
> }
> {code}
> to then let you use the normal composition / join / flatMap stuff in RxJava 
> to compose multiple requests across different microservice invocations 
> together with timeouts etc e.g. to compose the latest from 2 calls:
> {code}
> Observable.combineLatest(api.fetchUserProfile(), api.getUserState(),
> (user, userStatus) -> new Pair<>(user, userStatus));
> {code}
> Where we'd replace the @GET annotation with a bean binding annotation and a 
> URI parameter to switch to using ActiveMQ or Twitter or whatever



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-1077) tcp client mode / server mode determined by "to" or "from" elements limits usability.

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190564#comment-15190564
 ] 

Claus Ibsen commented on CAMEL-1077:


There is a clientMode option

> tcp client mode / server mode determined by "to" or "from" elements limits 
> usability.
> -
>
> Key: CAMEL-1077
> URL: https://issues.apache.org/jira/browse/CAMEL-1077
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-mina
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Jeff Vienneau
>Assignee: Willem Jiang
> Fix For: 2.15.0
>
>
> Internally, 
> MinaProducer is coded to create a Mina connector (client mode socket).
> MinaConsumer is coded to create a Mina acceptor (server mode socket).
> Additionally, it appears a producer (client mode socket) is created for a 
> "to" route mapping and a consumer (server mode socket) is created for a 
> "from" route mapping.
> This means an endpoint cannot be created in which the session is initiated by 
> a client and messages are routed "to" the client. 
> The opposite is also true, an endpoint with a "from" route mapping cannot 
> establish a connection to a tcp server.
> This is a major limitation, as we do not often have control over the systems 
> with which we are interfacing.
> Perhaps, the mina::tcp URI could have a parameter the sets the socket mode: 
> tcp.mode=server or tcp.mode=client.
> Hope this make sense, thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9697) Test component - Allow to receive in any order, or split using expression

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-9697.

Resolution: Fixed

Added a separator for now. An expression is maybe a bit over the top.

> Test component - Allow to receive in any order, or split using expression
> -
>
> Key: CAMEL-9697
> URL: https://issues.apache.org/jira/browse/CAMEL-9697
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Camel-Test-Endpoint-Error-tp5778858.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-1077) tcp client mode / server mode determined by "to" or "from" elements limits usability.

[Trey Sargent (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189705#comment-15189705
 ] 

Trey Sargent commented on CAMEL-1077:
-

Has this been implemented yet on camel-netty component?

> tcp client mode / server mode determined by "to" or "from" elements limits 
> usability.
> -
>
> Key: CAMEL-1077
> URL: https://issues.apache.org/jira/browse/CAMEL-1077
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-mina
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Jeff Vienneau
>Assignee: Willem Jiang
> Fix For: 2.15.0
>
>
> Internally, 
> MinaProducer is coded to create a Mina connector (client mode socket).
> MinaConsumer is coded to create a Mina acceptor (server mode socket).
> Additionally, it appears a producer (client mode socket) is created for a 
> "to" route mapping and a consumer (server mode socket) is created for a 
> "from" route mapping.
> This means an endpoint cannot be created in which the session is initiated by 
> a client and messages are routed "to" the client. 
> The opposite is also true, an endpoint with a "from" route mapping cannot 
> establish a connection to a tcp server.
> This is a major limitation, as we do not often have control over the systems 
> with which we are interfacing.
> Perhaps, the mina::tcp URI could have a parameter the sets the socket mode: 
> tcp.mode=server or tcp.mode=client.
> Hope this make sense, thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9699) Change the default for DataSets used as sources to zero

[Quinn Stevenson (JIRA)]

Quinn Stevenson created CAMEL-9699:
--

 Summary: Change the default for DataSets used as sources to zero
 Key: CAMEL-9699
 URL: https://issues.apache.org/jira/browse/CAMEL-9699
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Reporter: Quinn Stevenson
Priority: Minor


Change the current behavior of the DataSet component such that the expected 
message count defaults to zero for DataSets used as a source (i.e. 
DataSetConsumers).

The reasoning behind this is as follows. 

I use the DataSet component for simple load testing.  When I use a DataSet as a 
source (i.e. from(“dataset://my-dataset”) ), the assertMockEndpointsSatisfied() 
always fails because the expectedMessageSize is set to the size of the DataSet. 
 I either have to explicitly set the expected message count on the endpoint to 
zero ( getMockEndpoint( “dataset://my-dataset”).expectedMessageCount( 0 ), or I 
have to assert all of the other mock endpoints individually (i.e not use 
assertMockEndpointsSatisfied() ).

I rarely use the same dataset as both a source (i.e. from(“dataset://…”) ) and 
a target (i.e. to( “dataset://…”) ), so this behavior doesn’t make much sense 
to me.  Additionally, I can’t use the same DataSet as the source and target 
when the source message count would be different than the target message count 
- which would be the case for a route that does some simple filtering, and all 
I want to assert is the correct number of messages came through.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Jostein Gogstad (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189572#comment-15189572
 ] 

Jostein Gogstad commented on CAMEL-9694:


The use of {{localWorkDir}} in this scenario is really just to download large 
files up front, and keep streams in memory. The need is to have reusable 
streams in memory. The actual directory the files reside in isn't important. 

> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   ... 32 more
> {code}
> Looks like the stream caching isn't invoked at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Jostein Gogstad (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189563#comment-15189563
 ] 

Jostein Gogstad commented on CAMEL-9694:


That is indeed the point of the wiretap. The Thread.sleep in the test 
highlights this behaviour. I argue that when stream caching is in use, the file 
should be streamed from the streamCacheSpoolDirectory and not localWorkDir. 

The stream cache functionality supports wiretaps, the file in the spool 
directory is not deleted until all wiretaps are finished, therefore a route 
such as the one in the test is possible as long as the body is a stream cache.

The real world use case is this (I'm on mobile, so excuse the formatting):

{code:java}
from("ftp://...?delete=true;)
.bean(saveToDb) // consumes the stream
.wireTap("direct:pushToClients") // deletes the file on ftp and continue with 
pushing the stream to multiple clients on different transports
{code}

As long as one does the double {{.convertTo}} calls in my first comment, this 
works fine. If I where to do a {{.to("seda:..")}} instead of the wiretap, I 
wouldn't have the file deleted before the seda thread completes. 


> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> 

[jira] [Commented] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Vladimir Dzalbo (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189562#comment-15189562
 ] 

Vladimir Dzalbo commented on CAMEL-9698:


Yup, that's an easy fix indeed :)

But all other components seem to have that dependency. I'll make the PR.

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9698:
---
Estimated Complexity: Novice  (was: Unknown)

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189536#comment-15189536
 ] 

Claus Ibsen commented on CAMEL-9698:


A PR to fix this is welcome
http://camel.apache.org/contributing

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9698:
---
Priority: Minor  (was: Major)

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9698:
---
Fix Version/s: 2.17.0
   2.16.3

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189535#comment-15189535
 ] 

Claus Ibsen commented on CAMEL-9698:


Just install camel first which you really should

> camel-servlet karaf feature misses dependency on camel-core
> ---
>
> Key: CAMEL-9698
> URL: https://issues.apache.org/jira/browse/CAMEL-9698
> Project: Camel
>  Issue Type: Bug
>  Components: camel-servlet, karaf
>Affects Versions: 2.16.1
>Reporter: Vladimir Dzalbo
>Priority: Minor
>
> Installing camel-servlet fails, as it looks like the dependency on camel-core 
> has been removed from the features.xml
> {noformat}
> org.osgi.service.resolver.ResolutionException: Unable to resolve root: 
> missing requirement [root] osgi.identity; osgi.identity=camel-servlet; 
> type=karaf.feature; version="[2.16.1,2.16.1]"; 
> filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
>  [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
> [camel-servlet/2.16.1] osgi.identity; 
> osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
> version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to 
> resolve org.apache.camel.camel-servlet/2.16.1: missing requirement 
> [org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
> filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
>   at 
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
>   at 
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {noformat}
> Indeed this is definition from features.xml (current SNAPSHOT version)
> {code:xml}
>  start-level='50'>
>  camel-servlet need to access the http OSGi services 
> http
> mvn:org.apache.camel/camel-http-common/${project.version}
> mvn:org.apache.camel/camel-servlet/${project.version}
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler

[Martin Lichtin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Lichtin updated CAMEL-9695:
--
Environment: Karaf 3.0.3

> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.15.5
> Environment: Karaf 3.0.3
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint; 
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
>   id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>   
>   
>   
>   
>   etc.etc.
>   
> 
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error 
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at 
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at 
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at 
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at 
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at 
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at 
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at 
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at 
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at 
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at 
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9697) Test component - Allow to receive in any order, or split using expression

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9697:
---
Fix Version/s: (was: 2.16.3)

> Test component - Allow to receive in any order, or split using expression
> -
>
> Key: CAMEL-9697
> URL: https://issues.apache.org/jira/browse/CAMEL-9697
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.17.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Camel-Test-Endpoint-Error-tp5778858.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9698) camel-servlet karaf feature misses dependency on camel-core

[Vladimir Dzalbo (JIRA)]

Vladimir Dzalbo created CAMEL-9698:
--

 Summary: camel-servlet karaf feature misses dependency on 
camel-core
 Key: CAMEL-9698
 URL: https://issues.apache.org/jira/browse/CAMEL-9698
 Project: Camel
  Issue Type: Bug
  Components: camel-servlet, karaf
Affects Versions: 2.16.1
Reporter: Vladimir Dzalbo


Installing camel-servlet fails, as it looks like the dependency on camel-core 
has been removed from the features.xml

{noformat}
org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing 
requirement [root] osgi.identity; osgi.identity=camel-servlet; 
type=karaf.feature; version="[2.16.1,2.16.1]"; 
filter:="(&(osgi.identity=camel-servlet)(type=karaf.feature)(version>=2.16.1)(version<=2.16.1))"
 [caused by: Unable to resolve camel-servlet/2.16.1: missing requirement 
[camel-servlet/2.16.1] osgi.identity; 
osgi.identity=org.apache.camel.camel-servlet; type=osgi.bundle; 
version="[2.16.1,2.16.1]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.camel.camel-servlet/2.16.1: missing requirement 
[org.apache.camel.camel-servlet/2.16.1] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.apache.camel)(version>=2.16.0)(!(version>=2.17.0)))"]]
at 
org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[7:org.apache.karaf.features.core:4.0.4]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[7:org.apache.karaf.features.core:4.0.4]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1089)[7:org.apache.karaf.features.core:4.0.4]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:985)[7:org.apache.karaf.features.core:4.0.4]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
{noformat}


Indeed this is definition from features.xml (current SNAPSHOT version)

{code:xml}

 camel-servlet need to access the http OSGi services 
http
mvn:org.apache.camel/camel-http-common/${project.version}
mvn:org.apache.camel/camel-servlet/${project.version}
  
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9697) Test component - Allow to receive in any order, or split using expression

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9697:
--

 Summary: Test component - Allow to receive in any order, or split 
using expression
 Key: CAMEL-9697
 URL: https://issues.apache.org/jira/browse/CAMEL-9697
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Affects Versions: 2.16.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.16.3, 2.17.0


See nabble
http://camel.465427.n5.nabble.com/Camel-Test-Endpoint-Error-tp5778858.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9695) During shutdown, Camel cannot unregister error handler

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189491#comment-15189491
 ] 

Claus Ibsen commented on CAMEL-9695:


What version of Karaf do you use?

Its osgi blueprint that is an arse and shutdown beans in the wrong order.

> During shutdown, Camel cannot unregister error handler
> --
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.15.5
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint; 
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
>   id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>   
>   
>   
>   
>   etc.etc.
>   
> 
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error 
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at 
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at 
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at 
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at 
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at 
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at 
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at 
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at 
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at 
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at 
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9695) OSGi - During shutdown, Camel cannot unregister error handler

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9695:
---
Summary: OSGi - During shutdown, Camel cannot unregister error handler  
(was: During shutdown, Camel cannot unregister error handler)

> OSGi - During shutdown, Camel cannot unregister error handler
> -
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.15.5
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint; 
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
>   id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>   
>   
>   
>   
>   etc.etc.
>   
> 
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error 
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at 
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at 
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at 
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at 
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at 
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at 
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at 
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at 
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at 
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at 
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9695) During shutdown, Camel cannot unregister error handler

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9695:
---
Component/s: karaf

> During shutdown, Camel cannot unregister error handler
> --
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.15.5
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint; 
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
>   id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>   
>   
>   
>   
>   etc.etc.
>   
> 
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error 
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at 
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at 
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at 
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at 
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at 
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at 
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at 
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at 
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at 
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at 
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9695) During shutdown, Camel cannot unregister error handler

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9695:
---
Priority: Minor  (was: Major)

> During shutdown, Camel cannot unregister error handler
> --
>
> Key: CAMEL-9695
> URL: https://issues.apache.org/jira/browse/CAMEL-9695
> Project: Camel
>  Issue Type: Bug
>  Components: karaf
>Affects Versions: 2.15.5
>Reporter: Martin Lichtin
>Priority: Minor
>
> According to http://camel.apache.org/redeliverypolicy.html
> my camel context is like
> {code:xml}
> http://camel.apache.org/schema/blueprint; 
> xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
> http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
>   id="myIdxt" messageHistory="false">
>redeliveryPolicyRef="myRedeliveryPolicy" />
>   
>   
>   
>   
>   etc.etc.
>   
> 
> {code}
> During shutdown, the following is output:
> {noformat}
> 2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
> faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 
> 130 - org.apache.camel.camel-core - 2.15.5 | Could not unregister error 
> handler: org.apache.camel.management.mbean.ManagedErrorHandler@72c1
> e7c3 as ErrorHandler MBean.
> org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
> for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
> at 
> org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
> at 
> org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
> at 
> org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
> at 
> org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
> at 
> org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
> at 
> org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
> at 
> org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
> at 
> org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
> at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
> at 
> org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
> at 
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
> at 
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
> at 
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
> at 
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)[:1.8.0_66]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
> at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
> at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
> at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
> etc..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-9694.

Resolution: Won't Fix

> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   ... 32 more
> {code}
> Looks like the stream caching isn't invoked at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189488#comment-15189488
 ] 

Claus Ibsen commented on CAMEL-9694:


No the local work dir is only in use while the exchange of that route is 
in-flight. But when you wire-tap you fork the exchange, and the original 
exchange completes and the local work file is deleted. Then the wire tap wakes 
up after sleeping and wants to read that file which pointed to the local work 
dir.

So when you use wire tap and the likes with a ftp local work dir scenario you 
have to do that in a safer way. Such as loading the file into memory before 
doing the wire tap.

> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   ... 32 more
> {code}
> Looks like the stream caching isn't invoked at all.



--
This message was sent by 

[jira] [Updated] (CAMEL-9696) test component - Allow to pass in uri options to endpoint

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9696:
---
Fix Version/s: 2.16.3

> test component - Allow to pass in uri options to endpoint
> -
>
> Key: CAMEL-9696
> URL: https://issues.apache.org/jira/browse/CAMEL-9696
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.17.0
>
>
> The uri parameters are lost so you cannot pass in noop=true to a file 
> endpoint etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9696) test component - Allow to pass in uri options to endpoint

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-9696.

Resolution: Fixed

> test component - Allow to pass in uri options to endpoint
> -
>
> Key: CAMEL-9696
> URL: https://issues.apache.org/jira/browse/CAMEL-9696
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.16.3, 2.17.0
>
>
> The uri parameters are lost so you cannot pass in noop=true to a file 
> endpoint etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9696) test component - Allow to pass in uri options to endpoint

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-9696:
--

 Summary: test component - Allow to pass in uri options to endpoint
 Key: CAMEL-9696
 URL: https://issues.apache.org/jira/browse/CAMEL-9696
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Affects Versions: 2.16.2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.17.0


The uri parameters are lost so you cannot pass in noop=true to a file endpoint 
etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9685) camel-infinispan : support continuous query in consumer

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189375#comment-15189375
 ] 

Luca Burgazzoli commented on CAMEL-9685:


[~tristan.tarr...@gmail.com] I've added initial support for Infinispan's 
continuous query 
[here|https://github.com/lburgazzoli/apache-camel/commit/c2029a57e6b9c330fa421f047539cf00cf00a62e]
 would you be so kind to have look and report any improvement/error you may 
find ?

> camel-infinispan : support continuous query in consumer
> ---
>
> Key: CAMEL-9685
> URL: https://issues.apache.org/jira/browse/CAMEL-9685
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9689) Websocket Component Failing to Install in Karaf

[Trey Sargent (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Trey Sargent updated CAMEL-9689:

Description: 
When installing the camel-websocket component in Karaf 4.0.4 the process hangs.

When I try to install via Karaf's hot deploy I get:

karaf@root()> ERROR: Bundle org.apache.camel.camel-websocket [94] Error 
starting file:/opt/apache-karaf-4.0.4/deploy/camel-websocket-2.16.2.jar 
(org.osgi.framework.BundleException: Unable to resolve 
org.apache.camel.camel-websocket [94](R 94.0): missing requirement 
[org.apache.camel.camel-websocket [94](R 94.0)] osgi.wiring.package; 
(&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0))) 
Unresolved requirements: [[org.apache.camel.camel-websocket [94](R 94.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0)))]) 
org.osgi.framework.BundleException: Unable to resolve 
org.apache.camel.camel-websocket [94](R 94.0): missing requirement 
[org.apache.camel.camel-websocket [94](R 94.0)] osgi.wiring.package; 
(&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0))) 
Unresolved requirements: [[org.apache.camel.camel-websocket [94](R 94.0)] 
osgi.wiring.package; 
(&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0)))] at 
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111) at 
org.apache.felix.framework.Felix.startBundle(Felix.java:2117) at 
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371) at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
 at java.lang.Thread.run(Thread.java:745)

  was:
When installing the camel-websocket component in Karaf 4.0.4 the process fails 
with the following message:

Error executing command: Unable to resolve javax.mail/1.4.5: missing 
requirement [javax.mail/1.4.5] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=com.sun.mail.handlers)(version>=1.4.0))"


> Websocket Component Failing to Install in Karaf
> ---
>
> Key: CAMEL-9689
> URL: https://issues.apache.org/jira/browse/CAMEL-9689
> Project: Camel
>  Issue Type: Bug
>  Components: camel-websocket, karaf
>Affects Versions: 2.16.2
> Environment: Oracle Java 8, Apache Karaf 4.0.4
>Reporter: Trey Sargent
>
> When installing the camel-websocket component in Karaf 4.0.4 the process 
> hangs.
> When I try to install via Karaf's hot deploy I get:
> karaf@root()> ERROR: Bundle org.apache.camel.camel-websocket [94] Error 
> starting file:/opt/apache-karaf-4.0.4/deploy/camel-websocket-2.16.2.jar 
> (org.osgi.framework.BundleException: Unable to resolve 
> org.apache.camel.camel-websocket [94](R 94.0): missing requirement 
> [org.apache.camel.camel-websocket [94](R 94.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0))) 
> Unresolved requirements: [[org.apache.camel.camel-websocket [94](R 94.0)] 
> osgi.wiring.package; 
> (&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0)))]) 
> org.osgi.framework.BundleException: Unable to resolve 
> org.apache.camel.camel-websocket [94](R 94.0): missing requirement 
> [org.apache.camel.camel-websocket [94](R 94.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0))) 
> Unresolved requirements: [[org.apache.camel.camel-websocket [94](R 94.0)] 
> osgi.wiring.package; 
> (&(osgi.wiring.package=javax.servlet)(version>=2.6.0)(!(version>=3.0.0)))] at 
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4111) at 
> org.apache.felix.framework.Felix.startBundle(Felix.java:2117) at 
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371) at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>  at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Jostein Gogstad (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189226#comment-15189226
 ] 

Jostein Gogstad edited comment on CAMEL-9694 at 3/10/16 2:05 PM:
-

Looks like a missing type converter to me. The following work around seems to 
fix the problem:

{code:java}
   
from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
.convertBodyTo(InputStream.class)
.convertBodyTo(StreamCache.class)
.wireTap("direct:mydirect");

   from("direct:mydirect")...
{code}


was (Author: jgogstad):
Looks like a missing type converter to me. The following work around seems to 
fix the problem:

{code:java}
   
from("ftp://192.168.99.100/utboks/gat55?passiveMode=true=/tmp=docker=docker=true;)
.convertBodyTo(InputStream.class)
.convertBodyTo(StreamCache.class)
.wireTap("direct:mydirect");

   from("direct:mydirect")...
{code}

> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 

[jira] [Created] (CAMEL-9695) During shutdown, Camel cannot unregister error handler

[Martin Lichtin (JIRA)]

Martin Lichtin created CAMEL-9695:
-

 Summary: During shutdown, Camel cannot unregister error handler
 Key: CAMEL-9695
 URL: https://issues.apache.org/jira/browse/CAMEL-9695
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.15.5
Reporter: Martin Lichtin


According to http://camel.apache.org/redeliverypolicy.html
my camel context is like

{code:xml}
http://camel.apache.org/schema/blueprint; 
xsi:schemaLocation="http://camel.apache.org/schema/blueprint 
http://camel.apache.org/schema/blueprint/camel-blueprint.xsd;
id="myIdxt" messageHistory="false">





etc.etc.


{code}

During shutdown, the following is output:

{noformat}
2016-03-10 12:33:44,649 | WARN  | FelixStartLevel  | 
faultManagementLifecycleStrategy | faultManagementLifecycleStrategy  640 | 130 
- org.apache.camel.camel-core - 2.15.5 | Could not unregister error handler: 
org.apache.camel.management.mbean.ManagedErrorHandler@72c1
e7c3 as ErrorHandler MBean.
org.apache.camel.NoSuchBeanException: No bean could be found in the registry 
for: myErrorHandler of type: org.apache.camel.builder.ErrorHandlerBuilder
at 
org.apache.camel.util.CamelContextHelper.mandatoryLookup(CamelContextHelper.java:159)
at 
org.apache.camel.impl.DefaultRouteContext.mandatoryLookup(DefaultRouteContext.java:151)
at 
org.apache.camel.builder.ErrorHandlerBuilderRef.lookupErrorHandlerBuilder(ErrorHandlerBuilderRef.java:137)
at 
org.apache.camel.management.DefaultManagementNamingStrategy.getObjectNameForErrorHandler(DefaultManagementNamingStrategy.java:154)
at 
org.apache.camel.management.ManagedManagementStrategy.getManagedObjectName(ManagedManagementStrategy.java:104)
at 
org.apache.camel.management.ManagedManagementStrategy.unmanageObject(ManagedManagementStrategy.java:143)
at 
org.apache.camel.management.DefaultManagementLifecycleStrategy.unmanageObject(DefaultManagementLifecycleStrategy.java:839)
at 
org.apache.camel.management.DefaultManagementLifecycleStrategy.onErrorHandlerRemove(DefaultManagementLifecycleStrategy.java:638)
at 
org.apache.camel.impl.RouteService.stopChildService(RouteService.java:351)
at org.apache.camel.impl.RouteService.doStop(RouteService.java:237)
at 
org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:77)
at 
org.apache.camel.support.ChildServiceSupport.stop(ChildServiceSupport.java:101)
at 
org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:141)
at 
org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:204)
at 
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2843)
at 
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2868)
at 
org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:2856)
at 
org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:2691)
at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
at 
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)[:1.8.0_66]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_66]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497)[:1.8.0_66]
at 
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)[15:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:958)[15:org.apache.aries.blueprint.core:1.4.2]
etc..
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Jostein Gogstad (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189226#comment-15189226
 ] 

Jostein Gogstad commented on CAMEL-9694:


Looks like a missing type converter to me. The following work around seems to 
fix the problem:

{code:java}
   
from("ftp://192.168.99.100/utboks/gat55?passiveMode=true=/tmp=docker=docker=true;)
.convertBodyTo(InputStream.class)
.convertBodyTo(StreamCache.class)
.wireTap("direct:mydirect");

   from("direct:mydirect")...
{code}

> StreamCaching does not work with FTP2-components localWorkingDirectory
> --
>
> Key: CAMEL-9694
> URL: https://issues.apache.org/jira/browse/CAMEL-9694
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.2
>Reporter: Jostein Gogstad
>
> From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] 
> we read that the {{localWorkDirectory}} attribute can be used to download the 
> file up-front. Stream caching does not work in conjunction with this option.
> {code:java|title=StreamCachingTest.java}
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.LoggingLevel;
> import org.apache.camel.Processor;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.commons.io.IOUtils;
> import org.junit.Test;
> import org.slf4j.Logger;
> import org.slf4j.LoggerFactory;
> import java.io.IOException;
> import java.io.InputStream;
> public class StreamCachingTest extends CamelTestSupport {
> public static final String URI_END_OF_ROUTE = "mock:end_of_route";
> @EndpointInject(uri = URI_END_OF_ROUTE)
> private MockEndpoint endOfRoute;
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> context.setStreamCaching(true);
> 
> from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
> .wireTap("direct:mydirect");
> from("direct:mydirect")
> .process(new Processor() {
> @Override
> public void process(Exchange exchange) throws 
> Exception {
> Thread.sleep(3000);
> String s = 
> IOUtils.toString(exchange.getIn().getBody(InputStream.class));
> log.info("Consumed " + s.substring(0, 5));
> }
> })
> .to(URI_END_OF_ROUTE);
> }
> };
> }
> @Test
> public void stream_caching_with_spring() throws Exception {
> endOfRoute.expectedMessageCount(1);
> context.start();
> endOfRoute.assertIsSatisfied();
> }
> }
> {code}
> It fails with:
> {code:none}
> Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot 
> find the file specified)
>   at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
>   at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
>   at java.io.FileInputStream.(FileInputStream.java:138) 
> ~[?:1.8.0_60]
>   at 
> org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:1.8.0_60]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:1.8.0_60]
>   at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
>   at 
> org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
> ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   at 
> org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)
>  ~[camel-core-2.16.2.jar:2.16.2]
>   ... 32 more
> {code}
> Looks like the stream caching isn't invoked at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (CAMEL-9685) camel-infinispan : support continuous query in consumer

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-9685 started by Luca Burgazzoli.
--
> camel-infinispan : support continuous query in consumer
> ---
>
> Key: CAMEL-9685
> URL: https://issues.apache.org/jira/browse/CAMEL-9685
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9694) StreamCaching does not work with FTP2-components localWorkingDirectory

[Jostein Gogstad (JIRA)]

Jostein Gogstad created CAMEL-9694:
--

 Summary: StreamCaching does not work with FTP2-components 
localWorkingDirectory
 Key: CAMEL-9694
 URL: https://issues.apache.org/jira/browse/CAMEL-9694
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 2.16.2
Reporter: Jostein Gogstad


>From the [FTP2-components documentation|https://camel.apache.org/ftp2.html] we 
>read that the {{localWorkDirectory}} attribute can be used to download the 
>file up-front. Stream caching does not work in conjunction with this option.

{code:java|title=StreamCachingTest.java}
import org.apache.camel.EndpointInject;
import org.apache.camel.Exchange;
import org.apache.camel.LoggingLevel;
import org.apache.camel.Processor;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.component.mock.MockEndpoint;
import org.apache.camel.test.junit4.CamelTestSupport;
import org.apache.commons.io.IOUtils;
import org.junit.Test;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import java.io.IOException;
import java.io.InputStream;

public class StreamCachingTest extends CamelTestSupport {

public static final String URI_END_OF_ROUTE = "mock:end_of_route";

@EndpointInject(uri = URI_END_OF_ROUTE)
private MockEndpoint endOfRoute;

@Override
public boolean isUseAdviceWith() {
return true;
}

@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
context.setStreamCaching(true);


from("ftp://192.168.99.100/outbox?passiveMode=true=/tmp=docker=docker=true;)
.wireTap("direct:mydirect");

from("direct:mydirect")
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception 
{
Thread.sleep(3000);
String s = 
IOUtils.toString(exchange.getIn().getBody(InputStream.class));
log.info("Consumed " + s.substring(0, 5));
}
})
.to(URI_END_OF_ROUTE);
}
};
}

@Test
public void stream_caching_with_spring() throws Exception {
endOfRoute.expectedMessageCount(1);

context.start();

endOfRoute.assertIsSatisfied();

}
}
{code}

It fails with:
{code:none}
Caused by: java.io.FileNotFoundException: /tmp/FOO.DAT (The system cannot find 
the file specified)
at java.io.FileInputStream.open0(Native Method) ~[?:1.8.0_60]
at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:1.8.0_60]
at java.io.FileInputStream.(FileInputStream.java:138) 
~[?:1.8.0_60]
at 
org.apache.camel.converter.IOConverter.toInputStream(IOConverter.java:78) 
~[camel-core-2.16.2.jar:2.16.2]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:1.8.0_60]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[?:1.8.0_60]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[?:1.8.0_60]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
at 
org.apache.camel.util.ObjectHelper.invokeMethod(ObjectHelper.java:1243) 
~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.impl.converter.StaticMethodTypeConverter.convertTo(StaticMethodTypeConverter.java:59)
 ~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.doConvertTo(BaseTypeConverterRegistry.java:293)
 ~[camel-core-2.16.2.jar:2.16.2]
at 
org.apache.camel.impl.converter.BaseTypeConverterRegistry.convertTo(BaseTypeConverterRegistry.java:120)
 ~[camel-core-2.16.2.jar:2.16.2]
... 32 more
{code}

Looks like the stream caching isn't invoked at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9691) camel-infinispan : cleanup uri options

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-9691.

   Resolution: Fixed
Fix Version/s: 2.17.0

> camel-infinispan : cleanup uri options
> --
>
> Key: CAMEL-9691
> URL: https://issues.apache.org/jira/browse/CAMEL-9691
> Project: Camel
>  Issue Type: Task
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9693) camel-infinispan : disable building tests on JDK < 1.8

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-9693.

   Resolution: Fixed
Fix Version/s: 2.17.0

> camel-infinispan : disable building tests on JDK < 1.8
> --
>
> Key: CAMEL-9693
> URL: https://issues.apache.org/jira/browse/CAMEL-9693
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9684) camel-infinispan : add support for setting query builder in InifispanConfiguration

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-9684.

   Resolution: Fixed
Fix Version/s: 2.17.0

> camel-infinispan : add support for setting query builder in 
> InifispanConfiguration
> --
>
> Key: CAMEL-9684
> URL: https://issues.apache.org/jira/browse/CAMEL-9684
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.17.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9684) camel-infinispan : add support for setting query builder in InifispanConfiguration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189190#comment-15189190
 ] 

ASF GitHub Bot commented on CAMEL-9684:
---

Github user lburgazzoli closed the pull request at:

https://github.com/apache/camel/pull/891


> camel-infinispan : add support for setting query builder in 
> InifispanConfiguration
> --
>
> Key: CAMEL-9684
> URL: https://issues.apache.org/jira/browse/CAMEL-9684
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9691) camel-infinispan : cleanup uri options

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189188#comment-15189188
 ] 

ASF GitHub Bot commented on CAMEL-9691:
---

Github user lburgazzoli closed the pull request at:

https://github.com/apache/camel/pull/892


> camel-infinispan : cleanup uri options
> --
>
> Key: CAMEL-9691
> URL: https://issues.apache.org/jira/browse/CAMEL-9691
> Project: Camel
>  Issue Type: Task
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9693) camel-infinispan : disable building tests on JDK < 1.8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189189#comment-15189189
 ] 

ASF GitHub Bot commented on CAMEL-9693:
---

Github user lburgazzoli closed the pull request at:

https://github.com/apache/camel/pull/893


> camel-infinispan : disable building tests on JDK < 1.8
> --
>
> Key: CAMEL-9693
> URL: https://issues.apache.org/jira/browse/CAMEL-9693
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9693) camel-infinispan : disable building tests on JDK < 1.8

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189095#comment-15189095
 ] 

ASF GitHub Bot commented on CAMEL-9693:
---

GitHub user lburgazzoli opened a pull request:

https://github.com/apache/camel/pull/893

CAMEL-9693 : camel-infinispan : disable building tests on JDK < 1.8



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9693

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/893.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #893


commit 44deb074a0749a00d55b4ec73523d495f467
Author: lburgazzoli 
Date:   2016-03-10T10:56:00Z

CAMEL-9693 : camel-infinispan : disable building tests on JDK < 1.8




> camel-infinispan : disable building tests on JDK < 1.8
> --
>
> Key: CAMEL-9693
> URL: https://issues.apache.org/jira/browse/CAMEL-9693
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (CAMEL-9693) camel-infinispan : disable building tests on JDK < 1.8

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-9693 started by Luca Burgazzoli.
--
> camel-infinispan : disable building tests on JDK < 1.8
> --
>
> Key: CAMEL-9693
> URL: https://issues.apache.org/jira/browse/CAMEL-9693
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9693) camel-infinispan : disable building tests on JDK < 1.8

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-9693:
--

 Summary: camel-infinispan : disable building tests on JDK < 1.8
 Key: CAMEL-9693
 URL: https://issues.apache.org/jira/browse/CAMEL-9693
 Project: Camel
  Issue Type: Improvement
  Components: camel-infinispan
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli resolved CAMEL-9497.

Resolution: Fixed

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189012#comment-15189012
 ] 

Claus Ibsen commented on CAMEL-9497:


Sure looks good
https://cwiki.apache.org/confluence/display/CAMEL/Spring+Web+Services

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189008#comment-15189008
 ] 

Luca Burgazzoli commented on CAMEL-9497:


Sorry [~davsclaus] I'm wrong, it can be overridden as component's endpoint 
configuration sequence is:

addConsumerConfiguration --> which sets default EndpointMappingKey
setProperties --> which eventually override default EndpointMappingKey

I've added it to the list of options in confluence, let me know if the doc is 
good enough.

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188989#comment-15188989
 ] 

Claus Ibsen commented on CAMEL-9497:


Luca yeah you have maybe found something. And is that endpoint mapping key used 
in consumer only, or can the producer use it also?

If not them we can maybe remove it as an option?

Would this code return null sometimes?
EndpointMappingType.getTypeFromUriPrefix(remaining);

If it can then it seems it does not override the field. And then maybe it 
should stay.

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9497) camel-spring-ws - Component docs does not match actual code

[Luca Burgazzoli (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188981#comment-15188981
 ] 

Luca Burgazzoli commented on CAMEL-9497:


[~davsclaus] I've updated confluence, only open topic is about 
endpointMappingKey

> camel-spring-ws - Component docs does not match actual code
> ---
>
> Key: CAMEL-9497
> URL: https://issues.apache.org/jira/browse/CAMEL-9497
> Project: Camel
>  Issue Type: Task
>  Components: camel-spring-ws
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.17.0
>
>
> There is some options that do not match the @UriParam and @UriPath configured 
> on this endpoint.
> There was some time ago some contributions to this component, that didn't 
> include wiki doc updates as well. So we are a bit out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9691) camel-infinispan : cleanup uri options

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188980#comment-15188980
 ] 

ASF GitHub Bot commented on CAMEL-9691:
---

GitHub user lburgazzoli opened a pull request:

https://github.com/apache/camel/pull/892

CAMEL-9691 - camel-infinispan : cleanup uri options



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9691

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/892.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #892


commit 2034a97043016df83978878199a5c2914368ef3c
Author: lburgazzoli 
Date:   2016-03-10T09:48:43Z

CAMEL-9691 - camel-infinispan : cleanup uri options




> camel-infinispan : cleanup uri options
> --
>
> Key: CAMEL-9691
> URL: https://issues.apache.org/jira/browse/CAMEL-9691
> Project: Camel
>  Issue Type: Task
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9622) Provide well behaving features for Karaf 4x.

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-9622:
---
Fix Version/s: (was: 2.17.0)
   2.18.0

> Provide well behaving features for Karaf 4x.
> 
>
> Key: CAMEL-9622
> URL: https://issues.apache.org/jira/browse/CAMEL-9622
> Project: Camel
>  Issue Type: Improvement
>  Components: karaf
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 2.18.0
>
>
>   * Ensure completeness of features by using the maven plugin (some features 
> are missing dependencies on blueprint, etc...)
>   * Add some missing prerequisite features when using wrap protocol



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9679) Support for Hessian serialization - add new Data Format

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-9679.

Resolution: Fixed
  Assignee: Claus Ibsen

> Support for Hessian serialization - add new Data Format
> ---
>
> Key: CAMEL-9679
> URL: https://issues.apache.org/jira/browse/CAMEL-9679
> Project: Camel
>  Issue Type: New Feature
>Reporter: Jarosław Strzelecki
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.17.0
>
>
> Implement new Data Format using [Hessian 
> serialization|http://hessian.caucho.com/doc/hessian-serialization.html].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8975) camel-kafka - Message loss with batch commit

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-8975.

Resolution: Later

> camel-kafka - Message loss with batch commit
> 
>
> Key: CAMEL-8975
> URL: https://issues.apache.org/jira/browse/CAMEL-8975
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.15.2
> Environment: Unbuntu LTS 14.x, Java 7
>Reporter: Michael J. Kitchin
> Fix For: 2.17.0
>
>
> These issues center around Kafka consumer (KafaConsumer.java, line numbers 
> below):
> # Exchange exceptions/failures ignored at process() (:148), meaning:
> ## Automatic offset commit on exchange failure (e.g., processor/endpoint 
> exception)
> ## In-flight exchange loss on Camel context/runtime shutdown (i.e., route 
> interrupted -> exception suppressed -> offset committed)
> # BatchCommitConsumerTask activations are unbalanced during periods of low 
> activity, meaning:
> ## await() (:165) will timeout for active BatchCommitConsumerTask(s) when 
> other consumer threads are binding on it.hasNext() (:145) (blocking call, 
> despite no @throws)
> ## Any, previously-activated await()'ing thread will (a) get a 
> TimeoutExeception, (b) loop, and (c) get a BrokenBarrierException on the next 
> await() call and (d) exit
> ## Process will repeat until (a) all consumer stream threads have exited, (b) 
> leaving consumer dead
> ## Aggravated if process() (:148) blocks (e.g., for delay/redelivery on the 
> route)
> # An ExecutorService is obtained from Camel to handle KafkaStreams with # of 
> threads set to the consumerStreams param (:77). Since the # of KafkaStreams 
> actually created is (consumersCount * consumerStreams) and executor runnables 
> are indefinite loops, a random selection of streams will not be serviced if 
> consumersCount>1.
> Source code URL:
> - 
> https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java
> We've troubleshot this extensively and reimplemented the KafkaConsumer class 
> with params added to KafkaConfiguration to address these concerns and are 
> happy to submit these back to the community, if interested.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8975) camel-kafka - Message loss with batch commit

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-8975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188964#comment-15188964
 ] 

Claus Ibsen commented on CAMEL-8975:


We have migrated camel-kafka to be using the java client from kafka. So there 
has been some code changes there.

When 2.17 is out upgrade and give it a test there.

> camel-kafka - Message loss with batch commit
> 
>
> Key: CAMEL-8975
> URL: https://issues.apache.org/jira/browse/CAMEL-8975
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.15.2
> Environment: Unbuntu LTS 14.x, Java 7
>Reporter: Michael J. Kitchin
> Fix For: 2.17.0
>
>
> These issues center around Kafka consumer (KafaConsumer.java, line numbers 
> below):
> # Exchange exceptions/failures ignored at process() (:148), meaning:
> ## Automatic offset commit on exchange failure (e.g., processor/endpoint 
> exception)
> ## In-flight exchange loss on Camel context/runtime shutdown (i.e., route 
> interrupted -> exception suppressed -> offset committed)
> # BatchCommitConsumerTask activations are unbalanced during periods of low 
> activity, meaning:
> ## await() (:165) will timeout for active BatchCommitConsumerTask(s) when 
> other consumer threads are binding on it.hasNext() (:145) (blocking call, 
> despite no @throws)
> ## Any, previously-activated await()'ing thread will (a) get a 
> TimeoutExeception, (b) loop, and (c) get a BrokenBarrierException on the next 
> await() call and (d) exit
> ## Process will repeat until (a) all consumer stream threads have exited, (b) 
> leaving consumer dead
> ## Aggravated if process() (:148) blocks (e.g., for delay/redelivery on the 
> route)
> # An ExecutorService is obtained from Camel to handle KafkaStreams with # of 
> threads set to the consumerStreams param (:77). Since the # of KafkaStreams 
> actually created is (consumersCount * consumerStreams) and executor runnables 
> are indefinite loops, a random selection of streams will not be serviced if 
> consumersCount>1.
> Source code URL:
> - 
> https://github.com/apache/camel/blob/master/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConsumer.java
> We've troubleshot this extensively and reimplemented the KafkaConsumer class 
> with params added to KafkaConfiguration to address these concerns and are 
> happy to submit these back to the community, if interested.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Work started] (CAMEL-9691) camel-infinispan : cleanup uri options

[Luca Burgazzoli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-9691 started by Luca Burgazzoli.
--
> camel-infinispan : cleanup uri options
> --
>
> Key: CAMEL-9691
> URL: https://issues.apache.org/jira/browse/CAMEL-9691
> Project: Camel
>  Issue Type: Task
>  Components: camel-infinispan
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9692) LMAX Disruptor Component: Make it compatible with async routing engine

[JIRA]

Raúl Kripalani created CAMEL-9692:
-

 Summary: LMAX Disruptor Component: Make it compatible with async 
routing engine
 Key: CAMEL-9692
 URL: https://issues.apache.org/jira/browse/CAMEL-9692
 Project: Camel
  Issue Type: Improvement
  Components: camel-disruptor
Affects Versions: 2.16.2
Reporter: Raúl Kripalani


Currently, the {{camel-disruptor}} component is not compatible with the async 
routing engine. 

Therefore, in an InOut scenario, it keeps the calling thread waiting until the 
CountDownLatch fires.

This degree of synchronicity is contrary to a message-oriented middleware and 
contrary to the philosophy of the LMAX Disruptor itself.

We should strive to make it fully async via an {{AsyncCallback}}.

According to 
https://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work,
 it should be natively possible:

bq. We also allow consumers to wait on the results of other consumers without 
having to put another queuing stage between them. A consumer can simply watch 
the sequence number of a consumer that it is dependent on. This avoids the need 
for join stages in pipeline.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9691) camel-infinispan : cleanup uri options

[Luca Burgazzoli (JIRA)]

Luca Burgazzoli created CAMEL-9691:
--

 Summary: camel-infinispan : cleanup uri options
 Key: CAMEL-9691
 URL: https://issues.apache.org/jira/browse/CAMEL-9691
 Project: Camel
  Issue Type: Task
  Components: camel-infinispan
Reporter: Luca Burgazzoli
Assignee: Luca Burgazzoli
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)