[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13621:
Fix Version/s: 3.0.0
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13621:
Component/s: camel-core
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13621:
Estimated Complexity: Moderate (was: Unknown)
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861759#comment-16861759
]
Claus Ibsen commented on CAMEL-13621:
-
Also for key values it should not quote the masked password, eg it should not
be "" but just "
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861758#comment-16861758
]
Claus Ibsen commented on CAMEL-13621:
-
I really dislike complex regular exp pattern and sadly the
DefaultMaskingFormatter has those
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861756#comment-16861756
]
Claus Ibsen commented on CAMEL-13621:
-
Okay have reproduced it with your 2nd little unit test. This only happens if
you turn on logMask. And yeah its complex when its regular exp patterns.
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13038) Type Convert Problem for XQuery Build In founction
[
https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13038:
Priority: Minor (was: Major)
> Type Convert Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Minor
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:79)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
> [jetty-server-9.4.11.v20180605.jar!/:9.4.11.v20180605]
>
[jira] [Commented] (CAMEL-13369) enhance message history eip
[
https://issues.apache.org/jira/browse/CAMEL-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861754#comment-16861754
]
Claus Ibsen commented on CAMEL-13369:
-
You can now filter to only do this for step eips etc
context.setMessageHistory(true);
context.getMessageHistoryFactory().setNodePattern("step");
> enhance message history eip
>
>
> Key: CAMEL-13369
> URL: https://issues.apache.org/jira/browse/CAMEL-13369
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
>Reporter: Luca Burgazzoli
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> The current message history eip is somehow limited as we cannot choose which
> nodes we want to take into account, as example if one creates routes using
> the new Step EIP, he may want to get the history to track step related
> activities only.
> Another additional feature would be to have the message history pattern to
> keep a copy of the message being produced by the processor under monitor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13369) enhance message history eip
[ https://issues.apache.org/jira/browse/CAMEL-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13369. - Resolution: Fixed > enhance message history eip > > > Key: CAMEL-13369 > URL: https://issues.apache.org/jira/browse/CAMEL-13369 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0.M4 > > > The current message history eip is somehow limited as we cannot choose which > nodes we want to take into account, as example if one creates routes using > the new Step EIP, he may want to get the history to track step related > activities only. > Another additional feature would be to have the message history pattern to > keep a copy of the message being produced by the processor under monitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13038) Type Convert Problem for XQuery Build In founction
[
https://issues.apache.org/jira/browse/CAMEL-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861364#comment-16861364
]
Freeman Fang commented on CAMEL-13038:
--
Hi [~W.Y],
I think in your testcase, in the
src/main/resources/xquerytemplate/xqueryfile.xq
you should simply use
{code}
declare variable $in.body as xs:string external;
let $codetableRequest :=parse-xml($in.body)/*
{code}
instead of
{code}
declare variable $in.body as element() external;
let $codetableRequest :=$in.body
{code}
It works for me with this change.
Cheers
Freeman
> Type Convert Problem for XQuery Build In founction
> --
>
> Key: CAMEL-13038
> URL: https://issues.apache.org/jira/browse/CAMEL-13038
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 2.22.2
>Reporter: W.Y
>Priority: Major
> Attachments: xquerytest.zip
>
>
> when we send XML message to XQuery endpoint, it has problem with XML parsing
> Im XQuery the build in function looks like below :
> declare variable $in.body as element(*) external;
> return xf:my_xquery_function($request)
>
> the exception we got looks like
>
> org.apache.camel.RuntimeExpressionException:
> net.sf.saxon.trans.XPathException: Required item type of value of variable
> $in.body is element(); supplied value has item type
> Q{http://saxon.sf.net/java-t
> ype}org.apache.camel.converter.stream.CachedOutputStream-WrappedInputStream
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:155)
> ~[classes!/:na]
> at
> org.apache.camel.component.xquery.XQueryBuilder.evaluate(XQueryBuilder.java:120)
> ~[classes!/:na]
> at
> org.apache.camel.processor.TransformProcessor.process(TransformProcessor.java:50)
> ~[camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> [camel-core-2.22.1.jar!/:2.22.1]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> [camel-core-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:185)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:161)
> [camel-cxf-2.22.1.jar!/:2.22.1]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_121]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_121]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$2.run(ServiceInvokerInterceptor.java:126)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:131)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> [cxf-core-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267)
> [cxf-rt-transports-http-3.2.5.jar!/:3.2.5]
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:247)
> [cxf-rt-transports-http-jetty-3.2.5.jar!/:3.2.5]
> at
>
[jira] [Assigned] (CAMEL-13369) enhance message history eip
[ https://issues.apache.org/jira/browse/CAMEL-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13369: --- Assignee: Claus Ibsen > enhance message history eip > > > Key: CAMEL-13369 > URL: https://issues.apache.org/jira/browse/CAMEL-13369 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0.M4 > > > The current message history eip is somehow limited as we cannot choose which > nodes we want to take into account, as example if one creates routes using > the new Step EIP, he may want to get the history to track step related > activities only. > Another additional feature would be to have the message history pattern to > keep a copy of the message being produced by the processor under monitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13633) AuthenticationFailedException is not propagated to onException route
[
https://issues.apache.org/jira/browse/CAMEL-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13633.
--
Resolution: Not A Problem
> AuthenticationFailedException is not propagated to onException route
>
>
> Key: CAMEL-13633
> URL: https://issues.apache.org/jira/browse/CAMEL-13633
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Major
>
> If imaps Compotent throws:
>
> {code:java}
> javax.mail.AuthenticationFailedException: [AUTHENTICATIONFAILED] Invalid
> credentials (Failure)
> at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:732)
> at javax.mail.Service.connect(Service.java:388)
> at
> org.apache.camel.component.mail.MailConsumer.ensureIsConnected(MailConsumer.java:521)
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:95)
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 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)
> {code}
>
> It is not propagated to onException Route.
> Test case:
> {code:java}
> import javax.mail.AuthenticationFailedException;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.Processor;
> import org.apache.camel.Produce;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.RoutesBuilder;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.http.client.utils.URIBuilder;
> import org.junit.Test;
> public class EmailRouteTest extends CamelTestSupport {
> private static final String STATIC_ROUTE_FROM = "direct:email";
> @EndpointInject(uri = "mock:error")
> private MockEndpoint mockErrorEndpoint;
> @Produce(uri = STATIC_ROUTE_FROM)
> private ProducerTemplate sender;
> @Override
> protected RoutesBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> final String routeUri = new URIBuilder()
> .setScheme("imaps")
> .setHost("imap.gmail.com")
> .setPort(993)
> .addParameter("username", "foobar")
> .addParameter("password", "foobar")
> .addParameter("debugMode", "false")
> .addParameter("delete", "false")
> .addParameter("unseen", "true")
> .addParameter("consumer.delay", "6")
> .toString();
> onException(Exception.class)
> .handled(true)
> .to(mockErrorEndpoint);
> from(routeUri)
> .to("stream:out");
> }
> };
> }
> @Test
> public void shouldInterceptError() throws Exception {
> mockErrorEndpoint.expectedMessageCount(1);
> mockErrorEndpoint.expectedMessagesMatches(ex ->
> ex.getProperty(Exchange.EXCEPTION_CAUGHT).getClass().equals(AuthenticationFailedException.class));
> mockErrorEndpoint.assertIsSatisfied();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13633) AuthenticationFailedException is not propagated to onException route
[
https://issues.apache.org/jira/browse/CAMEL-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861109#comment-16861109
]
Jan Bednar commented on CAMEL-13633:
This is correct. onException is intended to handle exceptions during Exchange
processing. This exception occured during consumer initialization. You need
custom {{ExceptionHandler}} for this. See
[https://stackoverflow.com/questions/31185913/handle-apache-camel-consumer-errors]
. Please next time consider asking on mailing list, before filling bug.
> AuthenticationFailedException is not propagated to onException route
>
>
> Key: CAMEL-13633
> URL: https://issues.apache.org/jira/browse/CAMEL-13633
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 2.24.0
>Reporter: Kamil
>Priority: Major
>
> If imaps Compotent throws:
>
> {code:java}
> javax.mail.AuthenticationFailedException: [AUTHENTICATIONFAILED] Invalid
> credentials (Failure)
> at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:732)
> at javax.mail.Service.connect(Service.java:388)
> at
> org.apache.camel.component.mail.MailConsumer.ensureIsConnected(MailConsumer.java:521)
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:95)
> at
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
> at
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 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)
> {code}
>
> It is not propagated to onException Route.
> Test case:
> {code:java}
> import javax.mail.AuthenticationFailedException;
> import org.apache.camel.EndpointInject;
> import org.apache.camel.Exchange;
> import org.apache.camel.Processor;
> import org.apache.camel.Produce;
> import org.apache.camel.ProducerTemplate;
> import org.apache.camel.RoutesBuilder;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.component.mock.MockEndpoint;
> import org.apache.camel.test.junit4.CamelTestSupport;
> import org.apache.http.client.utils.URIBuilder;
> import org.junit.Test;
> public class EmailRouteTest extends CamelTestSupport {
> private static final String STATIC_ROUTE_FROM = "direct:email";
> @EndpointInject(uri = "mock:error")
> private MockEndpoint mockErrorEndpoint;
> @Produce(uri = STATIC_ROUTE_FROM)
> private ProducerTemplate sender;
> @Override
> protected RoutesBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> final String routeUri = new URIBuilder()
> .setScheme("imaps")
> .setHost("imap.gmail.com")
> .setPort(993)
> .addParameter("username", "foobar")
> .addParameter("password", "foobar")
> .addParameter("debugMode", "false")
> .addParameter("delete", "false")
> .addParameter("unseen", "true")
> .addParameter("consumer.delay", "6")
> .toString();
> onException(Exception.class)
> .handled(true)
> .to(mockErrorEndpoint);
> from(routeUri)
> .to("stream:out");
> }
> };
> }
> @Test
> public void shouldInterceptError() throws Exception {
> mockErrorEndpoint.expectedMessageCount(1);
> mockErrorEndpoint.expectedMessagesMatches(ex ->
> ex.getProperty(Exchange.EXCEPTION_CAUGHT).getClass().equals(AuthenticationFailedException.class));
> mockErrorEndpoint.assertIsSatisfied();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13633) AuthenticationFailedException is not propagated to onException route
Kamil created CAMEL-13633:
-
Summary: AuthenticationFailedException is not propagated to
onException route
Key: CAMEL-13633
URL: https://issues.apache.org/jira/browse/CAMEL-13633
Project: Camel
Issue Type: Bug
Components: camel-mail
Affects Versions: 2.24.0
Reporter: Kamil
If imaps Compotent throws:
{code:java}
javax.mail.AuthenticationFailedException: [AUTHENTICATIONFAILED] Invalid
credentials (Failure)
at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:732)
at javax.mail.Service.connect(Service.java:388)
at
org.apache.camel.component.mail.MailConsumer.ensureIsConnected(MailConsumer.java:521)
at
org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:95)
at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
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)
{code}
It is not propagated to onException Route.
Test case:
{code:java}
import javax.mail.AuthenticationFailedException;
import org.apache.camel.EndpointInject;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.apache.camel.Produce;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.RoutesBuilder;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.component.mock.MockEndpoint;
import org.apache.camel.test.junit4.CamelTestSupport;
import org.apache.http.client.utils.URIBuilder;
import org.junit.Test;
public class EmailRouteTest extends CamelTestSupport {
private static final String STATIC_ROUTE_FROM = "direct:email";
@EndpointInject(uri = "mock:error")
private MockEndpoint mockErrorEndpoint;
@Produce(uri = STATIC_ROUTE_FROM)
private ProducerTemplate sender;
@Override
protected RoutesBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
final String routeUri = new URIBuilder()
.setScheme("imaps")
.setHost("imap.gmail.com")
.setPort(993)
.addParameter("username", "foobar")
.addParameter("password", "foobar")
.addParameter("debugMode", "false")
.addParameter("delete", "false")
.addParameter("unseen", "true")
.addParameter("consumer.delay", "6")
.toString();
onException(Exception.class)
.handled(true)
.to(mockErrorEndpoint);
from(routeUri)
.to("stream:out");
}
};
}
@Test
public void shouldInterceptError() throws Exception {
mockErrorEndpoint.expectedMessageCount(1);
mockErrorEndpoint.expectedMessagesMatches(ex ->
ex.getProperty(Exchange.EXCEPTION_CAUGHT).getClass().equals(AuthenticationFailedException.class));
mockErrorEndpoint.assertIsSatisfied();
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13563: Fix Version/s: (was: 2.24.1) (was: 2.23.3) 2.25.0 > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861040#comment-16861040 ] Andrea Cosentino commented on CAMEL-13563: -- I mean only 2.x > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861039#comment-16861039 ] Colm O hEigeartaigh commented on CAMEL-13563: - [~acosentino] By "I think it's safe to do this on 2.x" - do you mean only camel-2.x branch, or also for 2.24.1 + 2.23.3? > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13369) enhance message history eip
[ https://issues.apache.org/jira/browse/CAMEL-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13369: Fix Version/s: 3.0.0.M4 > enhance message history eip > > > Key: CAMEL-13369 > URL: https://issues.apache.org/jira/browse/CAMEL-13369 > Project: Camel > Issue Type: New Feature > Components: camel-core, eip >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0, 3.0.0.M4 > > > The current message history eip is somehow limited as we cannot choose which > nodes we want to take into account, as example if one creates routes using > the new Step EIP, he may want to get the history to track step related > activities only. > Another additional feature would be to have the message history pattern to > keep a copy of the message being produced by the processor under monitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13627) camel-main - Reuse options for main and camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13627. - Resolution: Fixed Fix Version/s: 3.0.0 Okay there is now a org.apache.camel.main.DefaultConfigurationConfigurer which should be used > camel-main - Reuse options for main and camel-spring-boot > - > > Key: CAMEL-13627 > URL: https://issues.apache.org/jira/browse/CAMEL-13627 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861008#comment-16861008 ] Andrea Cosentino commented on CAMEL-13563: -- I think it's safe to do this on 2.x, but I'd take care of Karaf integration tests and Spring Boot integration tests > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861006#comment-16861006 ] Colm O hEigeartaigh commented on CAMEL-13563: - [~acosentino] I think the Jetty upgrade could be backported to the camel-2.x branch. Then I can merge the fixes that relate to client authentication only back to the older branches. WDYT? > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860992#comment-16860992 ] Andrea Cosentino commented on CAMEL-13563: -- done on Camel 3, not sure this can be done on 2.x > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?focusedWorklogId=257661=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-257661 ] ASF GitHub Bot logged work on CAMEL-13563: -- Author: ASF GitHub Bot Created on: 11/Jun/19 12:26 Start Date: 11/Jun/19 12:26 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #2971: CAMEL-13563 - Update Jetty to 9.4.18 + fix client authentication issues URL: https://github.com/apache/camel/pull/2971 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 257661) Time Spent: 20m (was: 10m) > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Giera updated CAMEL-13621:
Environment:
Camel 2.20.2
Oracle JDK 8u121/OpenJDK 11.0.3
was:
Camel 2.20.2
Oracle JDK 8u121
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121/OpenJDK 11.0.3
>
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13407) CouchDbChangesetTracker fails silently on network error and does not recover
[ https://issues.apache.org/jira/browse/CAMEL-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860808#comment-16860808 ] Andrea Cosentino commented on CAMEL-13407: -- We can try to backport on 2.x and 2.24.x and 2.23.x (available for 2.23.4) > CouchDbChangesetTracker fails silently on network error and does not recover > > > Key: CAMEL-13407 > URL: https://issues.apache.org/jira/browse/CAMEL-13407 > Project: Camel > Issue Type: Bug > Components: camel-couchdb >Affects Versions: 2.21.5 >Reporter: Simon Temple >Assignee: Ramu >Priority: Major > Fix For: 3.0.0 > > Attachments: CouchDbChangesetTracker.java, > CouchDbChangesetTrackerTest.java > > Original Estimate: 4h > Remaining Estimate: 4h > > We ran into this in production when a network error made the CouchDB instance > unavailable for a short while. > We were running with camel 2.18.1 so I patched a local copy of the component; > which has been running without problems for many weeks now. > I'd like to propose our code as the fix to this. > We're now running with 2.23.1 so would be looking for a 2.x fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860799#comment-16860799
]
Christoph Giera commented on CAMEL-13621:
-
It's not so easy to show or explain the StackOverflowError, I've attached 2
screenshots which are the results of the same test(FormatTest.java). Executing
this test results in ~50% errors(see ExecuteTest_2.PNG) and ~50% success(see
ExecuteTest_1.PNG). This is really weird because it's the same test. Maybe it
has something to do with [https://bugs.openjdk.java.net/browse/JDK-6328855] but
I'm not sure.
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Giera updated CAMEL-13621:
Attachment: ExecuteTest_1.PNG
ExecuteTest_2.PNG
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: ExecuteTest_1.PNG, ExecuteTest_2.PNG, FormatTest.java,
> FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13632) Deprecate and remove ReloadStrategy
[ https://issues.apache.org/jira/browse/CAMEL-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13632. - Resolution: Fixed Fix Version/s: 3.0.0 Deprecated on 2.x branches > Deprecate and remove ReloadStrategy > --- > > Key: CAMEL-13632 > URL: https://issues.apache.org/jira/browse/CAMEL-13632 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > This should be deprecated in camel 2.x and removed in 3.0. > This makes the modularization of camel 3 better, and its also only used as a > developer/demo thing and not for production usage. And today there are better > alternatives with camel k, and camel-quarkus etc, for hot re-load that can > load the entire app and not only a xml route. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-7779) Endpoint URI builder for Java RouteBuilder DSL
[ https://issues.apache.org/jira/browse/CAMEL-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7779: --- Fix Version/s: (was: Future) > Endpoint URI builder for Java RouteBuilder DSL > -- > > Key: CAMEL-7779 > URL: https://issues.apache.org/jira/browse/CAMEL-7779 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Serge Smertin >Priority: Minor > Fix For: 3.0.0 > > > Sometimes we may want to add configuration into our RouteBuilders on endpoint > parameters like number of concurrent consumers or types of some exchanges. I > guess it might be pretty useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-7779) Endpoint URI builder for Java RouteBuilder DSL
[ https://issues.apache.org/jira/browse/CAMEL-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-7779: -- Assignee: Guillaume Nodet > Endpoint URI builder for Java RouteBuilder DSL > -- > > Key: CAMEL-7779 > URL: https://issues.apache.org/jira/browse/CAMEL-7779 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Serge Smertin >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 3.0.0 > > > Sometimes we may want to add configuration into our RouteBuilders on endpoint > parameters like number of concurrent consumers or types of some exchanges. I > guess it might be pretty useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-7779) Endpoint URI builder for Java RouteBuilder DSL
[ https://issues.apache.org/jira/browse/CAMEL-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-7779: --- Issue Type: New Feature (was: Improvement) > Endpoint URI builder for Java RouteBuilder DSL > -- > > Key: CAMEL-7779 > URL: https://issues.apache.org/jira/browse/CAMEL-7779 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Serge Smertin >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 3.0.0 > > > Sometimes we may want to add configuration into our RouteBuilders on endpoint > parameters like number of concurrent consumers or types of some exchanges. I > guess it might be pretty useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13314) Add a fluent DSL for components and endpoints
[
https://issues.apache.org/jira/browse/CAMEL-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13314:
---
Assignee: Guillaume Nodet
> Add a fluent DSL for components and endpoints
> -
>
> Key: CAMEL-13314
> URL: https://issues.apache.org/jira/browse/CAMEL-13314
> Project: Camel
> Issue Type: New Feature
>Reporter: Andrea Cosentino
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0
>
>
> It would be good to have a fluent DSL to build component and endpoint
> instances. Something like:
> {code:java}
> jms().withConnectionFactory(connectionFactory)...build();{code}
> We can collect ideas here.
> We can generate code from the catalog.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13631) PropertyBindingSupport to support key filtering and transformation
[
https://issues.apache.org/jira/browse/CAMEL-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli resolved CAMEL-13631.
-
Resolution: Fixed
> PropertyBindingSupport to support key filtering and transformation
> --
>
> Key: CAMEL-13631
> URL: https://issues.apache.org/jira/browse/CAMEL-13631
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0.M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is common that you want to filter out or transform properties before they
> are applied to a target, for example you may want to filter out by prefix and
> in camel-k we do something like that:
> {code}
> public static int bindProperties(CamelContext context, Properties properties,
> Object target, String prefix) {
> final AtomicInteger count = new AtomicInteger();
> properties.entrySet().stream()
> .filter(entry -> entry.getKey() instanceof String)
> .filter(entry -> entry.getValue() != null)
> .filter(entry -> ((String)entry.getKey()).startsWith(prefix))
> .forEach(entry -> {
> final String key =
> ((String)entry.getKey()).substring(prefix.length());
> final Object val = entry.getValue();
> try {
> if (PropertyBindingSupport.bindProperty(context,
> target, key, val)) {
> count.incrementAndGet();
> }
> } catch (Exception ex) {
> throw new RuntimeException(ex);
> }
> }
> );
> return count.get();
> }
> {code}
> Would be nice to have a support for filtering out of the box
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13631) PropertyBindingSupport to support key filtering and transformation
[
https://issues.apache.org/jira/browse/CAMEL-13631?focusedWorklogId=257577=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-257577
]
ASF GitHub Bot logged work on CAMEL-13631:
--
Author: ASF GitHub Bot
Created on: 11/Jun/19 10:09
Start Date: 11/Jun/19 10:09
Worklog Time Spent: 10m
Work Description: lburgazzoli commented on pull request #2970:
CAMEL-13631: PropertyBindingSupport to support key filtering and transformation
URL: https://github.com/apache/camel/pull/2970
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 257577)
Time Spent: 10m
Remaining Estimate: 0h
> PropertyBindingSupport to support key filtering and transformation
> --
>
> Key: CAMEL-13631
> URL: https://issues.apache.org/jira/browse/CAMEL-13631
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0.M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is common that you want to filter out or transform properties before they
> are applied to a target, for example you may want to filter out by prefix and
> in camel-k we do something like that:
> {code}
> public static int bindProperties(CamelContext context, Properties properties,
> Object target, String prefix) {
> final AtomicInteger count = new AtomicInteger();
> properties.entrySet().stream()
> .filter(entry -> entry.getKey() instanceof String)
> .filter(entry -> entry.getValue() != null)
> .filter(entry -> ((String)entry.getKey()).startsWith(prefix))
> .forEach(entry -> {
> final String key =
> ((String)entry.getKey()).substring(prefix.length());
> final Object val = entry.getValue();
> try {
> if (PropertyBindingSupport.bindProperty(context,
> target, key, val)) {
> count.incrementAndGet();
> }
> } catch (Exception ex) {
> throw new RuntimeException(ex);
> }
> }
> );
> return count.get();
> }
> {code}
> Would be nice to have a support for filtering out of the box
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-8362) Camel Components - Generate per component Java fluent builder
[
https://issues.apache.org/jira/browse/CAMEL-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned CAMEL-8362:
--
Assignee: Guillaume Nodet
> Camel Components - Generate per component Java fluent builder
> -
>
> Key: CAMEL-8362
> URL: https://issues.apache.org/jira/browse/CAMEL-8362
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Reporter: Claus Ibsen
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0
>
>
> Similar to CAMEL-8361, but for generating java source code fluent builder, so
> people can configured components and endpoints in a nicer style.
> {code}
> Endpoint file =
> FileEndpointBuilder.directory("somepath").recursive(true).includes("*.txt").build();
> ...
> {code}
> Though there is a few tasks to figure out.
> We would need some template as skeleton for generating the source code. And
> we would need a naming convention for the class name. And also we should
> allow each builder method to have 2 options. As its original type, eg String,
> boolean, int, etc. And then an alternative that uses a String so people can
> use property placeholders, eg "{{foo}}".
> And besides endpoints we should also generate for components as well, so its
> easier to configure them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-8362) Camel Components - Generate per component Java fluent builder
[
https://issues.apache.org/jira/browse/CAMEL-8362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated CAMEL-8362:
---
Fix Version/s: 3.0.0.M4
> Camel Components - Generate per component Java fluent builder
> -
>
> Key: CAMEL-8362
> URL: https://issues.apache.org/jira/browse/CAMEL-8362
> Project: Camel
> Issue Type: New Feature
> Components: tooling
>Reporter: Claus Ibsen
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
>
> Similar to CAMEL-8361, but for generating java source code fluent builder, so
> people can configured components and endpoints in a nicer style.
> {code}
> Endpoint file =
> FileEndpointBuilder.directory("somepath").recursive(true).includes("*.txt").build();
> ...
> {code}
> Though there is a few tasks to figure out.
> We would need some template as skeleton for generating the source code. And
> we would need a naming convention for the class name. And also we should
> allow each builder method to have 2 options. As its original type, eg String,
> boolean, int, etc. And then an alternative that uses a String so people can
> use property placeholders, eg "{{foo}}".
> And besides endpoints we should also generate for components as well, so its
> easier to configure them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?focusedWorklogId=257530=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-257530 ] ASF GitHub Bot logged work on CAMEL-13563: -- Author: ASF GitHub Bot Created on: 11/Jun/19 08:51 Start Date: 11/Jun/19 08:51 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #2971: CAMEL-13563 - Update Jetty to 9.4.18 + fix client authentication issues URL: https://github.com/apache/camel/pull/2971 I fixed the issues that were previously reported about failing itests - all of the Karaf itests now pass. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 257530) Time Spent: 10m Remaining Estimate: 0h > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 10m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860619#comment-16860619
]
Christoph Giera commented on CAMEL-13621:
-
Added FormatUriTest.java. The DefaultMaskingFormatter is used in the log
component and also provides options for json and xml formatting. So I assumed
that multiline strings should not be a problem at all. E.g. a pretty printed
xml contains line breaks.
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: FormatTest.java, FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13621) DefaultMaskingFormatter: & is ignored as ending character
[
https://issues.apache.org/jira/browse/CAMEL-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Giera updated CAMEL-13621:
Attachment: FormatUriTest.java
> DefaultMaskingFormatter: & is ignored as ending character
> -
>
> Key: CAMEL-13621
> URL: https://issues.apache.org/jira/browse/CAMEL-13621
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.20.2
> Environment: Camel 2.20.2
> Oracle JDK 8u121
>Reporter: Christoph Giera
>Priority: Minor
> Attachments: FormatTest.java, FormatUriTest.java
>
>
> Using the DefaultMaskingFormatter and formatting a string that contains for
> example
> {noformat}
> password=mypass=nextvalue{noformat}
> should be masked to
> {noformat}
> password="x"=nextvalue{noformat}
> Instead of this the & is ignored(the next parameter will swallowed up) and
> the output looks like the following
> {noformat}
> password="x"{noformat}
>
> Additionaly StackoverflowErrors occur when formatting/masking bigger strings
> with line breaks, see example attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13627) camel-main - Reuse options for main and camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860616#comment-16860616 ] Claus Ibsen commented on CAMEL-13627: - There is also some logic that setup this common configuration that should be reusable > camel-main - Reuse options for main and camel-spring-boot > - > > Key: CAMEL-13627 > URL: https://issues.apache.org/jira/browse/CAMEL-13627 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0.M4 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13632) Deprecate and remove ReloadStrategy
Claus Ibsen created CAMEL-13632: --- Summary: Deprecate and remove ReloadStrategy Key: CAMEL-13632 URL: https://issues.apache.org/jira/browse/CAMEL-13632 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0.M4 This should be deprecated in camel 2.x and removed in 3.0. This makes the modularization of camel 3 better, and its also only used as a developer/demo thing and not for production usage. And today there are better alternatives with camel k, and camel-quarkus etc, for hot re-load that can load the entire app and not only a xml route. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
