[jira] [Assigned] (CAMEL-12244) RemoteFileProducer stopped instead of being released to the pool when "interceptSendToEndpoint" is used
[
https://issues.apache.org/jira/browse/CAMEL-12244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-12244:
---
Assignee: Claus Ibsen
> RemoteFileProducer stopped instead of being released to the pool when
> "interceptSendToEndpoint" is used
> ---
>
> Key: CAMEL-12244
> URL: https://issues.apache.org/jira/browse/CAMEL-12244
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.19.0
>Reporter: Krzysztof Szafrański
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> In our application we're using an SFTP producer with "fileExist=Move" and a
> specific "moveExisting" expression. I encountered a problem where this would
> sometimes work, and sometimes not (i.e. there would be no ".archived" file).
> Upon further investigation I found the problem and it seems to be a bug in
> Camel.
> Our SFTP endpoint looks like this:
> {code:none}
> sftp://...:.../...?username=...&privateKeyPassphrase=...&privateKeyFile=...&useUserKnownHostsFile=false&jschLoggingLevel=ERROR&fileExist=Move&moveExisting=${file:name}.archived${date:now:MMddHHmmssSSS}
> {code}
> We also have an interceptor:
> {code:none}
> route.interceptSendToEndpoint("sftp://.*";).process(exchange ->
> LOG.info("Sending file {} to {}", ...));
> {code}
> As I discovered, using the interceptor wraps the RemoteFileProducer with
> InterceptSendToEndpoint. This however changes the behavior of the
> ProducerCache:
> {code}
> public boolean doInAsyncProducer(...) {
> ...
> return producerCallback.doInAsyncProducer(producer, asyncProcessor,
> exchange, pattern, doneSync -> {
> ...
> if (producer instanceof ServicePoolAware) {
> // release back to the pool
> pool.release(endpoint, producer);
> } else if (!producer.isSingleton()) {
> // stop and shutdown non-singleton producers as we should not
> leak resources
> try {
> ServiceHelper.stopAndShutdownService(producer);
> } catch (Exception e) {
> ...
> }
> }
> ...
> });
> ...
> }
> {code}
> RemoteFileProducer implements ServicePoolAware so it would normally go back
> to the pool, but InterceptSendToEndpoint _does not_. As a result, our
> producers keep getting stopped (note that RemoteFileProducer#isSingleton
> always returns false).
> What's more, somehow they _are_ being reused and in the end we run into
> situations, where one thread is closing a producer, while another thread is
> trying to write with it.
> I set up some breakpoints that log the thread name and
> System#identityHashCode of the producer:
> {code}
> 2018-02-08 15:05:25.070 TRACE o.a.c.c.file.remote.RemoteFileProducer :
> Starting producer: RemoteFileProducer[...]
> 2018-02-08 15:05:25.073 TRACE o.a.c.c.file.remote.RemoteFileProducer :
> Processing file: [my_file] for exchange: ...
> 2018-02-08 15:05:25.073 DEBUG o.a.c.c.file.remote.RemoteFileProducer :
> Not already connected/logged in. Connecting to: ...
> doStop(), time: 1518098725112, thread [Camel (camel-1) thread #35 -
> CamelInvocationHandler], producer: 889747012
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.doStop(RemoteFileProducer.java:175)
> at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:142)
> at
> org.apache.camel.impl.InterceptSendToEndpoint$1.stop(InterceptSendToEndpoint.java:196)
> at
> org.apache.camel.support.ServiceSupport.shutdown(ServiceSupport.java:164)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:211)
> at
> org.apache.camel.impl.ProducerCache.lambda$doInAsyncProducer$2(ProducerCache.java:450)
> at
> org.apache.camel.processor.SendProcessor$2$1.done(SendProcessor.java:178)
> at
> org.apache.camel.impl.InterceptSendToEndpoint$1.process(InterceptSendToEndpoint.java:171)
> at
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:173)
> at
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:436)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:168)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:110)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.proce
[jira] [Created] (CAMEL-12266) camel-restdsl-swagger-plugin - Make it possible to chose XML generation
Claus Ibsen created CAMEL-12266: --- Summary: camel-restdsl-swagger-plugin - Make it possible to chose XML generation Key: CAMEL-12266 URL: https://issues.apache.org/jira/browse/CAMEL-12266 Project: Camel Issue Type: New Feature Components: tooling Reporter: Claus Ibsen Fix For: 2.21.0 This tool [https://github.com/apache/camel/blob/master/tooling/maven/camel-restdsl-swagger-plugin/src/main/docs/camel-package-maven-plugin.adoc] Can generate java code from a swagger doc. We should add an option so you can tell the tool to generate as either Java or XML DSL source code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12265) Reduce logging caused by load balancer probes
Quinn Stevenson created CAMEL-12265: --- Summary: Reduce logging caused by load balancer probes Key: CAMEL-12265 URL: https://issues.apache.org/jira/browse/CAMEL-12265 Project: Camel Issue Type: Improvement Components: camel-mllp Reporter: Quinn Stevenson Assignee: Quinn Stevenson When load balancers are used in front of MLLP data sources, the component logs information for every probe from the load-balance. This pollutes the log file with a large number of log entries (at the INFO/WARN levels) that can be distracting when troubleshooting. This log information will be moved to DEBUG. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12264) Concurrent modification in safeCopyProperties Method of DefaultExchange
[
https://issues.apache.org/jira/browse/CAMEL-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Wu updated CAMEL-12264:
-
Affects Version/s: 2.20.2
> Concurrent modification in safeCopyProperties Method of DefaultExchange
> ---
>
> Key: CAMEL-12264
> URL: https://issues.apache.org/jira/browse/CAMEL-12264
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.2
>Reporter: Yifan Wu
>Priority: Minor
>
> {color:#ffc66d}{color:#33}safeCopyProperties method of DefaultExchange
> class,{color} {color}
> {code:java}
> // new LinkedList<>(Collection c) is not thread-safe.
> answer.put(Exchange.MESSAGE_HISTORY, new LinkedList<>(history));
> {code}
> new LinkedList<>(Collection c) is not thread-safe. Quote from LinkedList
> implementation "The behavior of this operation is undefined if{color:#629755}
> the specified collection is modified while the operation is
> in{color}{color:#629755} progress."{color}
>
> {color:#33}In our case, when we have high throughput, we see the
> following exception (when the history is concurrently being modified.):{color}
> {color:#33}java.lang.ArrayIndexOutOfBoundsException: 19
> at java.util.LinkedList.toArray(LinkedList.java:1053)
> at java.util.LinkedList.addAll(LinkedList.java:408)
> at java.util.LinkedList.addAll(LinkedList.java:387)
> at java.util.LinkedList.(LinkedList.java:119)
> at
> org.apache.camel.impl.DefaultExchange.safeCopyProperties(DefaultExchange.java:152)
> at
> org.apache.camel.impl.DefaultExchange.copy(DefaultExchange.java:97)
> at
> org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:235)
> at
> org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:218)
> at
> org.apache.camel.processor.OnCompletionProcessor.prepareExchange(OnCompletionProcessor.java:190)
> at
> org.apache.camel.processor.OnCompletionProcessor$OnCompletionSynchronizationAfterConsumer.onComplete(OnCompletionProcessor.java:235)
> at
> org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:104)
> at
> org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:229)
> at
> org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:65){color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12264) Concurrent modification in safeCopyProperties Method of DefaultExchange
[
https://issues.apache.org/jira/browse/CAMEL-12264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Wu updated CAMEL-12264:
-
Description:
{color:#ffc66d}{color:#33}safeCopyProperties method of DefaultExchange
class,{color} {color}
{code:java}
// new LinkedList<>(Collection c) is not thread-safe.
answer.put(Exchange.MESSAGE_HISTORY, new LinkedList<>(history));
{code}
new LinkedList<>(Collection c) is not thread-safe. Quote from LinkedList
implementation "The behavior of this operation is undefined if{color:#629755}
the specified collection is modified while the operation is
in{color}{color:#629755} progress."{color}
{color:#33}In our case, when we have high throughput, we see the following
exception (when the history is concurrently being modified.):{color}
{color:#33}java.lang.ArrayIndexOutOfBoundsException: 19
at java.util.LinkedList.toArray(LinkedList.java:1053)
at java.util.LinkedList.addAll(LinkedList.java:408)
at java.util.LinkedList.addAll(LinkedList.java:387)
at java.util.LinkedList.(LinkedList.java:119)
at
org.apache.camel.impl.DefaultExchange.safeCopyProperties(DefaultExchange.java:152)
at org.apache.camel.impl.DefaultExchange.copy(DefaultExchange.java:97)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:235)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:218)
at
org.apache.camel.processor.OnCompletionProcessor.prepareExchange(OnCompletionProcessor.java:190)
at
org.apache.camel.processor.OnCompletionProcessor$OnCompletionSynchronizationAfterConsumer.onComplete(OnCompletionProcessor.java:235)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:104)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:229)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:65){color}
was:
{color:#ffc66d}{color:#33}safeCopyProperties method of DefaultExchange
class, {color}
{color}
{code:java}
// new LinkedList<>(Collection c) is not thread-safe.
answer.put(Exchange.MESSAGE_HISTORY, new LinkedList<>(history));
{code}
{color:#ffc66d}{color:#33}new LinkedList<>(Collection c) is not
thread-safe. Quote from LinkedList implementation "{color}{color}
{color:#629755}The behavior of this operation is undefined if
{color}{color:#629755}* the specified collection is modified while the
operation is in
{color}{color:#629755}* progress."{color}
{color:#33}In our case, when we have high throughput, we see the following
exception:
{color}
{color:#33}java.lang.ArrayIndexOutOfBoundsException: 19
at java.util.LinkedList.toArray(LinkedList.java:1053)
at java.util.LinkedList.addAll(LinkedList.java:408)
at java.util.LinkedList.addAll(LinkedList.java:387)
at java.util.LinkedList.(LinkedList.java:119)
at
org.apache.camel.impl.DefaultExchange.safeCopyProperties(DefaultExchange.java:152)
at org.apache.camel.impl.DefaultExchange.copy(DefaultExchange.java:97)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:235)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:218)
at
org.apache.camel.processor.OnCompletionProcessor.prepareExchange(OnCompletionProcessor.java:190)
at
org.apache.camel.processor.OnCompletionProcessor$OnCompletionSynchronizationAfterConsumer.onComplete(OnCompletionProcessor.java:235)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:104)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:229)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:65){color}
> Concurrent modification in safeCopyProperties Method of DefaultExchange
> ---
>
> Key: CAMEL-12264
> URL: https://issues.apache.org/jira/browse/CAMEL-12264
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Yifan Wu
>Priority: Minor
>
> {color:#ffc66d}{color:#33}safeCopyProperties method of DefaultExchange
> class,{color} {color}
> {code:java}
> // new LinkedList<>(Collection c) is not thread-safe.
> answer.put(Exchange.MESSAGE_HISTORY, new LinkedList<>(history));
> {code}
> new LinkedList<>(Collection c) is not thread-safe. Quote from LinkedList
> implementation "The behavior of this operation is undefined if{color:#629755}
> the specified collection is modified while the operation is
> in{color}{color:#629755} progress."{color}
>
> {color:#33}In our case, when we have high throughput, we see the
> following exception (when the history is concurrently being modif
[jira] [Created] (CAMEL-12264) Concurrent modification in safeCopyProperties Method of DefaultExchange
Yifan Wu created CAMEL-12264:
Summary: Concurrent modification in safeCopyProperties Method of
DefaultExchange
Key: CAMEL-12264
URL: https://issues.apache.org/jira/browse/CAMEL-12264
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Yifan Wu
{color:#ffc66d}{color:#33}safeCopyProperties method of DefaultExchange
class, {color}
{color}
{code:java}
// new LinkedList<>(Collection c) is not thread-safe.
answer.put(Exchange.MESSAGE_HISTORY, new LinkedList<>(history));
{code}
{color:#ffc66d}{color:#33}new LinkedList<>(Collection c) is not
thread-safe. Quote from LinkedList implementation "{color}{color}
{color:#629755}The behavior of this operation is undefined if
{color}{color:#629755}* the specified collection is modified while the
operation is in
{color}{color:#629755}* progress."{color}
{color:#33}In our case, when we have high throughput, we see the following
exception:
{color}
{color:#33}java.lang.ArrayIndexOutOfBoundsException: 19
at java.util.LinkedList.toArray(LinkedList.java:1053)
at java.util.LinkedList.addAll(LinkedList.java:408)
at java.util.LinkedList.addAll(LinkedList.java:387)
at java.util.LinkedList.(LinkedList.java:119)
at
org.apache.camel.impl.DefaultExchange.safeCopyProperties(DefaultExchange.java:152)
at org.apache.camel.impl.DefaultExchange.copy(DefaultExchange.java:97)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:235)
at
org.apache.camel.util.ExchangeHelper.createCorrelatedCopy(ExchangeHelper.java:218)
at
org.apache.camel.processor.OnCompletionProcessor.prepareExchange(OnCompletionProcessor.java:190)
at
org.apache.camel.processor.OnCompletionProcessor$OnCompletionSynchronizationAfterConsumer.onComplete(OnCompletionProcessor.java:235)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:104)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:229)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:65){color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12254) Add restart operation to route JMX mbean
[ https://issues.apache.org/jira/browse/CAMEL-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362980#comment-16362980 ] Preben Asmussen commented on CAMEL-12254: - yeah. Just remembered that :). > Add restart operation to route JMX mbean > > > Key: CAMEL-12254 > URL: https://issues.apache.org/jira/browse/CAMEL-12254 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > To make it easier to restart a route from JMX. Today you have to stop and > then start. > We need to be able to set a little delay between stop/start so the start does > not happen asap, as you may want to give the system a bit of time to just > settle down before starting up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12254) Add restart operation to route JMX mbean
[ https://issues.apache.org/jira/browse/CAMEL-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362977#comment-16362977 ] Claus Ibsen commented on CAMEL-12254: - The stop is doing graceful stop > Add restart operation to route JMX mbean > > > Key: CAMEL-12254 > URL: https://issues.apache.org/jira/browse/CAMEL-12254 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > To make it easier to restart a route from JMX. Today you have to stop and > then start. > We need to be able to set a little delay between stop/start so the start does > not happen asap, as you may want to give the system a bit of time to just > settle down before starting up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12254) Add restart operation to route JMX mbean
[ https://issues.apache.org/jira/browse/CAMEL-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362946#comment-16362946 ] Preben Asmussen commented on CAMEL-12254: - I wonder if the restart shouldn't take existing inflight exchanges into account before it tries to start the route again. > Add restart operation to route JMX mbean > > > Key: CAMEL-12254 > URL: https://issues.apache.org/jira/browse/CAMEL-12254 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > To make it easier to restart a route from JMX. Today you have to stop and > then start. > We need to be able to set a little delay between stop/start so the start does > not happen asap, as you may want to give the system a bit of time to just > settle down before starting up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12249) Camel-JMS: transferExchange - send ExchangeProperties can not be accessed before first endpoint in route
[
https://issues.apache.org/jira/browse/CAMEL-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362694#comment-16362694
]
Pascal Schumacher commented on CAMEL-12249:
---
Thank you very much, Claus!
> Camel-JMS: transferExchange - send ExchangeProperties can not be accessed
> before first endpoint in route
>
>
> Key: CAMEL-12249
> URL: https://issues.apache.org/jira/browse/CAMEL-12249
> Project: Camel
> Issue Type: Bug
> Components: came-jms
>Affects Versions: 2.20.2
>Reporter: Pascal Schumacher
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> I am using Camel 2.20.2 and ActiveMQ 5.14.5 with the _transferExchange_
> option enabled. When I read a message from a queue the send custom
> _ExchangeProperties_ are not set. After the exchange is routed to the first
> endpoint the send _ExchangeProperties_ are set.
> Unittest to replicate:
> {code:java}
> public class
> JmsTransferExchangeAccessExchangePropertiesBeforeFirstEndpointTest extends
> CamelTestSupport {
> @Test
> public void
> testSendExchangeAndAccessExchangePropertiesBeforeFirstEndpoint() throws
> Exception {
> MockEndpoint mock = getMockEndpoint("mock:result");
> mock.expectedBodiesReceived("Hello World");
> mock.expectedPropertyReceived("bar", 123);
> template.send("direct:start", new Processor() {
> public void process(Exchange exchange) throws Exception {
> exchange.getIn().setBody("Hello World");
> exchange.setProperty("bar", 123);
> }
> });
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("direct:start").to(getUri());
> from(getUri())
> // .to("log:debug") this line has uncommented to make
> the test pass
>
> .choice().when(exchangeProperty("bar").isEqualTo(123)).to("mock:result");
> }
> };
> }
>
> protected String getUri() {
> return "activemq:queue:foo?transferExchange=true";
> }
> protected CamelContext createCamelContext() throws Exception {
> CamelContext camelContext = super.createCamelContext();
> ConnectionFactory connectionFactory =
> CamelJmsTestHelper.createConnectionFactory();
> camelContext.addComponent("activemq",
> jmsComponentAutoAcknowledge(connectionFactory));
> return camelContext;
> }
> }
> {code}
> The test fails, but if I uncomment the _.to("log:debug")_ line it passes.
> The test also fails with current master of camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12249) Camel-JMS: transferExchange - send ExchangeProperties can not be accessed before first endpoint in route
[
https://issues.apache.org/jira/browse/CAMEL-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12249.
-
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.21.0
> Camel-JMS: transferExchange - send ExchangeProperties can not be accessed
> before first endpoint in route
>
>
> Key: CAMEL-12249
> URL: https://issues.apache.org/jira/browse/CAMEL-12249
> Project: Camel
> Issue Type: Bug
> Components: came-jms
>Affects Versions: 2.20.2
>Reporter: Pascal Schumacher
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> I am using Camel 2.20.2 and ActiveMQ 5.14.5 with the _transferExchange_
> option enabled. When I read a message from a queue the send custom
> _ExchangeProperties_ are not set. After the exchange is routed to the first
> endpoint the send _ExchangeProperties_ are set.
> Unittest to replicate:
> {code:java}
> public class
> JmsTransferExchangeAccessExchangePropertiesBeforeFirstEndpointTest extends
> CamelTestSupport {
> @Test
> public void
> testSendExchangeAndAccessExchangePropertiesBeforeFirstEndpoint() throws
> Exception {
> MockEndpoint mock = getMockEndpoint("mock:result");
> mock.expectedBodiesReceived("Hello World");
> mock.expectedPropertyReceived("bar", 123);
> template.send("direct:start", new Processor() {
> public void process(Exchange exchange) throws Exception {
> exchange.getIn().setBody("Hello World");
> exchange.setProperty("bar", 123);
> }
> });
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("direct:start").to(getUri());
> from(getUri())
> // .to("log:debug") this line has uncommented to make
> the test pass
>
> .choice().when(exchangeProperty("bar").isEqualTo(123)).to("mock:result");
> }
> };
> }
>
> protected String getUri() {
> return "activemq:queue:foo?transferExchange=true";
> }
> protected CamelContext createCamelContext() throws Exception {
> CamelContext camelContext = super.createCamelContext();
> ConnectionFactory connectionFactory =
> CamelJmsTestHelper.createConnectionFactory();
> camelContext.addComponent("activemq",
> jmsComponentAutoAcknowledge(connectionFactory));
> return camelContext;
> }
> }
> {code}
> The test fails, but if I uncomment the _.to("log:debug")_ line it passes.
> The test also fails with current master of camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12250) Interceptors are not working for route with redelivery strategy
[
https://issues.apache.org/jira/browse/CAMEL-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12250.
-
Resolution: Won't Fix
Assignee: Claus Ibsen
Using custom InterceptStrategy is not intended for end-users
> Interceptors are not working for route with redelivery strategy
> ---
>
> Key: CAMEL-12250
> URL: https://issues.apache.org/jira/browse/CAMEL-12250
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: Krzysztof Borgul
>Assignee: Claus Ibsen
>Priority: Major
>
> Camel interceptors are not being executed if there is redelivery strategy
> defined.
> Code below will display BEFORE and AFTER text only if you remove
> errorHandler configuration.
>
> {code:java}
> public static void main(String[] args) throws Exception {
> DefaultCamelContext context = new DefaultCamelContext();
> context.addRoutes(new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> errorHandler(new DefaultErrorHandlerBuilder()
> .maximumRedeliveries(3)
> .redeliveryDelay(2000L));
> from("direct:start")
> .process(new Processor() {
> public void process(Exchange exchange) throws Exception {
> System.out.println("PROCESSED");
> }
> });
> }
> });
> context.addInterceptStrategy(new InterceptStrategy() {
> @Override
> public Processor wrapProcessorInInterceptors(CamelContext context,
> ProcessorDefinition definition,
> Processor target, Processor nextTarget) throws Exception {
> System.out.println("INTERCEPTOR");
> return new Processor() {
> @Override
> public void process(Exchange exchange) throws Exception {
> System.out.println("BEFORE");
> target.process(exchange);
> System.out.println("AFTER");
> }
> };
> }
> });
> context.start();
> ProducerTemplate template = context.createProducerTemplate();
> template.sendBody("direct:start", "foo");
> }{code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12244) RemoteFileProducer stopped instead of being released to the pool when "interceptSendToEndpoint" is used
[
https://issues.apache.org/jira/browse/CAMEL-12244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12244:
Fix Version/s: 2.21.0
> RemoteFileProducer stopped instead of being released to the pool when
> "interceptSendToEndpoint" is used
> ---
>
> Key: CAMEL-12244
> URL: https://issues.apache.org/jira/browse/CAMEL-12244
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.19.0
>Reporter: Krzysztof Szafrański
>Priority: Major
> Fix For: 2.21.0
>
>
> In our application we're using an SFTP producer with "fileExist=Move" and a
> specific "moveExisting" expression. I encountered a problem where this would
> sometimes work, and sometimes not (i.e. there would be no ".archived" file).
> Upon further investigation I found the problem and it seems to be a bug in
> Camel.
> Our SFTP endpoint looks like this:
> {code:none}
> sftp://...:.../...?username=...&privateKeyPassphrase=...&privateKeyFile=...&useUserKnownHostsFile=false&jschLoggingLevel=ERROR&fileExist=Move&moveExisting=${file:name}.archived${date:now:MMddHHmmssSSS}
> {code}
> We also have an interceptor:
> {code:none}
> route.interceptSendToEndpoint("sftp://.*";).process(exchange ->
> LOG.info("Sending file {} to {}", ...));
> {code}
> As I discovered, using the interceptor wraps the RemoteFileProducer with
> InterceptSendToEndpoint. This however changes the behavior of the
> ProducerCache:
> {code}
> public boolean doInAsyncProducer(...) {
> ...
> return producerCallback.doInAsyncProducer(producer, asyncProcessor,
> exchange, pattern, doneSync -> {
> ...
> if (producer instanceof ServicePoolAware) {
> // release back to the pool
> pool.release(endpoint, producer);
> } else if (!producer.isSingleton()) {
> // stop and shutdown non-singleton producers as we should not
> leak resources
> try {
> ServiceHelper.stopAndShutdownService(producer);
> } catch (Exception e) {
> ...
> }
> }
> ...
> });
> ...
> }
> {code}
> RemoteFileProducer implements ServicePoolAware so it would normally go back
> to the pool, but InterceptSendToEndpoint _does not_. As a result, our
> producers keep getting stopped (note that RemoteFileProducer#isSingleton
> always returns false).
> What's more, somehow they _are_ being reused and in the end we run into
> situations, where one thread is closing a producer, while another thread is
> trying to write with it.
> I set up some breakpoints that log the thread name and
> System#identityHashCode of the producer:
> {code}
> 2018-02-08 15:05:25.070 TRACE o.a.c.c.file.remote.RemoteFileProducer :
> Starting producer: RemoteFileProducer[...]
> 2018-02-08 15:05:25.073 TRACE o.a.c.c.file.remote.RemoteFileProducer :
> Processing file: [my_file] for exchange: ...
> 2018-02-08 15:05:25.073 DEBUG o.a.c.c.file.remote.RemoteFileProducer :
> Not already connected/logged in. Connecting to: ...
> doStop(), time: 1518098725112, thread [Camel (camel-1) thread #35 -
> CamelInvocationHandler], producer: 889747012
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.doStop(RemoteFileProducer.java:175)
> at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:142)
> at
> org.apache.camel.impl.InterceptSendToEndpoint$1.stop(InterceptSendToEndpoint.java:196)
> at
> org.apache.camel.support.ServiceSupport.shutdown(ServiceSupport.java:164)
> at
> org.apache.camel.util.ServiceHelper.stopAndShutdownService(ServiceHelper.java:211)
> at
> org.apache.camel.impl.ProducerCache.lambda$doInAsyncProducer$2(ProducerCache.java:450)
> at
> org.apache.camel.processor.SendProcessor$2$1.done(SendProcessor.java:178)
> at
> org.apache.camel.impl.InterceptSendToEndpoint$1.process(InterceptSendToEndpoint.java:171)
> at
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:173)
> at
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:436)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:168)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:120)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:110)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541)
>
[jira] [Commented] (CAMEL-12249) Camel-JMS: transferExchange - send ExchangeProperties can not be accessed before first endpoint in route
[
https://issues.apache.org/jira/browse/CAMEL-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362479#comment-16362479
]
Claus Ibsen commented on CAMEL-12249:
-
Okay just looked in the source that option only triggers the headers, and the
transferExchange is unmarshalled when accessing the body, so will get that
improved so the eager option works for that too.
> Camel-JMS: transferExchange - send ExchangeProperties can not be accessed
> before first endpoint in route
>
>
> Key: CAMEL-12249
> URL: https://issues.apache.org/jira/browse/CAMEL-12249
> Project: Camel
> Issue Type: Bug
> Components: came-jms
>Affects Versions: 2.20.2
>Reporter: Pascal Schumacher
>Priority: Major
>
> I am using Camel 2.20.2 and ActiveMQ 5.14.5 with the _transferExchange_
> option enabled. When I read a message from a queue the send custom
> _ExchangeProperties_ are not set. After the exchange is routed to the first
> endpoint the send _ExchangeProperties_ are set.
> Unittest to replicate:
> {code:java}
> public class
> JmsTransferExchangeAccessExchangePropertiesBeforeFirstEndpointTest extends
> CamelTestSupport {
> @Test
> public void
> testSendExchangeAndAccessExchangePropertiesBeforeFirstEndpoint() throws
> Exception {
> MockEndpoint mock = getMockEndpoint("mock:result");
> mock.expectedBodiesReceived("Hello World");
> mock.expectedPropertyReceived("bar", 123);
> template.send("direct:start", new Processor() {
> public void process(Exchange exchange) throws Exception {
> exchange.getIn().setBody("Hello World");
> exchange.setProperty("bar", 123);
> }
> });
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("direct:start").to(getUri());
> from(getUri())
> // .to("log:debug") this line has uncommented to make
> the test pass
>
> .choice().when(exchangeProperty("bar").isEqualTo(123)).to("mock:result");
> }
> };
> }
>
> protected String getUri() {
> return "activemq:queue:foo?transferExchange=true";
> }
> protected CamelContext createCamelContext() throws Exception {
> CamelContext camelContext = super.createCamelContext();
> ConnectionFactory connectionFactory =
> CamelJmsTestHelper.createConnectionFactory();
> camelContext.addComponent("activemq",
> jmsComponentAutoAcknowledge(connectionFactory));
> return camelContext;
> }
> }
> {code}
> The test fails, but if I uncomment the _.to("log:debug")_ line it passes.
> The test also fails with current master of camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12259) Error creating
[ https://issues.apache.org/jira/browse/CAMEL-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362470#comment-16362470 ] Michael Bohan commented on CAMEL-12259: --- Ok, will do. -Michael > Error creating > --- > > Key: CAMEL-12259 > URL: https://issues.apache.org/jira/browse/CAMEL-12259 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-jms >Affects Versions: 2.20.2 > Environment: Windows 10 64-bit > Java 8 > Karaf 4.1.4 > Here are all the installed components in Karaf (I left out .xml camel > contexts for now. There are about 15 installed): > START LEVEL 100 , List Threshold: 50 > ID | State | Lvl | Version | Name > +--+-++- > 29 | Active | 80 | 4.1.4 | Apache Karaf :: OSGi Services :: Event > 67 | Active | 50 | 2.20.2 | camel-blueprint > 68 | Active | 80 | 2.20.2 | camel-commands-core > 69 | Active | 50 | 2.20.2 | camel-core > 70 | Active | 80 | 2.20.2 | camel-karaf-commands > 74 | Active | 50 | 1.6.0 | JavaMail API > 75 | Active | 50 | 2.20.2 | camel-mail > 76 | Active | 80 | 19.0.0 | Guava: Google Core Libraries for Java > 77 | Active | 80 | 4.1.16.Final | Netty/Buffer > 78 | Active | 80 | 4.1.16.Final | Netty/Codec > 79 | Active | 80 | 4.1.16.Final | Netty/Codec/HTTP > 80 | Active | 80 | 4.1.16.Final | Netty/Codec/MQTT > 81 | Active | 80 | 4.1.16.Final | Netty/Common > 82 | Active | 80 | 4.1.16.Final | Netty/Handler > 83 | Active | 80 | 4.1.16.Final | Netty/Resolver > 84 | Active | 80 | 4.1.16.Final | Netty/Transport > 85 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Epoll > 86 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/KQueue > 87 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Unix/Common > 89 | Active | 80 | 1.2.0 | CDI APIs > 90 | Active | 80 | 1.2 | javax.interceptor API > 91 | Active | 80 | 1.2 | javax.transaction API > 92 | Active | 80 | 2.4.0 | ActiveMQ Artemis AMQP Protocol > 93 | Active | 80 | 2.4.0 | ActiveMQ Artemis HornetQ Protocol > 94 | Active | 80 | 2.4.0 | ActiveMQ Artemis HQClient Protocol > 95 | Active | 80 | 2.4.0 | ActiveMQ Artemis MQTT Protocol > 96 | Active | 80 | 2.4.0 | ActiveMQ Artemis Native POM > 97 | Active | 80 | 2.4.0 | ActiveMQ Artemis OpenWire Protocol > 98 | Active | 80 | 2.4.0 | ActiveMQ Artemis Server OSGi > 99 | Active | 80 | 2.4.0 | ActiveMQ Artemis STOMP Protocol > 100 | Active | 80 | 1.1.1 | Apache Aries Transaction Blueprint > 101 | Active | 80 | 2.1.0 | Apache Aries Transaction Blueprint > 102 | Active | 80 | 1.3.3 | Apache Aries Transaction Manager > 103 | Active | 80 | 1.9.3 | Apache Commons BeanUtils > 104 | Active | 50 | 3.2.2 | Apache Commons Collections > 105 | Active | 80 | 1.0.2 | Apache Felix Coordinator Service > 108 | Active | 80 | 1.0.1 | geronimo-j2ee-management_1.1_spec > 109 | Active | 50 | 1.0.0.alpha-2 | Apache Geronimo JMS Spec 2.0 > 110 | Active | 80 | 0.9.5 | Johnzon :: Core > 114 | Active | 80 | 0.26.0 | QpidJMS Client > 115 | Active | 80 | 0.22.0 | Proton-J > 116 | Active | 80 | 1.0.0.2 | Apache ServiceMix :: Bundles :: javax.inject > 117 | Active | 80 | 2.9.0 | Apache ServiceMix :: Specs :: JSon API 1.1 > 118 | Active | 80 | 1.11.0 | hawtbuf > 119 | Active | 80 | 3.6.13.Final | JGroups > 120 | Active | 50 | 5.15.3 | activemq-karaf > 121 | Active | 50 | 2.6.7 | Jackson-annotations > 122 | Active | 50 | 2.6.7 | Jackson-core > 123 | Active | 50 | 2.6.7 | jackson-databind > 125 | Active | 50 | 2.9 | Joda-Time > 126 | Active | 50 | 3.1.4 | activeio-core > 127 | Active | 50 | 5.15.3 | activemq-osgi > 128 | Active | 50 | 1.9.0 | Apache Commons Codec > 129 | Active | 50 | 2.6 | Commons Lang > 130 | Active | 50 | 3.6.0 | Apache Commons Net > 131 | Active | 50 | 2.4.2 | Apache Commons Pool > 132 | Active | 80 | 3.1.1 | Geronimo TxManager :: Connector > 133 | Active | 80 | 1.0 | J2EE Connector 1.6 > 135 | Active | 80 | 1.1 | Apache Geronimo JSR-303 Bean Validation Spec API > 136 | Active | 50 | 3.4.6 | ZooKeeper Bundle > 139 | Active | 50 | 1.9.2.1 | Apache ServiceMix :: Bundles :: jasypt > 146 | Active | 50 | 1.7.0.6 | Apache ServiceMix :: Bundles :: velocity > 147 | Active | 50 | 1.1.0.4c_5 | Apache ServiceMix :: Bundles :: xpp3 > 148 | Active | 50 | 1.4.8.1 | Apache ServiceMix :: Bundles :: xstream > 151 | Active | 50 | 1.3.8 | jettison > 171 | Active | 50 | 0.6.4 | JAXB2 Basics - Runtime > 176 | Active | 50 | 2.11.0.v20140415-163722-cac6383e66 | Scala Standard > Library > 177 | Active | 50 | 2.20.2 | camel-jms > 178 | Active | 50 | 1.6.0 | Commons Pool > 181 | Active | 80 | 2.0.0 | hawtio :: hawtio-json-schema-mbean > 182 | Failure | 80 | 2.0.0 | hawtio :: Karaf terminal plugin > 183 | Active | 80 | 2.0.0 | hawtio :: hawtio-maven-indexer > 184 | Active | 80 | 2.0.0 | hawtio :: ha
[jira] [Resolved] (CAMEL-12254) Add restart operation to route JMX mbean
[ https://issues.apache.org/jira/browse/CAMEL-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12254. - Resolution: Fixed > Add restart operation to route JMX mbean > > > Key: CAMEL-12254 > URL: https://issues.apache.org/jira/browse/CAMEL-12254 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > To make it easier to restart a route from JMX. Today you have to stop and > then start. > We need to be able to set a little delay between stop/start so the start does > not happen asap, as you may want to give the system a bit of time to just > settle down before starting up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAMEL-12259) Error creating
[ https://issues.apache.org/jira/browse/CAMEL-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bohan closed CAMEL-12259. - Estimated Complexity: (was: Unknown) > Error creating > --- > > Key: CAMEL-12259 > URL: https://issues.apache.org/jira/browse/CAMEL-12259 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-jms >Affects Versions: 2.20.2 > Environment: Windows 10 64-bit > Java 8 > Karaf 4.1.4 > Here are all the installed components in Karaf (I left out .xml camel > contexts for now. There are about 15 installed): > START LEVEL 100 , List Threshold: 50 > ID | State | Lvl | Version | Name > +--+-++- > 29 | Active | 80 | 4.1.4 | Apache Karaf :: OSGi Services :: Event > 67 | Active | 50 | 2.20.2 | camel-blueprint > 68 | Active | 80 | 2.20.2 | camel-commands-core > 69 | Active | 50 | 2.20.2 | camel-core > 70 | Active | 80 | 2.20.2 | camel-karaf-commands > 74 | Active | 50 | 1.6.0 | JavaMail API > 75 | Active | 50 | 2.20.2 | camel-mail > 76 | Active | 80 | 19.0.0 | Guava: Google Core Libraries for Java > 77 | Active | 80 | 4.1.16.Final | Netty/Buffer > 78 | Active | 80 | 4.1.16.Final | Netty/Codec > 79 | Active | 80 | 4.1.16.Final | Netty/Codec/HTTP > 80 | Active | 80 | 4.1.16.Final | Netty/Codec/MQTT > 81 | Active | 80 | 4.1.16.Final | Netty/Common > 82 | Active | 80 | 4.1.16.Final | Netty/Handler > 83 | Active | 80 | 4.1.16.Final | Netty/Resolver > 84 | Active | 80 | 4.1.16.Final | Netty/Transport > 85 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Epoll > 86 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/KQueue > 87 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Unix/Common > 89 | Active | 80 | 1.2.0 | CDI APIs > 90 | Active | 80 | 1.2 | javax.interceptor API > 91 | Active | 80 | 1.2 | javax.transaction API > 92 | Active | 80 | 2.4.0 | ActiveMQ Artemis AMQP Protocol > 93 | Active | 80 | 2.4.0 | ActiveMQ Artemis HornetQ Protocol > 94 | Active | 80 | 2.4.0 | ActiveMQ Artemis HQClient Protocol > 95 | Active | 80 | 2.4.0 | ActiveMQ Artemis MQTT Protocol > 96 | Active | 80 | 2.4.0 | ActiveMQ Artemis Native POM > 97 | Active | 80 | 2.4.0 | ActiveMQ Artemis OpenWire Protocol > 98 | Active | 80 | 2.4.0 | ActiveMQ Artemis Server OSGi > 99 | Active | 80 | 2.4.0 | ActiveMQ Artemis STOMP Protocol > 100 | Active | 80 | 1.1.1 | Apache Aries Transaction Blueprint > 101 | Active | 80 | 2.1.0 | Apache Aries Transaction Blueprint > 102 | Active | 80 | 1.3.3 | Apache Aries Transaction Manager > 103 | Active | 80 | 1.9.3 | Apache Commons BeanUtils > 104 | Active | 50 | 3.2.2 | Apache Commons Collections > 105 | Active | 80 | 1.0.2 | Apache Felix Coordinator Service > 108 | Active | 80 | 1.0.1 | geronimo-j2ee-management_1.1_spec > 109 | Active | 50 | 1.0.0.alpha-2 | Apache Geronimo JMS Spec 2.0 > 110 | Active | 80 | 0.9.5 | Johnzon :: Core > 114 | Active | 80 | 0.26.0 | QpidJMS Client > 115 | Active | 80 | 0.22.0 | Proton-J > 116 | Active | 80 | 1.0.0.2 | Apache ServiceMix :: Bundles :: javax.inject > 117 | Active | 80 | 2.9.0 | Apache ServiceMix :: Specs :: JSon API 1.1 > 118 | Active | 80 | 1.11.0 | hawtbuf > 119 | Active | 80 | 3.6.13.Final | JGroups > 120 | Active | 50 | 5.15.3 | activemq-karaf > 121 | Active | 50 | 2.6.7 | Jackson-annotations > 122 | Active | 50 | 2.6.7 | Jackson-core > 123 | Active | 50 | 2.6.7 | jackson-databind > 125 | Active | 50 | 2.9 | Joda-Time > 126 | Active | 50 | 3.1.4 | activeio-core > 127 | Active | 50 | 5.15.3 | activemq-osgi > 128 | Active | 50 | 1.9.0 | Apache Commons Codec > 129 | Active | 50 | 2.6 | Commons Lang > 130 | Active | 50 | 3.6.0 | Apache Commons Net > 131 | Active | 50 | 2.4.2 | Apache Commons Pool > 132 | Active | 80 | 3.1.1 | Geronimo TxManager :: Connector > 133 | Active | 80 | 1.0 | J2EE Connector 1.6 > 135 | Active | 80 | 1.1 | Apache Geronimo JSR-303 Bean Validation Spec API > 136 | Active | 50 | 3.4.6 | ZooKeeper Bundle > 139 | Active | 50 | 1.9.2.1 | Apache ServiceMix :: Bundles :: jasypt > 146 | Active | 50 | 1.7.0.6 | Apache ServiceMix :: Bundles :: velocity > 147 | Active | 50 | 1.1.0.4c_5 | Apache ServiceMix :: Bundles :: xpp3 > 148 | Active | 50 | 1.4.8.1 | Apache ServiceMix :: Bundles :: xstream > 151 | Active | 50 | 1.3.8 | jettison > 171 | Active | 50 | 0.6.4 | JAXB2 Basics - Runtime > 176 | Active | 50 | 2.11.0.v20140415-163722-cac6383e66 | Scala Standard > Library > 177 | Active | 50 | 2.20.2 | camel-jms > 178 | Active | 50 | 1.6.0 | Commons Pool > 181 | Active | 80 | 2.0.0 | hawtio :: hawtio-json-schema-mbean > 182 | Failure | 80 | 2.0.0 | hawtio :: Karaf terminal plugin > 183 | Active | 80 | 2.0.0 | hawtio :: hawtio-maven-indexer > 184 | Active | 80 | 2.0.0 | hawtio :: hawtio-osgi-jmx > 185 | Active | 80 | 2.0.
[jira] [Assigned] (CAMEL-12254) Add restart operation to route JMX mbean
[ https://issues.apache.org/jira/browse/CAMEL-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-12254: --- Assignee: Claus Ibsen > Add restart operation to route JMX mbean > > > Key: CAMEL-12254 > URL: https://issues.apache.org/jira/browse/CAMEL-12254 > Project: Camel > Issue Type: Improvement > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > To make it easier to restart a route from JMX. Today you have to stop and > then start. > We need to be able to set a little delay between stop/start so the start does > not happen asap, as you may want to give the system a bit of time to just > settle down before starting up again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12249) Camel-JMS: transferExchange - send ExchangeProperties can not be accessed before first endpoint in route
[
https://issues.apache.org/jira/browse/CAMEL-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362413#comment-16362413
]
Claus Ibsen commented on CAMEL-12249:
-
You need then to turn on eagerLoadingOfProperties=true
> Camel-JMS: transferExchange - send ExchangeProperties can not be accessed
> before first endpoint in route
>
>
> Key: CAMEL-12249
> URL: https://issues.apache.org/jira/browse/CAMEL-12249
> Project: Camel
> Issue Type: Bug
> Components: came-jms
>Affects Versions: 2.20.2
>Reporter: Pascal Schumacher
>Priority: Major
>
> I am using Camel 2.20.2 and ActiveMQ 5.14.5 with the _transferExchange_
> option enabled. When I read a message from a queue the send custom
> _ExchangeProperties_ are not set. After the exchange is routed to the first
> endpoint the send _ExchangeProperties_ are set.
> Unittest to replicate:
> {code:java}
> public class
> JmsTransferExchangeAccessExchangePropertiesBeforeFirstEndpointTest extends
> CamelTestSupport {
> @Test
> public void
> testSendExchangeAndAccessExchangePropertiesBeforeFirstEndpoint() throws
> Exception {
> MockEndpoint mock = getMockEndpoint("mock:result");
> mock.expectedBodiesReceived("Hello World");
> mock.expectedPropertyReceived("bar", 123);
> template.send("direct:start", new Processor() {
> public void process(Exchange exchange) throws Exception {
> exchange.getIn().setBody("Hello World");
> exchange.setProperty("bar", 123);
> }
> });
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("direct:start").to(getUri());
> from(getUri())
> // .to("log:debug") this line has uncommented to make
> the test pass
>
> .choice().when(exchangeProperty("bar").isEqualTo(123)).to("mock:result");
> }
> };
> }
>
> protected String getUri() {
> return "activemq:queue:foo?transferExchange=true";
> }
> protected CamelContext createCamelContext() throws Exception {
> CamelContext camelContext = super.createCamelContext();
> ConnectionFactory connectionFactory =
> CamelJmsTestHelper.createConnectionFactory();
> camelContext.addComponent("activemq",
> jmsComponentAutoAcknowledge(connectionFactory));
> return camelContext;
> }
> }
> {code}
> The test fails, but if I uncomment the _.to("log:debug")_ line it passes.
> The test also fails with current master of camel.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12222) ResrSwaggerServlet removes last part of context root
[
https://issues.apache.org/jira/browse/CAMEL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1.
-
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.21.0
2.20.3
2.19.5
Thanks for the PR.
I fixed the checkstyle issue
http://camel.apache.org/building.html
> ResrSwaggerServlet removes last part of context root
>
>
> Key: CAMEL-1
> URL: https://issues.apache.org/jira/browse/CAMEL-1
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger
>Reporter: Darius Cooper
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.19.5, 2.20.3, 2.21.0
>
>
> The method within RestSwaggerServlet, looks for the last "/" in the context
> root, and drops anything after that slash.
> {code:java}
> private String translateContextPath(HttpServletRequest request) {
> String path = request.getContextPath();
> if (path.isEmpty() || path.equals("/")) {
> return "";
> } else {
> int idx = path.lastIndexOf("/");
> if (idx > 0) {
> return path.substring(0, idx);
> }
> }
> return path;
> }{code}
> Even though this has been deprecated, it would be good to fix it.
> An approach could be to add a servlet init parameter named
> "translateContextPath" which would default to true, and would work exactly as
> it does today by default. if set to false, it would return whatever value is
> in request.getContextPath() , with no translation.
> Also, to avoid the NPE thrown, pass in an empty RestConfiguration to
> RestSwaggerSupport.renderResourceListing()
> (See: https://issues.apache.org/jira/browse/CAMEL-12038)
> I plan on working on this. Creating a Jira to get feedback on the approach
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12170) [XChange] Add initial support for account management
[ https://issues.apache.org/jira/browse/CAMEL-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362404#comment-16362404 ] ASF GitHub Bot commented on CAMEL-12170: Github user davsclaus closed the pull request at: https://github.com/apache/camel/pull/2216 > [XChange] Add initial support for account management > > > Key: CAMEL-12170 > URL: https://issues.apache.org/jira/browse/CAMEL-12170 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12263) Using "PROPAGATION_REQUIRES_NEW" appears to create two new transactions instead of one
Jim Reitz created CAMEL-12263:
-
Summary: Using "PROPAGATION_REQUIRES_NEW" appears to create two
new transactions instead of one
Key: CAMEL-12263
URL: https://issues.apache.org/jira/browse/CAMEL-12263
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.20.2, 2.19.4, 2.18.5, 2.17.7, 2.16.5, 2.15.6, 2.14.3,
2.13.4
Environment: java8
Reporter: Jim Reitz
I am in the process of upgrading from Camel 2.12.x to 2.18.x. I have a
unit test that verifies transacted routes work as expected. The test used
to work but after upgrading Camel, it now fails. The failure appears to be
related to encountering a route with "PROPAGATION_REQUIRES_NEW".
The test uses a mock platform transaction manager, and it verifies that
getTransaction() and commit() are only called once on that mock. However,
after changing to Camel 2.13.4 or above (have tried the latest point
release of each major version up to 2.18.3), the test now fails because
getTransaction() and commit() are called twice on the platform transaction
manager mock. In other words, Camel appears to be be creating two
transactions when it should only be creating one. Note that this behavior
is not seen when using PROPAGATION_REQUIRED.
The route in the test looks like this:
EventDrivenConsumerRoute[direct-vm://rollbackAll.innerRoute -> Channel[
TransactionErrorHandler:PROPAGATION_REQUIRES_NEW[
Channel[sendTo(mock://result)>
In addition I see the following two identical log statements from the
output of the test (including the transactionKey 0x6775c0d1 in parens)
which seem to reinforce my summation of what's happening:
2018-01-10 19:25:36,804 DEBUG [main]
org.apache.camel.spring.spi.TransactionErrorHandler
-
...
2018-01-10 19:25:37,966 DEBUG [main]
org.apache.camel.spring.spi.TransactionErrorHandler
-
It is not practical for me to post the test as it is on an isolated
machine/system.
When using the debugger in Eclipse to step through the test, I noticed in
TransactionErrorHandler#process(Exchange) line 98 (Camel version 2.18.3)
has this line that I believe was modified in version 2.13.4:
if(transactionTemplate.getPropagationBehavior() !=
TransactionDefinition.PROPAGATION_REQUIRES_NEW
&& exchange.getUnitOfWork().isTransactedBy(transactionKey)) {
I believe the issue is related to the above line. This conditional block
determines if the code calls processByErrorHandler(Exchange) or
processInTransaction(Exchange). In the case of the above documented route,
processInTransaction(Exchange) is called twice (I believe in error),
instead of calling processInTransaction(Exchange) first, and then
subsequently calling processByErrorHandler(Exchange).
If I'm correct, I can see how this bug could be overlooked because creating
an extra transaction doesn't really have any bad side effects except for
overhead/performance.
I posted this in the Camel Users formum, but received no satisfactory
explanation.
[http://camel.465427.n5.nabble.com/Using-quot-PROPAGATION-REQUIRES-NEW-quot-appears-to-create-two-new-transactions-instead-of-one-td5816606.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12222) ResrSwaggerServlet removes last part of context root
[
https://issues.apache.org/jira/browse/CAMEL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362398#comment-16362398
]
ASF GitHub Bot commented on CAMEL-1:
Github user davsclaus closed the pull request at:
https://github.com/apache/camel/pull/2220
> ResrSwaggerServlet removes last part of context root
>
>
> Key: CAMEL-1
> URL: https://issues.apache.org/jira/browse/CAMEL-1
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger
>Reporter: Darius Cooper
>Priority: Minor
>
> The method within RestSwaggerServlet, looks for the last "/" in the context
> root, and drops anything after that slash.
> {code:java}
> private String translateContextPath(HttpServletRequest request) {
> String path = request.getContextPath();
> if (path.isEmpty() || path.equals("/")) {
> return "";
> } else {
> int idx = path.lastIndexOf("/");
> if (idx > 0) {
> return path.substring(0, idx);
> }
> }
> return path;
> }{code}
> Even though this has been deprecated, it would be good to fix it.
> An approach could be to add a servlet init parameter named
> "translateContextPath" which would default to true, and would work exactly as
> it does today by default. if set to false, it would return whatever value is
> in request.getContextPath() , with no translation.
> Also, to avoid the NPE thrown, pass in an empty RestConfiguration to
> RestSwaggerSupport.renderResourceListing()
> (See: https://issues.apache.org/jira/browse/CAMEL-12038)
> I plan on working on this. Creating a Jira to get feedback on the approach
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12222) ResrSwaggerServlet removes last part of context root
[
https://issues.apache.org/jira/browse/CAMEL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362397#comment-16362397
]
ASF GitHub Bot commented on CAMEL-1:
davsclaus closed pull request #2220: CAMEL-1: RestSwaggerServlet - added
option to suppress "translate…
URL: https://github.com/apache/camel/pull/2220
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/components/camel-swagger-java/src/main/java/org/apache/camel/swagger/servlet/RestSwaggerServlet.java
b/components/camel-swagger-java/src/main/java/org/apache/camel/swagger/servlet/RestSwaggerServlet.java
index 51ca3d2e0d7..15f9d001627 100644
---
a/components/camel-swagger-java/src/main/java/org/apache/camel/swagger/servlet/RestSwaggerServlet.java
+++
b/components/camel-swagger-java/src/main/java/org/apache/camel/swagger/servlet/RestSwaggerServlet.java
@@ -34,6 +34,7 @@
import org.apache.camel.Exchange;
import org.apache.camel.impl.DefaultClassResolver;
import org.apache.camel.spi.ClassResolver;
+import org.apache.camel.spi.RestConfiguration;
import org.apache.camel.swagger.RestApiResponseAdapter;
import org.apache.camel.swagger.RestSwaggerSupport;
import org.apache.camel.util.EndpointHelper;
@@ -61,6 +62,19 @@
private String apiContextIdPattern;
private boolean apiContextIdListing;
+private boolean translateContextPath = true;
+
+
+public boolean isTranslateContextPath() { return translateContextPath; }
+
+/**
+ * Sets whether the context path of the request should be translated
(true) or used as-is (false)
+ * Optional, Defaults to true
+ * @param translateContextPath
+ */
+public void setTranslateContextPath(boolean translateContextPath) {
this.translateContextPath = translateContextPath; }
+
+
public String getApiContextIdPattern() {
return apiContextIdPattern;
@@ -115,6 +129,11 @@ public void init(final ServletConfig config) throws
ServletException {
if (listing != null) {
apiContextIdListing = Boolean.valueOf(listing.toString());
}
+Object translate = parameters.remove("translateContextPath");
+if (translate != null) {
+translateContextPath = Boolean.valueOf(translate.toString());
+}
+
}
@Override
@@ -192,7 +211,7 @@ protected void doGet(HttpServletRequest request,
HttpServletResponse response) t
if (!match) {
adapter.noContent();
} else {
-support.renderResourceListing(adapter, swaggerConfig,
name, route, json, yaml, classResolver, null);
+support.renderResourceListing(adapter, swaggerConfig,
name, route, json, yaml, classResolver, new RestConfiguration());
}
}
} catch (Exception e) {
@@ -229,6 +248,9 @@ private void initBaseAndApiPaths(HttpServletRequest
request) throws MalformedURL
*/
private String translateContextPath(HttpServletRequest request) {
String path = request.getContextPath();
+if (!translateContextPath) {
+return path;
+}
if (path.isEmpty() || path.equals("/")) {
return "";
} else {
@@ -240,4 +262,4 @@ private String translateContextPath(HttpServletRequest
request) {
return path;
}
-}
+}
\ No newline at end of file
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> ResrSwaggerServlet removes last part of context root
>
>
> Key: CAMEL-1
> URL: https://issues.apache.org/jira/browse/CAMEL-1
> Project: Camel
> Issue Type: Bug
> Components: camel-swagger
>Reporter: Darius Cooper
>Priority: Minor
>
> The method within RestSwaggerServlet, looks for the last "/" in the context
> root, and drops anything after that slash.
> {code:java}
> private String translateContextPath(HttpServletRequest request) {
> String path = request.getContextPath();
> if (path.isEmpty() || path.equals("/")) {
> return "";
> } else {
> int idx = path.lastIndexOf("/");
> if (idx > 0) {
> return path.substring(0, idx);
> }
> }
> return path;
> }{code}
> Even though this has been deprecated, it would be good to fix it.
> An approach could be to add a servlet init parameter named
> "translateConte
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362392#comment-16362392
]
Claus Ibsen commented on CAMEL-12262:
-
[~coheig] btw in that git commit
([https://github.com/apache/camel/commit/1798974a64eb54c46c0ffb4034adf73e62d4e260)]
the chiper DES is excluded. But as Lyubomir says what about 3DES dont we want
to exclude that too? And if so we would need to update the default pattern for
that in the source code.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened CAMEL-12262:
-
Yeah good point about 3DES - it should likely be excluded as well.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12262.
-
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.21.0
Okay so it was the wiki system that shows the text in italic font if you use
underlineXXXunderline, so I have corrected that in the docs.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362381#comment-16362381
]
Lyubomir commented on CAMEL-12262:
--
Please confirm the issue is in the documentation only, and the code is
implemented as expected.
The git commit in discussion
[here|https://github.com/apache/camel/commit/1798974a64eb54c46c0ffb4034adf73e62d4e260]
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362375#comment-16362375
]
Claus Ibsen commented on CAMEL-12262:
-
See the top of the page, the old wiki pages are in process of being migrated
and they will become out of sync.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362372#comment-16362372
]
Lyubomir edited comment on CAMEL-12262 at 2/13/18 2:13 PM:
---
[Documentation|http://camel.apache.org/camel-configuration-utilities.html] -
Also added to the ticket Description.
Could you confirm it is a Documentation issue and not a coding mistake ?
was (Author: atanasov):
[Documentation|http://camel.apache.org/camel-configuration-utilities.html] -
Also added to the ticket Description.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362372#comment-16362372
]
Lyubomir commented on CAMEL-12262:
--
[Documentation|http://camel.apache.org/camel-configuration-utilities.html] -
Also added to the ticket Description.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12259) Error creating
[ https://issues.apache.org/jira/browse/CAMEL-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12259. - Resolution: Invalid Use the user mailing list or places like gitter or stackoverflow to get help first > Error creating > --- > > Key: CAMEL-12259 > URL: https://issues.apache.org/jira/browse/CAMEL-12259 > Project: Camel > Issue Type: Bug > Components: camel-activemq, camel-jms >Affects Versions: 2.20.2 > Environment: Windows 10 64-bit > Java 8 > Karaf 4.1.4 > Here are all the installed components in Karaf (I left out .xml camel > contexts for now. There are about 15 installed): > START LEVEL 100 , List Threshold: 50 > ID | State | Lvl | Version | Name > +--+-++- > 29 | Active | 80 | 4.1.4 | Apache Karaf :: OSGi Services :: Event > 67 | Active | 50 | 2.20.2 | camel-blueprint > 68 | Active | 80 | 2.20.2 | camel-commands-core > 69 | Active | 50 | 2.20.2 | camel-core > 70 | Active | 80 | 2.20.2 | camel-karaf-commands > 74 | Active | 50 | 1.6.0 | JavaMail API > 75 | Active | 50 | 2.20.2 | camel-mail > 76 | Active | 80 | 19.0.0 | Guava: Google Core Libraries for Java > 77 | Active | 80 | 4.1.16.Final | Netty/Buffer > 78 | Active | 80 | 4.1.16.Final | Netty/Codec > 79 | Active | 80 | 4.1.16.Final | Netty/Codec/HTTP > 80 | Active | 80 | 4.1.16.Final | Netty/Codec/MQTT > 81 | Active | 80 | 4.1.16.Final | Netty/Common > 82 | Active | 80 | 4.1.16.Final | Netty/Handler > 83 | Active | 80 | 4.1.16.Final | Netty/Resolver > 84 | Active | 80 | 4.1.16.Final | Netty/Transport > 85 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Epoll > 86 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/KQueue > 87 | Active | 80 | 4.1.16.Final | Netty/Transport/Native/Unix/Common > 89 | Active | 80 | 1.2.0 | CDI APIs > 90 | Active | 80 | 1.2 | javax.interceptor API > 91 | Active | 80 | 1.2 | javax.transaction API > 92 | Active | 80 | 2.4.0 | ActiveMQ Artemis AMQP Protocol > 93 | Active | 80 | 2.4.0 | ActiveMQ Artemis HornetQ Protocol > 94 | Active | 80 | 2.4.0 | ActiveMQ Artemis HQClient Protocol > 95 | Active | 80 | 2.4.0 | ActiveMQ Artemis MQTT Protocol > 96 | Active | 80 | 2.4.0 | ActiveMQ Artemis Native POM > 97 | Active | 80 | 2.4.0 | ActiveMQ Artemis OpenWire Protocol > 98 | Active | 80 | 2.4.0 | ActiveMQ Artemis Server OSGi > 99 | Active | 80 | 2.4.0 | ActiveMQ Artemis STOMP Protocol > 100 | Active | 80 | 1.1.1 | Apache Aries Transaction Blueprint > 101 | Active | 80 | 2.1.0 | Apache Aries Transaction Blueprint > 102 | Active | 80 | 1.3.3 | Apache Aries Transaction Manager > 103 | Active | 80 | 1.9.3 | Apache Commons BeanUtils > 104 | Active | 50 | 3.2.2 | Apache Commons Collections > 105 | Active | 80 | 1.0.2 | Apache Felix Coordinator Service > 108 | Active | 80 | 1.0.1 | geronimo-j2ee-management_1.1_spec > 109 | Active | 50 | 1.0.0.alpha-2 | Apache Geronimo JMS Spec 2.0 > 110 | Active | 80 | 0.9.5 | Johnzon :: Core > 114 | Active | 80 | 0.26.0 | QpidJMS Client > 115 | Active | 80 | 0.22.0 | Proton-J > 116 | Active | 80 | 1.0.0.2 | Apache ServiceMix :: Bundles :: javax.inject > 117 | Active | 80 | 2.9.0 | Apache ServiceMix :: Specs :: JSon API 1.1 > 118 | Active | 80 | 1.11.0 | hawtbuf > 119 | Active | 80 | 3.6.13.Final | JGroups > 120 | Active | 50 | 5.15.3 | activemq-karaf > 121 | Active | 50 | 2.6.7 | Jackson-annotations > 122 | Active | 50 | 2.6.7 | Jackson-core > 123 | Active | 50 | 2.6.7 | jackson-databind > 125 | Active | 50 | 2.9 | Joda-Time > 126 | Active | 50 | 3.1.4 | activeio-core > 127 | Active | 50 | 5.15.3 | activemq-osgi > 128 | Active | 50 | 1.9.0 | Apache Commons Codec > 129 | Active | 50 | 2.6 | Commons Lang > 130 | Active | 50 | 3.6.0 | Apache Commons Net > 131 | Active | 50 | 2.4.2 | Apache Commons Pool > 132 | Active | 80 | 3.1.1 | Geronimo TxManager :: Connector > 133 | Active | 80 | 1.0 | J2EE Connector 1.6 > 135 | Active | 80 | 1.1 | Apache Geronimo JSR-303 Bean Validation Spec API > 136 | Active | 50 | 3.4.6 | ZooKeeper Bundle > 139 | Active | 50 | 1.9.2.1 | Apache ServiceMix :: Bundles :: jasypt > 146 | Active | 50 | 1.7.0.6 | Apache ServiceMix :: Bundles :: velocity > 147 | Active | 50 | 1.1.0.4c_5 | Apache ServiceMix :: Bundles :: xpp3 > 148 | Active | 50 | 1.4.8.1 | Apache ServiceMix :: Bundles :: xstream > 151 | Active | 50 | 1.3.8 | jettison > 171 | Active | 50 | 0.6.4 | JAXB2 Basics - Runtime > 176 | Active | 50 | 2.11.0.v20140415-163722-cac6383e66 | Scala Standard > Library > 177 | Active | 50 | 2.20.2 | camel-jms > 178 | Active | 50 | 1.6.0 | Commons Pool > 181 | Active | 80 | 2.0.0 | hawtio :: hawtio-json-schema-mbean > 182 | Failure | 80 | 2.0.0 | hawtio :: Karaf terminal plugin > 183 | Active | 80 | 2.0.0 | hawtio :: hawtio-maven-indexer > 184 | Active |
[jira] [Commented] (CAMEL-12257) Possibility to disable quartz2 route during testing
[ https://issues.apache.org/jira/browse/CAMEL-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362370#comment-16362370 ] Claus Ibsen commented on CAMEL-12257: - Some tips You can turn off quartz to start its scheduler on the component You can tell Camel to not start any of the routes, and then you can start them manually You can use advice-with during test to change the input of routes to something else than quartz2 > Possibility to disable quartz2 route during testing > --- > > Key: CAMEL-12257 > URL: https://issues.apache.org/jira/browse/CAMEL-12257 > Project: Camel > Issue Type: Improvement > Components: camel-quartz2 >Affects Versions: 2.20.2 >Reporter: Kamil >Priority: Major > > While running integration tests, most of our components are mocked, but for > now there is no possibility to completly disable quartz2 routes. > My suggestion is to provide additional option "execute" which defaults to > "true", but we can set it to "false" in tests. If this option is set to false > - the route doesn't fire at all. > It could be also nice (as an additional feature) to disable firing quartz2 > routes CamelContext-wide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reopened CAMEL-12230:
--
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Sc
[jira] [Commented] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362369#comment-16362369
]
Andrea Cosentino commented on CAMEL-12230:
--
Reverted.
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concur
[jira] [Resolved] (CAMEL-12257) Possibility to disable quartz2 route during testing
[ https://issues.apache.org/jira/browse/CAMEL-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12257. - Resolution: Invalid Use the user mailing list, or places like gitter or stackoverflow to ask such questions and to get help with Camel. > Possibility to disable quartz2 route during testing > --- > > Key: CAMEL-12257 > URL: https://issues.apache.org/jira/browse/CAMEL-12257 > Project: Camel > Issue Type: Improvement > Components: camel-quartz2 >Affects Versions: 2.20.2 >Reporter: Kamil >Priority: Major > > While running integration tests, most of our components are mocked, but for > now there is no possibility to completly disable quartz2 routes. > My suggestion is to provide additional option "execute" which defaults to > "true", but we can set it to "false" in tests. If this option is set to false > - the route doesn't fire at all. > It could be also nice (as an additional feature) to disable firing quartz2 > routes CamelContext-wide -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-12230.
--
Resolution: Won't Fix
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$Schedul
[jira] [Updated] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-12230:
-
Fix Version/s: (was: 2.21.0)
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecuto
[jira] [Updated] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyubomir updated CAMEL-12262:
-
Description:
The [official
documentation|http://camel.apache.org/camel-configuration-utilities.html]
states the default cipher suites exclude filters are:
{code:java}
.*NULL.*
.*anon.*
.*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
.*EXPORT.* Camel 2.15.4
{code}
The default cipher suite exclude filter declared is:
{code:java}
/camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
{code}
{code:java}
protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
Collections.unmodifiableList(Arrays.asList(".*_NULL_.*", ".*_anon_.*",
".*_EXPORT_.*", ".*_DES_.*"));
{code}
According to the documentation 3DES will be excluded by default. Based on the
code only DES will be excluded.
was:
The official documentations states the default cipher suites exclude filters
are:
{code:java}
.*NULL.*
.*anon.*
.*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
.*EXPORT.* Camel 2.15.4
{code}
The default cipher suite exclude filter declared is:
{code:java}
/camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
{code}
{code:java}
protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
Collections.unmodifiableList(Arrays.asList(".*_NULL_.*", ".*_anon_.*",
".*_EXPORT_.*", ".*_DES_.*"));
{code}
According to the documentation 3DES will be excluded by default. Based on the
code only DES will be excluded.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-11941) Online xsd is not the latest 2.20 one
[ https://issues.apache.org/jira/browse/CAMEL-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362366#comment-16362366 ] Claus Ibsen commented on CAMEL-11941: - Yeah I think we need to ensure the highest released version of Camel has the online XSD updated. Gregor wonder if we need to get steps for this into the release guide http://camel.apache.org/release-guide.html > Online xsd is not the latest 2.20 one > - > > Key: CAMEL-11941 > URL: https://issues.apache.org/jira/browse/CAMEL-11941 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Assignee: Gregor Zurowski >Priority: Major > Fix For: 2.21.0 > > Attachments: screenshot-1.png > > > http://camel.apache.org/schema/spring/camel-spring.xsd is currently not the > 2.20.0 xsd > !screenshot-1.png! > based on last modification date it is the 2.18.3 one -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11941) Online xsd is not the latest 2.20 one
[ https://issues.apache.org/jira/browse/CAMEL-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11941: --- Assignee: Gregor Zurowski > Online xsd is not the latest 2.20 one > - > > Key: CAMEL-11941 > URL: https://issues.apache.org/jira/browse/CAMEL-11941 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Assignee: Gregor Zurowski >Priority: Major > Fix For: 2.21.0 > > Attachments: screenshot-1.png > > > http://camel.apache.org/schema/spring/camel-spring.xsd is currently not the > 2.20.0 xsd > !screenshot-1.png! > based on last modification date it is the 2.18.3 one -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12260) Default value for String field results in null for CSV / Bindy
[ https://issues.apache.org/jira/browse/CAMEL-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12260: Estimated Complexity: Novice (was: Unknown) > Default value for String field results in null for CSV / Bindy > -- > > Key: CAMEL-12260 > URL: https://issues.apache.org/jira/browse/CAMEL-12260 > Project: Camel > Issue Type: Bug > Components: camel-bindy >Affects Versions: 2.20.2 >Reporter: Pauli Borodulin >Priority: Minor > Fix For: 2.20.3, 2.21.0 > > > **CAMEL-5018 added "support the set the default value on the field of bindy > CVS", which is nice, but the default value is useless for Strings, because > BindyCSVFactory turns the empty value to null even when defaultValue = "", see > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230] > and > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12260) Default value for String field results in null for CSV / Bindy
[ https://issues.apache.org/jira/browse/CAMEL-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362363#comment-16362363 ] Claus Ibsen commented on CAMEL-12260: - Contributions is welcome http://camel.apache.org/contributing > Default value for String field results in null for CSV / Bindy > -- > > Key: CAMEL-12260 > URL: https://issues.apache.org/jira/browse/CAMEL-12260 > Project: Camel > Issue Type: Bug > Components: camel-bindy >Affects Versions: 2.20.2 >Reporter: Pauli Borodulin >Priority: Minor > Fix For: 2.20.3, 2.21.0 > > > **CAMEL-5018 added "support the set the default value on the field of bindy > CVS", which is nice, but the default value is useless for Strings, because > BindyCSVFactory turns the empty value to null even when defaultValue = "", see > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230] > and > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362365#comment-16362365
]
Claus Ibsen commented on CAMEL-12230:
-
Yeah if we cannot get camel-ribbon to work on OSGi we should not have a feature
for it - only what we have as karaf features are supported on OSGi
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Execu
[jira] [Updated] (CAMEL-12260) Default value for String field results in null for CSV / Bindy
[ https://issues.apache.org/jira/browse/CAMEL-12260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12260: Fix Version/s: 2.21.0 2.20.3 > Default value for String field results in null for CSV / Bindy > -- > > Key: CAMEL-12260 > URL: https://issues.apache.org/jira/browse/CAMEL-12260 > Project: Camel > Issue Type: Bug > Components: camel-bindy >Affects Versions: 2.20.2 >Reporter: Pauli Borodulin >Priority: Minor > Fix For: 2.20.3, 2.21.0 > > > **CAMEL-5018 added "support the set the default value on the field of bindy > CVS", which is nice, but the default value is useless for Strings, because > BindyCSVFactory turns the empty value to null even when defaultValue = "", see > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230] > and > [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12262:
Issue Type: Task (was: Bug)
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Major
>
> The official documentations states the default cipher suites exclude filters
> are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12262:
Component/s: (was: camel-core)
documentation
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The official documentations states the default cipher suites exclude filters
> are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362362#comment-16362362
]
Claus Ibsen commented on CAMEL-12262:
-
Can you add the link to the documentation where its present
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The official documentations states the default cipher suites exclude filters
> are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12262:
Priority: Minor (was: Major)
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Priority: Minor
>
> The official documentations states the default cipher suites exclude filters
> are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE
Lyubomir created CAMEL-12262:
Summary: DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE
Key: CAMEL-12262
URL: https://issues.apache.org/jira/browse/CAMEL-12262
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Lyubomir
The official documentations states the default cipher suites exclude filters
are:
{code:java}
.*NULL.*
.*anon.*
.*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
.*EXPORT.* Camel 2.15.4
{code}
The default cipher suite exclude filter declared is:
{code:java}
/camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
{code}
{code:java}
protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
Collections.unmodifiableList(Arrays.asList(".*_NULL_.*", ".*_anon_.*",
".*_EXPORT_.*", ".*_DES_.*"));
{code}
According to the documentation 3DES will be excluded by default. Based on the
code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lyubomir updated CAMEL-12262:
-
Summary: DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect (was:
DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE )
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Lyubomir
>Priority: Major
>
> The official documentations states the default cipher suites exclude filters
> are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12261) Camel-AWS KMS: Add a scheduleKeyDeletion operation
[ https://issues.apache.org/jira/browse/CAMEL-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12261. -- Resolution: Fixed > Camel-AWS KMS: Add a scheduleKeyDeletion operation > -- > > Key: CAMEL-12261 > URL: https://issues.apache.org/jira/browse/CAMEL-12261 > Project: Camel > Issue Type: Task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 2.21.0 > > > Actually we are unable to delete a KMS key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12261) Camel-AWS KMS: Add a scheduleKeyDeletion operation
Andrea Cosentino created CAMEL-12261: Summary: Camel-AWS KMS: Add a scheduleKeyDeletion operation Key: CAMEL-12261 URL: https://issues.apache.org/jira/browse/CAMEL-12261 Project: Camel Issue Type: Task Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 2.21.0 Actually we are unable to delete a KMS key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12260) Default value for String field results in null for CSV / Bindy
Pauli Borodulin created CAMEL-12260: --- Summary: Default value for String field results in null for CSV / Bindy Key: CAMEL-12260 URL: https://issues.apache.org/jira/browse/CAMEL-12260 Project: Camel Issue Type: Bug Components: camel-bindy Affects Versions: 2.20.2 Reporter: Pauli Borodulin **CAMEL-5018 added "support the set the default value on the field of bindy CVS", which is nice, but the default value is useless for Strings, because BindyCSVFactory turns the empty value to null even when defaultValue = "", see [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyCsvFactory.java#L230] and [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/BindyAbstractFactory.java#L234] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362121#comment-16362121
]
Andrea Cosentino commented on CAMEL-12230:
--
Do we need to remove the feature [~davsclaus] ?
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true&delay=0&period=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.Futu
[jira] [Commented] (CAMEL-12240) Create a real tests with Apache Qpid Broker-J
[ https://issues.apache.org/jira/browse/CAMEL-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362112#comment-16362112 ] ASF GitHub Bot commented on CAMEL-12240: Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/ > Create a real tests with Apache Qpid Broker-J > - > > Key: CAMEL-12240 > URL: https://issues.apache.org/jira/browse/CAMEL-12240 > Project: Camel > Issue Type: Sub-task > Components: camel-rabbitmq >Affects Versions: 2.21.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.21.0 > > > As unable to run integration tests for camel-rabbitmq component with live > RabbitMQ server and it's very difficult to diagnose issues like CAMEL-12229 > and others. > It's a task for cover some tests with live AMQP 0.9.1 (supports in RabbitMQ) > server based on Apache Qpid Broker-J. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12240) Create a real tests with Apache Qpid Broker-J
[ https://issues.apache.org/jira/browse/CAMEL-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12240. -- Resolution: Fixed > Create a real tests with Apache Qpid Broker-J > - > > Key: CAMEL-12240 > URL: https://issues.apache.org/jira/browse/CAMEL-12240 > Project: Camel > Issue Type: Sub-task > Components: camel-rabbitmq >Affects Versions: 2.21.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.21.0 > > > As unable to run integration tests for camel-rabbitmq component with live > RabbitMQ server and it's very difficult to diagnose issues like CAMEL-12229 > and others. > It's a task for cover some tests with live AMQP 0.9.1 (supports in RabbitMQ) > server based on Apache Qpid Broker-J. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12240) Create a real tests with Apache Qpid Broker-J
[ https://issues.apache.org/jira/browse/CAMEL-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362111#comment-16362111 ] ASF GitHub Bot commented on CAMEL-12240: oscerd commented on issue #: CAMEL-12240: Create a real tests with Apache Qpid Broker-J URL: https://github.com/apache/camel/pull/#issuecomment-365222414 Thanks a lot :-) Merged on master. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Create a real tests with Apache Qpid Broker-J > - > > Key: CAMEL-12240 > URL: https://issues.apache.org/jira/browse/CAMEL-12240 > Project: Camel > Issue Type: Sub-task > Components: camel-rabbitmq >Affects Versions: 2.21.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Minor > Fix For: 2.21.0 > > > As unable to run integration tests for camel-rabbitmq component with live > RabbitMQ server and it's very difficult to diagnose issues like CAMEL-12229 > and others. > It's a task for cover some tests with live AMQP 0.9.1 (supports in RabbitMQ) > server based on Apache Qpid Broker-J. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-5469) CxfRsProducer is not thread safe
[
https://issues.apache.org/jira/browse/CAMEL-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362063#comment-16362063
]
Alex Furmanski commented on CAMEL-5469:
---
FYI I have encountered this exception in Camel 2.15
{noformat}
java.util.concurrent.ExecutionException:
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[Message: hello world]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at com.example.ConcurrencyTest.testConcurrently(ConcurrencyTest.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: org.apache.camel.CamelExecutionException: Exception occurred during
execution on the exchange: Exchange[Message: hello world]
at
org.apache.camel.util.ObjectHelper.wrapCamelExecutionException(ObjectHelper.java:1635)
at
org.apache.camel.util.ExchangeHelper.extractResultBody(ExchangeHelper.java:645)
at
org.apache.camel.impl.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:471)
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:133)
at
org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:149)
at com.example.ConcurrencyTest.test(ConcurrencyTest.java:25)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: java.util.ConcurrentModificationException
at
org.apache.cxf.jaxrs.client.JAXRSClientFactoryBean.createWebClient(JAXRSClientFactoryBean.java:233)
at
org.apache.camel.component.cxf.jaxrs.CxfRsProducer.invokeHttpClient(CxfRsProduce
[jira] [Commented] (CAMEL-11941) Online xsd is not the latest 2.20 one
[ https://issues.apache.org/jira/browse/CAMEL-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362013#comment-16362013 ] Andrea Cosentino commented on CAMEL-11941: -- [~gzurowski] If you have a chance can you take a look? Thanks. > Online xsd is not the latest 2.20 one > - > > Key: CAMEL-11941 > URL: https://issues.apache.org/jira/browse/CAMEL-11941 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Major > Fix For: 2.21.0 > > Attachments: screenshot-1.png > > > http://camel.apache.org/schema/spring/camel-spring.xsd is currently not the > 2.20.0 xsd > !screenshot-1.png! > based on last modification date it is the 2.18.3 one -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11941) Online xsd is not the latest 2.20 one
[ https://issues.apache.org/jira/browse/CAMEL-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361991#comment-16361991 ] Aurélien Pupier commented on CAMEL-11941: - the online xsd is now 11 versions older than the current one. Is it possible to update it please? > Online xsd is not the latest 2.20 one > - > > Key: CAMEL-11941 > URL: https://issues.apache.org/jira/browse/CAMEL-11941 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Major > Fix For: 2.21.0 > > Attachments: screenshot-1.png > > > http://camel.apache.org/schema/spring/camel-spring.xsd is currently not the > 2.20.0 xsd > !screenshot-1.png! > based on last modification date it is the 2.18.3 one -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-11941) Online xsd is not the latest 2.20 one
[ https://issues.apache.org/jira/browse/CAMEL-11941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361991#comment-16361991 ] Aurélien Pupier edited comment on CAMEL-11941 at 2/13/18 8:42 AM: -- the online xsd is now 11 versions older than the latest one. Is it possible to update it please? was (Author: apupier): the online xsd is now 11 versions older than the current one. Is it possible to update it please? > Online xsd is not the latest 2.20 one > - > > Key: CAMEL-11941 > URL: https://issues.apache.org/jira/browse/CAMEL-11941 > Project: Camel > Issue Type: Task > Components: website >Reporter: Aurélien Pupier >Priority: Major > Fix For: 2.21.0 > > Attachments: screenshot-1.png > > > http://camel.apache.org/schema/spring/camel-spring.xsd is currently not the > 2.20.0 xsd > !screenshot-1.png! > based on last modification date it is the 2.18.3 one -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12256) AWS S3 Consumer does not return custom headers in S3 Headers
[ https://issues.apache.org/jira/browse/CAMEL-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361978#comment-16361978 ] Andrea Cosentino commented on CAMEL-12256: -- We released 2.20.2 in the last months, so I believe a couple of months or less. > AWS S3 Consumer does not return custom headers in S3 Headers > > > Key: CAMEL-12256 > URL: https://issues.apache.org/jira/browse/CAMEL-12256 > Project: Camel > Issue Type: Bug > Components: camel-aws >Affects Versions: 2.19.2, 2.20.1 >Reporter: Noel Vinod Aranha >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 2.19.5, 2.20.3, 2.21.0 > > > We can add custom user given metadata in AWS S3 as part of S3Headers in S3 > Producer. However, the same user provided meta data cannot be retrieved via > S3 Consumer. > Amazon SDK S3 Object provides two types of meta data: > 1) Raw Meta Data > 2) User Meta Data > In S3Endpoint.java, you can either set User Meta Data instead of Raw Meta > Data for S3 Headers or provide another key like S3UserMetaData and provide > this User Meta Data as value for that key. > Currently, there seems to be no way to access this User provided custom > headers using Camel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
