[jira] [Created] (CAMEL-13720) Properties component - Remove complexity of augemented properties parser
Claus Ibsen created CAMEL-13720: --- Summary: Properties component - Remove complexity of augemented properties parser Key: CAMEL-13720 URL: https://issues.apache.org/jira/browse/CAMEL-13720 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.0.0, 3.0.0.M4 The need for CAMEL-4520 is not needed and makes the logic too complex. Lets remove this stuff and just use the simpler parser -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13719) Upgrade to jasypt 1.9.3
Claus Ibsen created CAMEL-13719: --- Summary: Upgrade to jasypt 1.9.3 Key: CAMEL-13719 URL: https://issues.apache.org/jira/browse/CAMEL-13719 Project: Camel Issue Type: Task Components: camel-jasypt Reporter: Claus Ibsen Fix For: 3.0.0, 2.25.0 There is a new 1.9.3 release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13718) Fix syntax for pulsar component
[
https://issues.apache.org/jira/browse/CAMEL-13718?focusedWorklogId=270984=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270984
]
ASF GitHub Bot logged work on CAMEL-13718:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 15:55
Start Date: 02/Jul/19 15:55
Worklog Time Spent: 10m
Work Description: lhein commented on pull request #3013: CAMEL-13718 -
fixed wrong syntax for pulsar endpoints
URL: https://github.com/apache/camel/pull/3013
Signed-off-by: Lars Heinemann
This is a change proposal. I haven't tested it in all details. Please make
sure to review the change carefully.
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: 270984)
Time Spent: 10m
Remaining Estimate: 0h
> Fix syntax for pulsar component
> ---
>
> Key: CAMEL-13718
> URL: https://issues.apache.org/jira/browse/CAMEL-13718
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Replace
>
> {noformat}
> pulsar:persistence://tenant/namespace/topic{noformat}
>
> with
> {noformat}
> pulsar:configuration{noformat}
> or
> {noformat}
> pulsar:uri{noformat}
>
> There is currently only a single property of kind "path" for this component
> which is called "topic". The description of that parameter suggests that is
> should hold type, tenant and topic values for the endpoint which makes the
> name "topic" for this parameter a bad choice. I would rather suggest to
> rename it to something more fitting like "configuration" or "uri" instead.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13718) Fix syntax for pulsar component
[
https://issues.apache.org/jira/browse/CAMEL-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877084#comment-16877084
]
Lars Heinemann commented on CAMEL-13718:
added a change proposal at [https://github.com/apache/camel/pull/3013.] please
review and test carefully.
> Fix syntax for pulsar component
> ---
>
> Key: CAMEL-13718
> URL: https://issues.apache.org/jira/browse/CAMEL-13718
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Replace
>
> {noformat}
> pulsar:persistence://tenant/namespace/topic{noformat}
>
> with
> {noformat}
> pulsar:configuration{noformat}
> or
> {noformat}
> pulsar:uri{noformat}
>
> There is currently only a single property of kind "path" for this component
> which is called "topic". The description of that parameter suggests that is
> should hold type, tenant and topic values for the endpoint which makes the
> name "topic" for this parameter a bad choice. I would rather suggest to
> rename it to something more fitting like "configuration" or "uri" instead.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13710) Camel kafka with Spring FileStateRepository example
[ https://issues.apache.org/jira/browse/CAMEL-13710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu resolved CAMEL-13710. -- Resolution: Fixed > Camel kafka with Spring FileStateRepository example > --- > > Key: CAMEL-13710 > URL: https://issues.apache.org/jira/browse/CAMEL-13710 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 3.x >Reporter: Ramu >Assignee: Ramu >Priority: Major > Labels: examples > > Provide an example to write offset,partition to a file using > 'offsetRepository' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13716.
--
Resolution: Fixed
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-13716 started by Andrea Cosentino.
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-13716:
Assignee: Andrea Cosentino
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13717.
--
Resolution: Fixed
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13716:
-
Fix Version/s: 3.0.0.M4
3.0.0
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13717:
-
Fix Version/s: (was: 2.24.2)
(was: 2.25.0)
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?focusedWorklogId=270913=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270913
]
ASF GitHub Bot logged work on CAMEL-13717:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 14:20
Start Date: 02/Jul/19 14:20
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3012: CAMEL-13717 -
fixed wrong syntax for websocket-jsr356 endpoints
URL: https://github.com/apache/camel/pull/3012
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: 270913)
Time Spent: 20m (was: 10m)
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?focusedWorklogId=270912=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270912
]
ASF GitHub Bot logged work on CAMEL-13716:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 14:19
Start Date: 02/Jul/19 14:19
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3011: CAMEL-13716 -
fixed wrong syntax for corda endpoints
URL: https://github.com/apache/camel/pull/3011
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: 270912)
Time Spent: 20m (was: 10m)
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13718) Fix syntax for pulsar component
[
https://issues.apache.org/jira/browse/CAMEL-13718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CAMEL-13718:
---
Description:
Replace
{noformat}
pulsar:persistence://tenant/namespace/topic{noformat}
with
{noformat}
pulsar:configuration{noformat}
or
{noformat}
pulsar:uri{noformat}
There is currently only a single property of kind "path" for this component
which is called "topic". The description of that parameter suggests that is
should hold type, tenant and topic values for the endpoint which makes the name
"topic" for this parameter a bad choice. I would rather suggest to rename it to
something more fitting like "configuration" or "uri" instead.
was:
Replace
{noformat}
pulsar:persistence://tenant/namespace/topic{noformat}
with
{noformat}
pulsar:configuration{noformat}
There is currently only a single property of kind "path" for this component
which is called "topic". The description of that parameter suggests that is
should hold type, tenant and topic values for the endpoint which makes the name
"topic" for this parameter a bad choice. I would rather suggest to rename it to
something more fitting like "configuration" instead.
> Fix syntax for pulsar component
> ---
>
> Key: CAMEL-13718
> URL: https://issues.apache.org/jira/browse/CAMEL-13718
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
>
> Replace
>
> {noformat}
> pulsar:persistence://tenant/namespace/topic{noformat}
>
> with
> {noformat}
> pulsar:configuration{noformat}
> or
> {noformat}
> pulsar:uri{noformat}
>
> There is currently only a single property of kind "path" for this component
> which is called "topic". The description of that parameter suggests that is
> should hold type, tenant and topic values for the endpoint which makes the
> name "topic" for this parameter a bad choice. I would rather suggest to
> rename it to something more fitting like "configuration" or "uri" instead.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13718) Fix syntax for pulsar component
Lars Heinemann created CAMEL-13718:
--
Summary: Fix syntax for pulsar component
Key: CAMEL-13718
URL: https://issues.apache.org/jira/browse/CAMEL-13718
Project: Camel
Issue Type: Bug
Affects Versions: 2.24.1
Reporter: Lars Heinemann
Replace
{noformat}
pulsar:persistence://tenant/namespace/topic{noformat}
with
{noformat}
pulsar:configuration{noformat}
There is currently only a single property of kind "path" for this component
which is called "topic". The description of that parameter suggests that is
should hold type, tenant and topic values for the endpoint which makes the name
"topic" for this parameter a bad choice. I would rather suggest to rename it to
something more fitting like "configuration" instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CAMEL-13717:
---
Component/s: camel-websocket
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
> Components: camel-websocket
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876958#comment-16876958
]
Lars Heinemann commented on CAMEL-13717:
provided a PR at https://github.com/apache/camel/pull/3012
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?focusedWorklogId=270863=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270863
]
ASF GitHub Bot logged work on CAMEL-13717:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 13:16
Start Date: 02/Jul/19 13:16
Worklog Time Spent: 10m
Work Description: lhein commented on pull request #3012: CAMEL-13717 -
fixed wrong syntax for websocket-jsr356 endpoints
URL: https://github.com/apache/camel/pull/3012
Signed-off-by: Lars Heinemann
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: 270863)
Time Spent: 10m
Remaining Estimate: 0h
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13717:
-
Fix Version/s: 3.0.0.M4
2.25.0
2.24.2
3.0.0
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.0.0, 2.24.2, 2.25.0, 3.0.0.M4
>
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13717) Fix syntax for websocket-jsr356 component
[
https://issues.apache.org/jira/browse/CAMEL-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-13717:
Assignee: Andrea Cosentino
> Fix syntax for websocket-jsr356 component
> -
>
> Key: CAMEL-13717
> URL: https://issues.apache.org/jira/browse/CAMEL-13717
> Project: Camel
> Issue Type: Bug
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Assignee: Andrea Cosentino
>Priority: Major
>
> replace
> {noformat}
> resourceUri{noformat}
> with
> {noformat}
> websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13717) Fix syntax for websocket-jsr356 component
Lars Heinemann created CAMEL-13717:
--
Summary: Fix syntax for websocket-jsr356 component
Key: CAMEL-13717
URL: https://issues.apache.org/jira/browse/CAMEL-13717
Project: Camel
Issue Type: Bug
Affects Versions: 2.24.1
Reporter: Lars Heinemann
replace
{noformat}
resourceUri{noformat}
with
{noformat}
websocketPathOrUri{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876942#comment-16876942
]
Lars Heinemann commented on CAMEL-13716:
provided a PR at https://github.com/apache/camel/pull/3011
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Heinemann updated CAMEL-13716:
---
Component/s: (was: tooling)
camel-corda
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13716) Fix syntax for corda component
[
https://issues.apache.org/jira/browse/CAMEL-13716?focusedWorklogId=270855=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270855
]
ASF GitHub Bot logged work on CAMEL-13716:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 13:00
Start Date: 02/Jul/19 13:00
Worklog Time Spent: 10m
Work Description: lhein commented on pull request #3011: CAMEL-13716 -
fixed wrong syntax for corda endpoints
URL: https://github.com/apache/camel/pull/3011
Signed-off-by: Lars Heinemann
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: 270855)
Time Spent: 10m
Remaining Estimate: 0h
> Fix syntax for corda component
> --
>
> Key: CAMEL-13716
> URL: https://issues.apache.org/jira/browse/CAMEL-13716
> Project: Camel
> Issue Type: Bug
> Components: camel-corda
>Affects Versions: 2.24.1
>Reporter: Lars Heinemann
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> replace
> {noformat}
> corda:url {noformat}
> with
> {noformat}
> corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13716) Fix syntax for corda component
Lars Heinemann created CAMEL-13716:
--
Summary: Fix syntax for corda component
Key: CAMEL-13716
URL: https://issues.apache.org/jira/browse/CAMEL-13716
Project: Camel
Issue Type: Bug
Components: tooling
Affects Versions: 2.24.1
Reporter: Lars Heinemann
replace
{noformat}
corda:url {noformat}
with
{noformat}
corda:configuration{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13708) PropertiesSource to resolve a single property
[ https://issues.apache.org/jira/browse/CAMEL-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876927#comment-16876927 ] Luca Burgazzoli commented on CAMEL-13708: - Yeah, that's was the rationale for CAMEL-13694 > PropertiesSource to resolve a single property > - > > Key: CAMEL-13708 > URL: https://issues.apache.org/jira/browse/CAMEL-13708 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0 > > > CAMEL-13705 introduces support for property sources such as MP Config and > others and at the moment it does require to load all the properties upfront > on source initialization. > It would be nice to have an additional method to resolve a single property as > some back-and may perform some I/O to resolve properties and get alll of them > could be expensive. > So the properties component should: > - leverage PropertiesSource::loadPropertiers() when is is required to know > all the properties (i.e. when auto configure components in camel main) > - leverage a new PropertiesSource::resolveProperty(String) when it just need > to resolve a single property -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13708) PropertiesSource to resolve a single property
[ https://issues.apache.org/jira/browse/CAMEL-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876922#comment-16876922 ] Claus Ibsen commented on CAMEL-13708: - We can also consider having PropertySource for on-demand, and other PropertiesSource that are load everything at init phase. > PropertiesSource to resolve a single property > - > > Key: CAMEL-13708 > URL: https://issues.apache.org/jira/browse/CAMEL-13708 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.0.0 > > > CAMEL-13705 introduces support for property sources such as MP Config and > others and at the moment it does require to load all the properties upfront > on source initialization. > It would be nice to have an additional method to resolve a single property as > some back-and may perform some I/O to resolve properties and get alll of them > could be expensive. > So the properties component should: > - leverage PropertiesSource::loadPropertiers() when is is required to know > all the properties (i.e. when auto configure components in camel main) > - leverage a new PropertiesSource::resolveProperty(String) when it just need > to resolve a single property -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13708) PropertiesSource to resolve a single property
[
https://issues.apache.org/jira/browse/CAMEL-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876921#comment-16876921
]
Claus Ibsen commented on CAMEL-13708:
-
Hmm so currently Camel's property placeholder is based on the principle of all
the properties are loaded / initialized into a combined java.util.Properties,
which are then used by the parser to find / replace placeholders with the {{ }}
syntax.
So if the idea is to have a more on-demand lookup, then we would need to work
on some new API instead to use than java.util.Properties that gets used, so we
can have something that just does as today lookup in the big
java.util.Properties and then another way to pass in something that does an
on-demand single property lookup.
> PropertiesSource to resolve a single property
> -
>
> Key: CAMEL-13708
> URL: https://issues.apache.org/jira/browse/CAMEL-13708
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.0.0
>
>
> CAMEL-13705 introduces support for property sources such as MP Config and
> others and at the moment it does require to load all the properties upfront
> on source initialization.
> It would be nice to have an additional method to resolve a single property as
> some back-and may perform some I/O to resolve properties and get alll of them
> could be expensive.
> So the properties component should:
> - leverage PropertiesSource::loadPropertiers() when is is required to know
> all the properties (i.e. when auto configure components in camel main)
> - leverage a new PropertiesSource::resolveProperty(String) when it just need
> to resolve a single property
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876908#comment-16876908
]
Claus Ibsen commented on CAMEL-13680:
-
Added a check that if readLock=fileLock on windows you now get an error and
also updated the doc.
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.file.FileSystemException:
> work\cbr\input\ID-WIN-JTA8KU4EF9D-1561426618994-0-2 ->
> work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2: The process cannot
> access the file because it is being used by another process
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
> at java.nio.file.Files.copy(Unknown Source)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13680:
Fix Version/s: 2.25.0
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.file.FileSystemException:
> work\cbr\input\ID-WIN-JTA8KU4EF9D-1561426618994-0-2 ->
> work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2: The process cannot
> access the file because it is being used by another process
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
> at java.nio.file.Files.copy(Unknown Source)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876904#comment-16876904
]
Claus Ibsen commented on CAMEL-13680:
-
Okay so this is not possible on windows with readLock=fileLock. The changes we
did previously was only to ensure the file lock could be released.
There are too many places where the file component can do a copy/rename/move or
other operations. We will update the doc to mention that readLock=fileLock is
not supported on windows. You can use any of the many other read locks on
windows instead.
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.file.FileSystemException:
> work\cbr\input\ID-WIN-JTA8KU4EF9D-1561426618994-0-2 ->
> work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2: The process cannot
> access the file because it is being used by another process
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
> at java.nio.file.Files.copy(Unknown Source)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13713) Two CI server failures for camel-ribbon
[ https://issues.apache.org/jira/browse/CAMEL-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger updated CAMEL-13713: --- Affects Version/s: 3.0.0-M3 > Two CI server failures for camel-ribbon > --- > > Key: CAMEL-13713 > URL: https://issues.apache.org/jira/browse/CAMEL-13713 > Project: Camel > Issue Type: Task > Components: tests >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Alex Dettinger >Priority: Major > > Error Message > java.io.IOException: Failed to bind to /127.0.0.1:8084 > Stacktrace > org.apache.camel.RuntimeCamelException: java.io.IOException: Failed to bind > to /127.0.0.1:8084 > Caused by: java.io.IOException: Failed to bind to /127.0.0.1:8084 > Caused by: java.net.BindException: Address already in use > https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.consul.cloud/ConsulRibbonServiceCallRouteTest/testServiceCall/ > Has been failing for the last 5 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13713) Two CI server failures for camel-ribbon
[ https://issues.apache.org/jira/browse/CAMEL-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-13713. Resolution: Fixed Fix Version/s: 3.0.0.M4 Two test classes were impacted: ConsulDefaultServiceCallRouteTest ConsulRibbonServiceCallRouteTest This issue did not appear anymore in the last build, yet I've switched to dynamic port allocation in order to narrow down the probability of port conflict. > Two CI server failures for camel-ribbon > --- > > Key: CAMEL-13713 > URL: https://issues.apache.org/jira/browse/CAMEL-13713 > Project: Camel > Issue Type: Task > Components: tests >Affects Versions: 3.0.0-M3 >Reporter: Claus Ibsen >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0.M4 > > > Error Message > java.io.IOException: Failed to bind to /127.0.0.1:8084 > Stacktrace > org.apache.camel.RuntimeCamelException: java.io.IOException: Failed to bind > to /127.0.0.1:8084 > Caused by: java.io.IOException: Failed to bind to /127.0.0.1:8084 > Caused by: java.net.BindException: Address already in use > https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.consul.cloud/ConsulRibbonServiceCallRouteTest/testServiceCall/ > Has been failing for the last 5 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13700) createRowModel failed to set cell's valueType
[
https://issues.apache.org/jira/browse/CAMEL-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13700:
Fix Version/s: 2.25.0
2.24.2
2.23.4
3.0.0
> createRowModel failed to set cell's valueType
> -
>
> Key: CAMEL-13700
> URL: https://issues.apache.org/jira/browse/CAMEL-13700
> Project: Camel
> Issue Type: Bug
> Components: camel-hbase
>Affects Versions: 2.24.0
>Reporter: kevin.cao
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0
>
>
> When
> {code:java}
> org.apache.camel.component.hbase.HBaseEndpoint#createRowModel
> {code}
> function has been called, following code should check if `valueType`
> parameter has been set, if so, then set cell's valueType.
> {code:java}
> if (parameters.containsKey(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i))) {
> String valueType =
> String.valueOf(parameters.remove(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i)));
> if (valueType != null && !valueType.isEmpty()) {
>
> rowModel.setRowType(getCamelContext().getClassResolver().resolveClass(valueType));
> }
> }
> {code}
> However, the code set rowModel's rowType instead of cellModel's valueType,
> and, IMHO, this is not correct.
>
> My endpoint is configurated as following:
> {code:xml}
> uri="hbase:table?operation=CamelHBaseScanrow.family=motionrow.qualifier=aver_max_Arow.valueType=java.lang.Integer"
> />
> {code}
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13700) createRowModel failed to set cell's valueType
[
https://issues.apache.org/jira/browse/CAMEL-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13700:
Estimated Complexity: Novice (was: Unknown)
> createRowModel failed to set cell's valueType
> -
>
> Key: CAMEL-13700
> URL: https://issues.apache.org/jira/browse/CAMEL-13700
> Project: Camel
> Issue Type: Bug
> Components: camel-hbase
>Affects Versions: 2.24.0
>Reporter: kevin.cao
>Priority: Major
>
> When
> {code:java}
> org.apache.camel.component.hbase.HBaseEndpoint#createRowModel
> {code}
> function has been called, following code should check if `valueType`
> parameter has been set, if so, then set cell's valueType.
> {code:java}
> if (parameters.containsKey(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i))) {
> String valueType =
> String.valueOf(parameters.remove(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i)));
> if (valueType != null && !valueType.isEmpty()) {
>
> rowModel.setRowType(getCamelContext().getClassResolver().resolveClass(valueType));
> }
> }
> {code}
> However, the code set rowModel's rowType instead of cellModel's valueType,
> and, IMHO, this is not correct.
>
> My endpoint is configurated as following:
> {code:xml}
> uri="hbase:table?operation=CamelHBaseScanrow.family=motionrow.qualifier=aver_max_Arow.valueType=java.lang.Integer"
> />
> {code}
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13700) createRowModel failed to set cell's valueType
[
https://issues.apache.org/jira/browse/CAMEL-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876885#comment-16876885
]
Claus Ibsen commented on CAMEL-13700:
-
Ah yeah that seems more correct. You are welcome to provide a PR
> createRowModel failed to set cell's valueType
> -
>
> Key: CAMEL-13700
> URL: https://issues.apache.org/jira/browse/CAMEL-13700
> Project: Camel
> Issue Type: Bug
> Components: camel-hbase
>Affects Versions: 2.24.0
>Reporter: kevin.cao
>Priority: Major
>
> When
> {code:java}
> org.apache.camel.component.hbase.HBaseEndpoint#createRowModel
> {code}
> function has been called, following code should check if `valueType`
> parameter has been set, if so, then set cell's valueType.
> {code:java}
> if (parameters.containsKey(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i))) {
> String valueType =
> String.valueOf(parameters.remove(HBaseAttribute.HBASE_VALUE_TYPE.asOption(i)));
> if (valueType != null && !valueType.isEmpty()) {
>
> rowModel.setRowType(getCamelContext().getClassResolver().resolveClass(valueType));
> }
> }
> {code}
> However, the code set rowModel's rowType instead of cellModel's valueType,
> and, IMHO, this is not correct.
>
> My endpoint is configurated as following:
> {code:xml}
> uri="hbase:table?operation=CamelHBaseScanrow.family=motionrow.qualifier=aver_max_Arow.valueType=java.lang.Integer"
> />
> {code}
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13715) Remove dummyTrustManager from camel-mail
[ https://issues.apache.org/jira/browse/CAMEL-13715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13715. - Resolution: Fixed > Remove dummyTrustManager from camel-mail > > > Key: CAMEL-13715 > URL: https://issues.apache.org/jira/browse/CAMEL-13715 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > The camel-mail has a "*dummyTrustManager*" boolean configuration switch that > disables all TLS verification. This is not a good idea as it can easily be > set to false in development and not changed thereafter. Better instead to > force the user to set the truststore appropriately. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13711) Files.createTempFile not equivalent to File.createTempFile
[
https://issues.apache.org/jira/browse/CAMEL-13711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13711.
--
Resolution: Fixed
> Files.createTempFile not equivalent to File.createTempFile
> --
>
> Key: CAMEL-13711
> URL: https://issues.apache.org/jira/browse/CAMEL-13711
> Project: Camel
> Issue Type: Bug
> Components: camel-hdfs2
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It seems that Files.createTempFile is NOT equivalent to File.createTempFile.
> With this debug code
> {code}
> private File getHfdsFileToTmpFile(String hdfsPath, HdfsConfiguration
> configuration) {
> try {
> String fname = hdfsPath.substring(hdfsPath.lastIndexOf('/'));
> System.out.println("fname: " + fname);
>
> File outputDest;
> try {
> System.out.println("First trying: Files.createTempFile");
> outputDest = Files.createTempFile(fname,
> ".hdfs").toFile();
> } catch (Exception ex) {
>
> ex.printStackTrace();
> System.out.println("Now trying: File.createTempFile");
> outputDest = File.createTempFile(fname, ".hdfs");
> }
>
> System.out.println("outputDest: " + outputDest);
>
>...
> }
> },
> {code}
> I see ...
> {code}
> {12:29:50,180 INFO [stdout] fname: /ID-MacBook-1561976987280-0-1.opened
> 12:29:50,180 INFO [stdout] First trying: Files.createTempFile
> 12:29:50,189 ERROR [stderr] java.lang.IllegalArgumentException: Invalid
> prefix or suffix
> 12:29:50,189 ERROR [stderr] at
> java.nio.file.TempFileHelper.generatePath(TempFileHelper.java:63)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.create(TempFileHelper.java:127)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:161)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.Files.createTempFile(Files.java:897)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.getHfdsFileToTmpFile(HdfsFileType.java:147)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.createInputStream(HdfsFileType.java:131)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsInputStream.createInputStream(HdfsInputStream.java:50)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.doPoll(HdfsConsumer.java:139)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.poll(HdfsConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:170)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:29:50,192 ERROR [stderr] at java.lang.Thread.run(Thread.java:748)
> 12:29:50,192 INFO [stdout] Now trying: File.createTempFile
> 12:29:50,193 INFO [stdout] outputDest:
> /var/folders/11/lsh29g8s2msbx_sv1j2zzg5cgn/T/ID-MacBook-1561976987280-0-1.opened3105164072945824679.hdfs
> {code}
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2838
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13711) Files.createTempFile not equivalent to File.createTempFile
[
https://issues.apache.org/jira/browse/CAMEL-13711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13711:
-
Fix Version/s: 3.0.0.M4
2.25.0
> Files.createTempFile not equivalent to File.createTempFile
> --
>
> Key: CAMEL-13711
> URL: https://issues.apache.org/jira/browse/CAMEL-13711
> Project: Camel
> Issue Type: Bug
> Components: camel-hdfs2
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0, 2.25.0, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It seems that Files.createTempFile is NOT equivalent to File.createTempFile.
> With this debug code
> {code}
> private File getHfdsFileToTmpFile(String hdfsPath, HdfsConfiguration
> configuration) {
> try {
> String fname = hdfsPath.substring(hdfsPath.lastIndexOf('/'));
> System.out.println("fname: " + fname);
>
> File outputDest;
> try {
> System.out.println("First trying: Files.createTempFile");
> outputDest = Files.createTempFile(fname,
> ".hdfs").toFile();
> } catch (Exception ex) {
>
> ex.printStackTrace();
> System.out.println("Now trying: File.createTempFile");
> outputDest = File.createTempFile(fname, ".hdfs");
> }
>
> System.out.println("outputDest: " + outputDest);
>
>...
> }
> },
> {code}
> I see ...
> {code}
> {12:29:50,180 INFO [stdout] fname: /ID-MacBook-1561976987280-0-1.opened
> 12:29:50,180 INFO [stdout] First trying: Files.createTempFile
> 12:29:50,189 ERROR [stderr] java.lang.IllegalArgumentException: Invalid
> prefix or suffix
> 12:29:50,189 ERROR [stderr] at
> java.nio.file.TempFileHelper.generatePath(TempFileHelper.java:63)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.create(TempFileHelper.java:127)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:161)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.Files.createTempFile(Files.java:897)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.getHfdsFileToTmpFile(HdfsFileType.java:147)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.createInputStream(HdfsFileType.java:131)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsInputStream.createInputStream(HdfsInputStream.java:50)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.doPoll(HdfsConsumer.java:139)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.poll(HdfsConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:170)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:29:50,192 ERROR [stderr] at java.lang.Thread.run(Thread.java:748)
> 12:29:50,192 INFO [stdout] Now trying: File.createTempFile
> 12:29:50,193 INFO [stdout] outputDest:
> /var/folders/11/lsh29g8s2msbx_sv1j2zzg5cgn/T/ID-MacBook-1561976987280-0-1.opened3105164072945824679.hdfs
> {code}
> CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/2838
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13715) Remove dummyTrustManager from camel-mail
Colm O hEigeartaigh created CAMEL-13715: --- Summary: Remove dummyTrustManager from camel-mail Key: CAMEL-13715 URL: https://issues.apache.org/jira/browse/CAMEL-13715 Project: Camel Issue Type: Improvement Components: camel-mail Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 The camel-mail has a "*dummyTrustManager*" boolean configuration switch that disables all TLS verification. This is not a good idea as it can easily be set to false in development and not changed thereafter. Better instead to force the user to set the truststore appropriately. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876815#comment-16876815
]
hisao furuichi edited comment on CAMEL-13680 at 7/2/19 9:28 AM:
Yes. I tested it, but does not work either.
Even I enabled the option, go into the same stack trace.
{code:java}
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
at java.nio.file.Files.copy(Unknown Source)
at org.apache.camel.util.FileUtil.copyFile(FileUtil.java:541)
at org.apache.camel.util.FileUtil.renameFileUsingCopy(FileUtil.java:525)
{code}
Please take a look at this source code, how the "renameUsingCopy" option is
used.
[https://github.com/apache/camel/blob/eed7b1113ec1b72731b051f69ea3d269bf5fb1c5/components/camel-file/src/main/java/org/apache/camel/component/file/FileOperations.java#L80]
was (Author: hfuruichi):
Yes. I tested it, but does not work either.
Even I enabled the option, go into the same stack trace.
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
at java.nio.file.Files.copy(Unknown Source)
at org.apache.camel.util.FileUtil.copyFile(FileUtil.java:541)
at org.apache.camel.util.FileUtil.renameFileUsingCopy(FileUtil.java:525)
Please take a look at this source code, how the "renameUsingCopy" option is
used.
https://github.com/apache/camel/blob/eed7b1113ec1b72731b051f69ea3d269bf5fb1c5/components/camel-file/src/main/java/org/apache/camel/component/file/FileOperations.java#L80
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at
[jira] [Commented] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876815#comment-16876815
]
hisao furuichi commented on CAMEL-13680:
Yes. I tested it, but does not work either.
Even I enabled the option, go into the same stack trace.
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
at java.nio.file.Files.copy(Unknown Source)
at org.apache.camel.util.FileUtil.copyFile(FileUtil.java:541)
at org.apache.camel.util.FileUtil.renameFileUsingCopy(FileUtil.java:525)
Please take a look at this source code, how the "renameUsingCopy" option is
used.
https://github.com/apache/camel/blob/eed7b1113ec1b72731b051f69ea3d269bf5fb1c5/components/camel-file/src/main/java/org/apache/camel/component/file/FileOperations.java#L80
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.file.FileSystemException:
> work\cbr\input\ID-WIN-JTA8KU4EF9D-1561426618994-0-2 ->
> work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2: The process cannot
> access the file because it is being used by another process
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
> at java.nio.file.Files.copy(Unknown Source)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13466.
-
Resolution: Fixed
Fix Version/s: 3.0.0.M4
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M4
>
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
> One of this routes is a CxfConsumer which has already been instanciated, with
> a server creation :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
> Even with {{DefaultCamelContext.doStop()}}, the server is still started and
> available in {{/services}}.
> Tried a fix by adding this line in DefaultCamelContext:3502 :
> {code:java}
> // fill all the routes to be stopped
> getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
> // stop route inputs in the same order as they was started so we stop the
> very first inputs first
> try {
> // force shutting down routes as they may otherwise cause shutdown to hang
> ...
> {code}
> And now the endpoint isn't available anymore.
> But this fix isn't effective enough as {{getRouteStartupOrder()}} may have
> duplicates?
> Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876794#comment-16876794
]
Claus Ibsen commented on CAMEL-13680:
-
Can you try set renameUsingCopy=true
> camel-file - From file to file with readLock=fileLock dont work on windows
> --
>
> Key: CAMEL-13680
> URL: https://issues.apache.org/jira/browse/CAMEL-13680
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M4
>
>
> You can get errors like
> {code}
> Stacktrace
> ---
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> store file: work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2
> at
> org.apache.camel.component.file.FileOperations.storeFile(FileOperations.java:352)
> at
> org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:305)
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169)
> at
> org.apache.camel.component.file.GenericFileProducer.process(GenericFileProducer.java:80)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at
> org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:452)
> at
> org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:219)
> at
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:183)
> 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(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.nio.file.FileSystemException:
> work\cbr\input\ID-WIN-JTA8KU4EF9D-1561426618994-0-2 ->
> work\cbr\output\ID-WIN-JTA8KU4EF9D-1561426618994-0-2: The process cannot
> access the file because it is being used by another process
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
> at java.nio.file.Files.copy(Unknown Source)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13680) camel-file - From file to file with readLock=fileLock dont work on windows
[
https://issues.apache.org/jira/browse/CAMEL-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876789#comment-16876789
]
hisao furuichi commented on CAMEL-13680:
Hello [~davsclaus],
I realized that the fix was not enough for this issue.
org.apache.camel.component.file.FileOperations.writeFileByFile() was OK now,
but we also need to fix
org.apache.camel.component.file.FileOperations.renameFile() and
org.apache.camel.util.FileUtil class's methods to avoid to use
java.nio.file.Files.copy() method.
Please take a look at this stack trace to get an idea about it. (Sorry it's not
3.0.x, but I hope it still helps)
{code:java}
[ead #4 - file://work/cbr/input] GenericFileOnCompletionWARN Error
during commit. Exchange[ID-WIN-JTA8KU4EF9D-1562055372761-0-1]. Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - Error
renaming file from
C:\Users\Administrator\workspace\FuseReproducer\work\cbr\input\ID-WIN-JTA8KU4EF9D-1562029860727-1-2
to work\cbr\input\.camel\ID-WIN-JTA8KU4EF9D-1562029860727-1-2]
org.apache.camel.component.file.GenericFileOperationFailedException: Error
renaming file from
C:\Users\Administrator\workspace\FuseReproducer\work\cbr\input\ID-WIN-JTA8KU4EF9D-1562029860727-1-2
to work\cbr\input\.camel\ID-WIN-JTA8KU4EF9D-1562029860727-1-2
at
org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:85)
at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:128)
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:111)
at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:127)
at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:83)
at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:59)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:104)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:243)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:65)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:685)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:634)
at
org.apache.camel.processor.CamelInternalProcessor$InternalCallback.done(CamelInternalProcessor.java:251)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:127)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
at
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:454)
at
org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:223)
at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:187)
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(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.nio.file.FileSystemException:
C:\Users\Administrator\workspace\FuseReproducer\work\cbr\input\ID-WIN-JTA8KU4EF9D-1562029860727-1-2
-> work\cbr\input\.camel\ID-WIN-JTA8KU4EF9D-1562029860727-1-2: The process
cannot access the file because it is being used by another process
at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
at sun.nio.fs.WindowsFileCopy.copy(Unknown Source)
at sun.nio.fs.WindowsFileSystemProvider.copy(Unknown Source)
at java.nio.file.Files.copy(Unknown Source)
at org.apache.camel.util.FileUtil.copyFile(FileUtil.java:541)
at org.apache.camel.util.FileUtil.renameFileUsingCopy(FileUtil.java:525)
at org.apache.camel.util.FileUtil.renameFile(FileUtil.java:499)
at
org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:82)
... 25 more
{code}
> camel-file - From file to file
[jira] [Resolved] (CAMEL-13714) Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint parameter
[ https://issues.apache.org/jira/browse/CAMEL-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13714. -- Resolution: Fixed > Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint parameter > - > > Key: CAMEL-13714 > URL: https://issues.apache.org/jira/browse/CAMEL-13714 > Project: Camel > Issue Type: Task > Components: camel-aws-s3 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We can add the option and leave the header as first choice to be considered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13711) Files.createTempFile not equivalent to File.createTempFile
[
https://issues.apache.org/jira/browse/CAMEL-13711?focusedWorklogId=270700=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270700
]
ASF GitHub Bot logged work on CAMEL-13711:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 08:25
Start Date: 02/Jul/19 08:25
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3008: [CAMEL-13711]
Files.createTempFile not equivalent to File.createTempFile
URL: https://github.com/apache/camel/pull/3008
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: 270700)
Time Spent: 20m (was: 10m)
> Files.createTempFile not equivalent to File.createTempFile
> --
>
> Key: CAMEL-13711
> URL: https://issues.apache.org/jira/browse/CAMEL-13711
> Project: Camel
> Issue Type: Bug
> Components: camel-hdfs2
>Reporter: Thomas Diesler
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It seems that Files.createTempFile is NOT equivalent to File.createTempFile.
> With this debug code
> {code}
> private File getHfdsFileToTmpFile(String hdfsPath, HdfsConfiguration
> configuration) {
> try {
> String fname = hdfsPath.substring(hdfsPath.lastIndexOf('/'));
> System.out.println("fname: " + fname);
>
> File outputDest;
> try {
> System.out.println("First trying: Files.createTempFile");
> outputDest = Files.createTempFile(fname,
> ".hdfs").toFile();
> } catch (Exception ex) {
>
> ex.printStackTrace();
> System.out.println("Now trying: File.createTempFile");
> outputDest = File.createTempFile(fname, ".hdfs");
> }
>
> System.out.println("outputDest: " + outputDest);
>
>...
> }
> },
> {code}
> I see ...
> {code}
> {12:29:50,180 INFO [stdout] fname: /ID-MacBook-1561976987280-0-1.opened
> 12:29:50,180 INFO [stdout] First trying: Files.createTempFile
> 12:29:50,189 ERROR [stderr] java.lang.IllegalArgumentException: Invalid
> prefix or suffix
> 12:29:50,189 ERROR [stderr] at
> java.nio.file.TempFileHelper.generatePath(TempFileHelper.java:63)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.create(TempFileHelper.java:127)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.TempFileHelper.createTempFile(TempFileHelper.java:161)
> 12:29:50,190 ERROR [stderr] at
> java.nio.file.Files.createTempFile(Files.java:897)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.getHfdsFileToTmpFile(HdfsFileType.java:147)
> 12:29:50,190 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsFileType$1.createInputStream(HdfsFileType.java:131)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsInputStream.createInputStream(HdfsInputStream.java:50)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.doPoll(HdfsConsumer.java:139)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.component.hdfs2.HdfsConsumer.poll(HdfsConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:170)
> 12:29:50,191 ERROR [stderr] at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:97)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 12:29:50,191 ERROR [stderr] at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:29:50,192 ERROR [stderr] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:29:50,192 ERROR [stderr] at java.lang.Thread.run(Thread.java:748)
> 12:29:50,192 INFO [stdout] Now trying: File.createTempFile
>
[jira] [Work logged] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?focusedWorklogId=270699=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-270699
]
ASF GitHub Bot logged work on CAMEL-13466:
--
Author: ASF GitHub Bot
Created on: 02/Jul/19 08:25
Start Date: 02/Jul/19 08:25
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #2917:
[CAMEL-13466] Fully populate (including routes which failed to start) routes to
be stopped in the CamelContext
URL: https://github.com/apache/camel/pull/2917
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: 270699)
Time Spent: 20m (was: 10m)
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0
>
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
> One of this routes is a CxfConsumer which has already been instanciated, with
> a server creation :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
> Even with {{DefaultCamelContext.doStop()}}, the server is still started and
> available in {{/services}}.
> Tried a fix by adding this line in DefaultCamelContext:3502 :
> {code:java}
> // fill all the routes to be stopped
> getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
> // stop route inputs in the same order as they was started so we stop the
> very first inputs first
> try {
> // force shutting down routes as they may otherwise cause shutdown to hang
> ...
> {code}
> And now the endpoint isn't available anymore.
> But this fix isn't effective enough as {{getRouteStartupOrder()}} may have
> duplicates?
> Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876771#comment-16876771
]
Claus Ibsen commented on CAMEL-13466:
-
Okay I found some time to work on this and have a working fix with unit test.
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0
>
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
> One of this routes is a CxfConsumer which has already been instanciated, with
> a server creation :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
> Even with {{DefaultCamelContext.doStop()}}, the server is still started and
> available in {{/services}}.
> Tried a fix by adding this line in DefaultCamelContext:3502 :
> {code:java}
> // fill all the routes to be stopped
> getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
> // stop route inputs in the same order as they was started so we stop the
> very first inputs first
> try {
> // force shutting down routes as they may otherwise cause shutdown to hang
> ...
> {code}
> And now the endpoint isn't available anymore.
> But this fix isn't effective enough as {{getRouteStartupOrder()}} may have
> duplicates?
> Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13714) Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint parameter
[ https://issues.apache.org/jira/browse/CAMEL-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13714: - Summary: Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint parameter (was: Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint property) > Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint parameter > - > > Key: CAMEL-13714 > URL: https://issues.apache.org/jira/browse/CAMEL-13714 > Project: Camel > Issue Type: Task > Components: camel-aws-s3 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > We can add the option and leave the header as first choice to be considered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13714) Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint property
Andrea Cosentino created CAMEL-13714: Summary: Camel-AWS-S3: Add and option to specify the S3 Key also as endpoint property Key: CAMEL-13714 URL: https://issues.apache.org/jira/browse/CAMEL-13714 Project: Camel Issue Type: Task Components: camel-aws-s3 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0, 3.0.0.M4 We can add the option and leave the header as first choice to be considered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13713) Two CI server failures for camel-ribbon
[ https://issues.apache.org/jira/browse/CAMEL-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger reassigned CAMEL-13713: -- Assignee: Alex Dettinger > Two CI server failures for camel-ribbon > --- > > Key: CAMEL-13713 > URL: https://issues.apache.org/jira/browse/CAMEL-13713 > Project: Camel > Issue Type: Task > Components: tests >Reporter: Claus Ibsen >Assignee: Alex Dettinger >Priority: Major > > Error Message > java.io.IOException: Failed to bind to /127.0.0.1:8084 > Stacktrace > org.apache.camel.RuntimeCamelException: java.io.IOException: Failed to bind > to /127.0.0.1:8084 > Caused by: java.io.IOException: Failed to bind to /127.0.0.1:8084 > Caused by: java.net.BindException: Address already in use > https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.consul.cloud/ConsulRibbonServiceCallRouteTest/testServiceCall/ > Has been failing for the last 5 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13713) Two CI server failures for camel-ribbon
Claus Ibsen created CAMEL-13713: --- Summary: Two CI server failures for camel-ribbon Key: CAMEL-13713 URL: https://issues.apache.org/jira/browse/CAMEL-13713 Project: Camel Issue Type: Task Components: tests Reporter: Claus Ibsen Error Message java.io.IOException: Failed to bind to /127.0.0.1:8084 Stacktrace org.apache.camel.RuntimeCamelException: java.io.IOException: Failed to bind to /127.0.0.1:8084 Caused by: java.io.IOException: Failed to bind to /127.0.0.1:8084 Caused by: java.net.BindException: Address already in use https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.consul.cloud/ConsulRibbonServiceCallRouteTest/testServiceCall/ Has been failing for the last 5 builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
