[jira] [Updated] (CAMEL-20908) camel-debug - Support `pause` of all route exchanges
[
https://issues.apache.org/jira/browse/CAMEL-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20908:
Fix Version/s: 4.x
> camel-debug - Support `pause` of all route exchanges
>
>
> Key: CAMEL-20908
> URL: https://issues.apache.org/jira/browse/CAMEL-20908
> Project: Camel
> Issue Type: New Feature
> Components: camel-management
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.x
>
>
> it would convenient for investigation to be able to pause all current route
> exchange at the nearest point (surely next step) to investigate what is going
> on with the routes.
> It would be convenient to be able to pause all exchanges and also to be able
> to pause for a Route definition or a Camel context.
> Currently, suspend is no more starting new routes but finishes the current
> exchanges. The stop is no more starting the routes and not finishing the
> current exchange.
>
> Technical:
> it would likely be some option you turn on|off to have this behaviour - we
> can debate whether it should be on as default (new) or off (like now). To
> checked that it is not breaking other flow, like in Hawt.io to use the new
> behavior as default.
> {color:#262626}or a parameter on the suspend/stop methods?{color}
> {color:#262626}or create another one, as pause{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20140) camel-report:route-coverage results in no code coverage
[
https://issues.apache.org/jira/browse/CAMEL-20140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20140:
Fix Version/s: 4.0.6
> camel-report:route-coverage results in no code coverage
>
>
> Key: CAMEL-20140
> URL: https://issues.apache.org/jira/browse/CAMEL-20140
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.1.0
> Environment: Apache Maven 3.9.4
> (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /opt/maven
> Java version: 17.0.8.1, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "5.10.16.3-microsoft-standard-wsl2", arch:
> "amd64", family: "unix"
>Reporter: Magnus Bosson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.0.6, 4.3.0
>
>
> After upgrading my application from camel 3.20.4 and spring 2.7.11 to camel
> 4.1.0 and spring-boot 3.1.4 {{mvn camel-report:route-coverage}} results in no
> code coverage.
> {{mvn test}} generates files under target/camel-route-coverage for both
> versions
> *Camel 3.20.4*
> {code:java}
> mvn camel-report:route-coverage
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< xx.xxx.xxx.:-producer
> >--
> [INFO] Building -producer 0.0.1-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- camel-report:3.20.4:route-coverage (default-cli) @
> -producer ---
> [INFO] Discovered 1 routes
> [INFO] Route coverage summary:Class: xx.xxx.xxx.:-producer
> Route: ExampleRoute Line # Count Route
> -- - -
> 33 3 from
> 35 3 setHeader
> 36 3 log
> 37 3 to
> 38 2 choice
> 40 1 setHeader
> 41 1 log
> 43 1 setHeader
> 44 1 log
> 46 2 removeHeaders
> 47 2 to
> 48 2 logCoverage: 12 out of 12 (100.0% / threshold
> 100.0%)
> Status: Success{code}
> {{ }}
> *Camel 4.1*
> {code:java}
> mvn camel-report:route-coverage
> [WARNING] No route coverage data found for route: ExampleRouteId. Make sure
> to enable route coverage in your unit tests and assign unique route ids to
> your routes. Also remember to run unit tests first.{code}
> I found a differance in the output xml-files in target/camel-route-coverage
> between the versions
> The attribute *_customId="true"_* is missing from element *_route_* in
> version 4.1.0 ({{{} camel-report:route-coverage}} yields the expected result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20910:
Fix Version/s: 4.x
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Priority: Minor
> Fix For: 4.x
>
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20910:
Priority: Minor (was: Major)
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Priority: Minor
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20910:
Issue Type: Task (was: Bug)
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Priority: Minor
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
Adriano Machado created CAMEL-20910:
---
Summary: Build is failing with mvnd 1.0.0/1.0.1
Key: CAMEL-20910
URL: https://issues.apache.org/jira/browse/CAMEL-20910
Project: Camel
Issue Type: Bug
Components: tooling
Affects Versions: 4.6.0
Reporter: Adriano Machado
Build is failing using mvnd 1.0.0
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.577 s (Wall Clock)
[INFO] Finished at: 2024-06-24T23:40:46-04:00
[INFO]
[ERROR] Failed to execute goal
org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
(default) on project camel-dependencies: camelParentPomXml
/Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
does not exist -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20908) camel-debug - Support `pause` of all route exchanges
[
https://issues.apache.org/jira/browse/CAMEL-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859772#comment-17859772
]
Aurélien Pupier commented on CAMEL-20908:
-
Agree that it must be only in debug mode and not in production
> camel-debug - Support `pause` of all route exchanges
>
>
> Key: CAMEL-20908
> URL: https://issues.apache.org/jira/browse/CAMEL-20908
> Project: Camel
> Issue Type: New Feature
> Components: camel-management
>Reporter: Aurélien Pupier
>Priority: Major
>
> it would convenient for investigation to be able to pause all current route
> exchange at the nearest point (surely next step) to investigate what is going
> on with the routes.
> It would be convenient to be able to pause all exchanges and also to be able
> to pause for a Route definition or a Camel context.
> Currently, suspend is no more starting new routes but finishes the current
> exchanges. The stop is no more starting the routes and not finishing the
> current exchange.
>
> Technical:
> it would likely be some option you turn on|off to have this behaviour - we
> can debate whether it should be on as default (new) or off (like now). To
> checked that it is not breaking other flow, like in Hawt.io to use the new
> behavior as default.
> {color:#262626}or a parameter on the suspend/stop methods?{color}
> {color:#262626}or create another one, as pause{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20908) Support `pause` of all route exchanges
[
https://issues.apache.org/jira/browse/CAMEL-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859760#comment-17859760
]
Claus Ibsen commented on CAMEL-20908:
-
This will only be possible if camel-debug is included for Camel to have the
debugger installed, as for production use, then to pause would just add
overhead to the routing engine that is not need there.
> Support `pause` of all route exchanges
> --
>
> Key: CAMEL-20908
> URL: https://issues.apache.org/jira/browse/CAMEL-20908
> Project: Camel
> Issue Type: New Feature
> Components: camel-management
>Reporter: Aurélien Pupier
>Priority: Major
>
> it would convenient for investigation to be able to pause all current route
> exchange at the nearest point (surely next step) to investigate what is going
> on with the routes.
> It would be convenient to be able to pause all exchanges and also to be able
> to pause for a Route definition or a Camel context.
> Currently, suspend is no more starting new routes but finishes the current
> exchanges. The stop is no more starting the routes and not finishing the
> current exchange.
>
> Technical:
> it would likely be some option you turn on|off to have this behaviour - we
> can debate whether it should be on as default (new) or off (like now). To
> checked that it is not breaking other flow, like in Hawt.io to use the new
> behavior as default.
> {color:#262626}or a parameter on the suspend/stop methods?{color}
> {color:#262626}or create another one, as pause{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20908) camel-debug - Support `pause` of all route exchanges
[
https://issues.apache.org/jira/browse/CAMEL-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20908:
Summary: camel-debug - Support `pause` of all route exchanges (was:
Support `pause` of all route exchanges)
> camel-debug - Support `pause` of all route exchanges
>
>
> Key: CAMEL-20908
> URL: https://issues.apache.org/jira/browse/CAMEL-20908
> Project: Camel
> Issue Type: New Feature
> Components: camel-management
>Reporter: Aurélien Pupier
>Priority: Major
>
> it would convenient for investigation to be able to pause all current route
> exchange at the nearest point (surely next step) to investigate what is going
> on with the routes.
> It would be convenient to be able to pause all exchanges and also to be able
> to pause for a Route definition or a Camel context.
> Currently, suspend is no more starting new routes but finishes the current
> exchanges. The stop is no more starting the routes and not finishing the
> current exchange.
>
> Technical:
> it would likely be some option you turn on|off to have this behaviour - we
> can debate whether it should be on as default (new) or off (like now). To
> checked that it is not breaking other flow, like in Hawt.io to use the new
> behavior as default.
> {color:#262626}or a parameter on the suspend/stop methods?{color}
> {color:#262626}or create another one, as pause{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20909) Camel-Aws-Kinesis: Support KCL Consumers
Andrea Cosentino created CAMEL-20909: Summary: Camel-Aws-Kinesis: Support KCL Consumers Key: CAMEL-20909 URL: https://issues.apache.org/jira/browse/CAMEL-20909 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20908) Support `pause` of all route exchanges
Aurélien Pupier created CAMEL-20908:
---
Summary: Support `pause` of all route exchanges
Key: CAMEL-20908
URL: https://issues.apache.org/jira/browse/CAMEL-20908
Project: Camel
Issue Type: New Feature
Components: camel-management
Reporter: Aurélien Pupier
it would convenient for investigation to be able to pause all current route
exchange at the nearest point (surely next step) to investigate what is going
on with the routes.
It would be convenient to be able to pause all exchanges and also to be able to
pause for a Route definition or a Camel context.
Currently, suspend is no more starting new routes but finishes the current
exchanges. The stop is no more starting the routes and not finishing the
current exchange.
Technical:
it would likely be some option you turn on|off to have this behaviour - we can
debate whether it should be on as default (new) or off (like now). To checked
that it is not breaking other flow, like in Hawt.io to use the new behavior as
default.
{color:#262626}or a parameter on the suspend/stop methods?{color}
{color:#262626}or create another one, as pause{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20794) Camel-kinesis: Kinesis producer has a very low throughtput
[ https://issues.apache.org/jira/browse/CAMEL-20794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20794: Fix Version/s: 4.7.0 (was: 4.x) > Camel-kinesis: Kinesis producer has a very low throughtput > -- > > Key: CAMEL-20794 > URL: https://issues.apache.org/jira/browse/CAMEL-20794 > Project: Camel > Issue Type: Improvement > Components: camel-aws2-kinesis >Reporter: Fan Yang >Assignee: Fan Yang >Priority: Minor > Fix For: 4.7.0 > > > Current kinesis producer can only send on record each time. It neither > supports sending records in batch, nor supports async sending. Therefore, the > throughput of kinesis producer is extremely low. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20901) camel-arangodb: Add the option to provide a custom Vertx instance
[ https://issues.apache.org/jira/browse/CAMEL-20901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-20901. - Fix Version/s: 4.7.0 (was: 4.x) Resolution: Fixed > camel-arangodb: Add the option to provide a custom Vertx instance > - > > Key: CAMEL-20901 > URL: https://issues.apache.org/jira/browse/CAMEL-20901 > Project: Camel > Issue Type: Improvement > Components: camel-arangodb >Reporter: James Netherton >Assignee: James Netherton >Priority: Minor > Fix For: 4.7.0 > > > ArangoDB 7.7.1 made is possible to provide a custom Vertx instance for the > ArangoDB client. > This is useful for Camel Quarkus where there's already an existing managed > Vertx. Currently the client will create its own Vert.x instance. Which is a > waste of resources and causes some ugly log warnings. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17668) camel-core - WireTap - Remove function to tap as new body/header
[
https://issues.apache.org/jira/browse/CAMEL-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852455#comment-17852455
]
Henrik edited comment on CAMEL-17668 at 6/24/24 11:45 AM:
--
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
was (Author: monti):
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
> camel-core - WireTap - Remove function to tap as new body/header
>
>
> Key: CAMEL-17668
> URL: https://issues.apache.org/jira/browse/CAMEL-17668
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> The wiretap should be for tapping the message as-is, and not to create new
> messages.
> Otherwise the onPrepare processor can be used to customize a new message with
> copy option enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17668) camel-core - WireTap - Remove function to tap as new body/header
[
https://issues.apache.org/jira/browse/CAMEL-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852455#comment-17852455
]
Henrik edited comment on CAMEL-17668 at 6/24/24 11:45 AM:
--
For others encountering this:
_WireTapDefinition.newExchange(Processor)_ is missing from Camel 3.16.0. It
was fixed for me by replacing this:
{code:java}
.wireTap(someUri)
.newExchange(MyProcessor())
.end()
{code}
... with this:
{code:java}
.wireTap(someUri).copy()
.onPrepare(MyProcessor())
.end()
{code}
It is somewhat described in the [Camel 3.16 upgrade guide|#_wiretap_eip]]:
{quote}Removed the new message mode as this functionality is better done by
using onPrepare processor in copy mode
{quote}
was (Author: monti):
[~davsclaus] I'm sorry to comment on a very old issue, but I finally in the
process of upgrading our old Camel 2.x stack. I haven't found any examples of
this, so: what should I replace `newExchange()` with in this instance?
{code:java}
exceptionErrorHandlers.forEach {
onException(it.exceptionToHandle)
.process(ErrorHandlerProcessor(provider(), it))
.wireTap(Endpoint.solrizeUri)
.newExchange(StatusMessage(STATUS_FAILED_KEY))
.end()
.handled(true)
.bean(providerFailedCounter, "inc()")
} {code}
> camel-core - WireTap - Remove function to tap as new body/header
>
>
> Key: CAMEL-17668
> URL: https://issues.apache.org/jira/browse/CAMEL-17668
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, eip
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.16.0
>
>
> The wiretap should be for tapping the message as-is, and not to create new
> messages.
> Otherwise the onPrepare processor can be used to customize a new message with
> copy option enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18320) camel-core - Move xtokenize language into camel-stax
[ https://issues.apache.org/jira/browse/CAMEL-18320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859648#comment-17859648 ] Henrik commented on CAMEL-18320: For anyone else encountering "NoSuchLanguageException: No language could be found for: xtokenize": I needed to include the "camel-stax" dependency to fix this when upgrading to 3.19.0. > camel-core - Move xtokenize language into camel-stax > > > Key: CAMEL-18320 > URL: https://issues.apache.org/jira/browse/CAMEL-18320 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > This language needs a StAX parser that is not out of the box in the JDK that > works, instead you need to use woostock which we provide via camel-stax. > So lets move the language there so it will work OOTB for everyone. > CEQ has a special note about this at: > https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/xml-jaxp.html#_usage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
[
https://issues.apache.org/jira/browse/CAMEL-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20906.
-
Resolution: Fixed
> NPE in
> RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
>
>
> Key: CAMEL-20906
> URL: https://issues.apache.org/jira/browse/CAMEL-20906
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> {noformat}
> Error reloading routes from file: to/Initial.yaml due to Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
> exception is ignored.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
> not sure about steps to reproduce (yet) but surely related to suspending a
> route and doing a change of the file which is tried to be automatically
> reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
[
https://issues.apache.org/jira/browse/CAMEL-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859631#comment-17859631
]
Claus Ibsen commented on CAMEL-20906:
-
I cannot reproduce this either, but I am adding a WARN log and some NPE checks
> NPE in
> RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
>
>
> Key: CAMEL-20906
> URL: https://issues.apache.org/jira/browse/CAMEL-20906
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> {noformat}
> Error reloading routes from file: to/Initial.yaml due to Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
> exception is ignored.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
> not sure about steps to reproduce (yet) but surely related to suspending a
> route and doing a change of the file which is tried to be automatically
> reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
[
https://issues.apache.org/jira/browse/CAMEL-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-20906:
---
Assignee: Claus Ibsen
> NPE in
> RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
>
>
> Key: CAMEL-20906
> URL: https://issues.apache.org/jira/browse/CAMEL-20906
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> {noformat}
> Error reloading routes from file: to/Initial.yaml due to Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
> exception is ignored.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
> not sure about steps to reproduce (yet) but surely related to suspending a
> route and doing a change of the file which is tried to be automatically
> reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20907:
Priority: Minor (was: Major)
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Minor
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17859628#comment-17859628
]
Claus Ibsen commented on CAMEL-20907:
-
Only Camel 3.22.x is limited supported until end of this year. Try this release
first.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Major
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
[
https://issues.apache.org/jira/browse/CAMEL-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20906:
Component/s: camel-core
> NPE in
> RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
>
>
> Key: CAMEL-20906
> URL: https://issues.apache.org/jira/browse/CAMEL-20906
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.7.0
>
>
> {noformat}
> Error reloading routes from file: to/Initial.yaml due to Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
> exception is ignored.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
> not sure about steps to reproduce (yet) but surely related to suspending a
> route and doing a change of the file which is tried to be automatically
> reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
[
https://issues.apache.org/jira/browse/CAMEL-20906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20906:
Fix Version/s: 4.7.0
> NPE in
> RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
>
>
> Key: CAMEL-20906
> URL: https://issues.apache.org/jira/browse/CAMEL-20906
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.6.0
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.7.0
>
>
> {noformat}
> Error reloading routes from file: to/Initial.yaml due to Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
> exception is ignored.
> java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.ServiceStatus.name()" because the return value of
> "org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
> ~[camel-support-4.6.0.jar:4.6.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
> ~[?:?]
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
> ~[?:?]
> at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
> not sure about steps to reproduce (yet) but surely related to suspending a
> route and doing a change of the file which is tried to be automatically
> reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangjian updated CAMEL-20907:
-
Summary: came-mail - In Poll Enrich EIP, get email attachments are empty
(was: came-mail:In Poll Enrich EIP, get email attachments are empty)
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Major
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20907) came-mail:In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangjian updated CAMEL-20907:
-
Description:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
// Here attachments is null
Map attachments = attachmentMessage.getAttachments();
})
.end();{code}
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange;
}))
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
Map attachments = attachmentMessage.getAttachments();
})
.end(); {code}
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
was:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://mail.server?session=#oAuthSession=false=true=mail.sub.folder=true")
.process(exchange ->
{ AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class); *// Here
attachments is null* Map
attachments = attachmentMessage.getAttachments(); }
)
.end(); {code}
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{{}mail.server{}}}?session=#oAuthSession=false=true={{{}mail.sub.folder{}}}=true",
((oldExchange, newExchange) ->
{ // Deliver the attachment to the
oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange; }
))
.process(exchange ->
{ AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class);
Map attachments =
attachmentMessage.getAttachments(); }
)
.end();
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
[jira] [Updated] (CAMEL-20907) came-mail:In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangjian updated CAMEL-20907:
-
Description:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
// Here attachments is null
Map attachments = attachmentMessage.getAttachments();
})
.end();{code}
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange;
}))
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
Map attachments = attachmentMessage.getAttachments();
})
.end(); {code}
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
was:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
// Here attachments is null
Map attachments = attachmentMessage.getAttachments();
})
.end();{code}
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{mail.server}}?session=#oAuthSession=false=true={{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange;
}))
.process(exchange -> {
AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
Map attachments = attachmentMessage.getAttachments();
})
.end(); {code}
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
> came-mail:In Poll Enrich EIP, get email attachments are empty
> -
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Major
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
>
[jira] [Updated] (CAMEL-20907) came-mail:In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangjian updated CAMEL-20907:
-
Description:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
{code:java}
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://mail.server?session=#oAuthSession=false=true=mail.sub.folder=true")
.process(exchange ->
{ AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class); *// Here
attachments is null* Map
attachments = attachmentMessage.getAttachments(); }
)
.end(); {code}
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://{{{}mail.server{}}}?session=#oAuthSession=false=true={{{}mail.sub.folder{}}}=true",
((oldExchange, newExchange) ->
{ // Deliver the attachment to the
oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange; }
))
.process(exchange ->
{ AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class);
Map attachments =
attachmentMessage.getAttachments(); }
)
.end();
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
was:
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://\{{mail.server}}?session=#oAuthSession=false=true=\{{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class);
*// Here attachments is null*
Map attachments =
attachmentMessage.getAttachments();
})
.end();
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://\{{mail.server}}?session=#oAuthSession=false=true=\{{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return
[jira] [Created] (CAMEL-20907) came-mail:In Poll Enrich EIP, get email attachments are empty
kangjian created CAMEL-20907:
Summary: came-mail:In Poll Enrich EIP, get email attachments are
empty
Key: CAMEL-20907
URL: https://issues.apache.org/jira/browse/CAMEL-20907
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.18.0
Reporter: kangjian
Let's say I need to wait for an event notification and then pull an attachments
email like this:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://\{{mail.server}}?session=#oAuthSession=false=true=\{{mail.sub.folder}}=true")
.process(exchange -> {
AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class);
*// Here attachments is null*
Map attachments =
attachmentMessage.getAttachments();
})
.end();
Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
After debugging, it was found that in Camel 3.16.x, the implementation of
DefaultAttachmentMessage.java was upgraded.
The key point is the CamelAttachmentObjects property in the ExchangeProperty,
which is placed in the Exchange property in version 3.14.x, and in the
ExtendedExchange property in version 3.16.x, which results in the loss of the
CamelAttachmentObjects property between different Exchange.
Details can be found in the link below line 274:
[https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
I tried a solution as follows:
Camel version 3.18.x
from("servlet://foo?servletName=MyServlet")
.loopDoWhile().simple("${exchangeProperty.CamelBatchComplete}
== null || ${exchangeProperty.CamelBatchComplete} == false")
.pollEnrich("imaps://\{{mail.server}}?session=#oAuthSession=false=true=\{{mail.sub.folder}}=true",
((oldExchange, newExchange) -> {
// Deliver the attachment to the oldExchange
oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
return oldExchange;
}))
.process(exchange -> {
AttachmentMessage attachmentMessage =
exchange.getIn(AttachmentMessage.class);
Map attachments =
attachmentMessage.getAttachments();
})
.end();
The above can solve the problem of not being able to get attachments, but there
will be other properties missing.
Can you help with this? If information is missing, please do not hesitate to
contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20906) NPE in RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
Aurélien Pupier created CAMEL-20906:
---
Summary: NPE in
RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
Key: CAMEL-20906
URL: https://issues.apache.org/jira/browse/CAMEL-20906
Project: Camel
Issue Type: Bug
Affects Versions: 4.6.0
Reporter: Aurélien Pupier
{noformat}
Error reloading routes from file: to/Initial.yaml due to Cannot invoke
"org.apache.camel.ServiceStatus.name()" because the return value of
"org.apache.camel.spi.RouteController.getRouteStatus(String)" is null. This
exception is ignored.
java.lang.NullPointerException: Cannot invoke
"org.apache.camel.ServiceStatus.name()" because the return value of
"org.apache.camel.spi.RouteController.getRouteStatus(String)" is null
at
org.apache.camel.support.RouteWatcherReloadStrategy.onRouteReload(RouteWatcherReloadStrategy.java:300)
~[camel-support-4.6.0.jar:4.6.0]
at
org.apache.camel.support.RouteWatcherReloadStrategy.lambda$doStart$1(RouteWatcherReloadStrategy.java:154)
~[camel-support-4.6.0.jar:4.6.0]
at
org.apache.camel.support.FileWatcherResourceReloadStrategy$WatchFileChangesTask.run(FileWatcherResourceReloadStrategy.java:311)
~[camel-support-4.6.0.jar:4.6.0]
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
~[?:?]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
~[?:?]
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
~[?:?]
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?] {noformat}
not sure about steps to reproduce (yet) but surely related to suspending a
route and doing a change of the file which is tried to be automatically reloaded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
