[jira] [Resolved] (CAMEL-20643) camel-opentelemetry - OpenTelemetryTracingStrategy does not propagate OpenTelemetry Context in some cases
[
https://issues.apache.org/jira/browse/CAMEL-20643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth resolved CAMEL-20643.
---
Resolution: Fixed
> camel-opentelemetry - OpenTelemetryTracingStrategy does not propagate
> OpenTelemetry Context in some cases
> -
>
> Key: CAMEL-20643
> URL: https://issues.apache.org/jira/browse/CAMEL-20643
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry
>Affects Versions: 4.5.0
>Reporter: John Poth
>Assignee: John Poth
>Priority: Major
> Fix For: 4.6.0
>
>
> When the excludePatterns is set in some cases, our
> OpenTelemetryTracingStrategy does not propagate the OpenTelemetry Context.
> Having the current Context correctly set enables users to use the
> `io.opentelemetry.instrumentation.annotations.@WithSpan` annotation to create
> custom Spans. This is particularly useful when the user wants to create a
> Span only for a particular method within the Process even though it's
> disabled e.g:
>
> {code:java}
> openTelemetryTracingStrategy.setExcludePatterns("longRunningProcess")
>...
>.process(exchange -> {
> // No Span created by Camel because excluded
>longRunningProcess();
> }).id("longRunningProcess")
> ...
>private void longRunningProcess() {
> // no Span
> firstMethod();
> // custom Span
> secondMethod();
>}
>private void firstMethod() {
> // no Span
>}
>@WithSpan
>private void secondMethod() {
> // no Span
>}
> {code}
> It would be nice to add an option in OpenTelemetryTracingStrategy to
> propagate the OpenTelemetry context even though the Processor isn't traced.
> Thanks !
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20643) camel-opentelemetry - OpenTelemetryTracingStrategy does not propagate OpenTelemetry Context in some cases
John Poth created CAMEL-20643:
-
Summary: camel-opentelemetry - OpenTelemetryTracingStrategy does
not propagate OpenTelemetry Context in some cases
Key: CAMEL-20643
URL: https://issues.apache.org/jira/browse/CAMEL-20643
Project: Camel
Issue Type: Improvement
Components: camel-opentelemetry
Affects Versions: 4.5.0
Reporter: John Poth
Assignee: John Poth
Fix For: 4.6.0
When the excludePatterns is set in some cases, our OpenTelemetryTracingStrategy
does not propagate the OpenTelemetry Context. Having the current Context
correctly set enables users to use the
`io.opentelemetry.instrumentation.annotations.@WithSpan` annotation to create
custom Spans. This is particularly useful when the user wants to create a Span
only for a particular method within the Process even though it's disabled e.g:
{code:java}
openTelemetryTracingStrategy.setExcludePatterns("longRunningProcess")
...
.process(exchange -> {
// No Span created by Camel because excluded
longRunningProcess();
}).id("longRunningProcess")
...
private void longRunningProcess() {
// no Span
firstMethod();
// custom Span
secondMethod();
}
private void firstMethod() {
// no Span
}
@WithSpan
private void secondMethod() {
// no Span
}
{code}
It would be nice to add an option in OpenTelemetryTracingStrategy to propagate
the OpenTelemetry context even though the Processor isn't traced.
Thanks !
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19667) camel-tracing: Context is not propagated from exchange header to OpenTelemetry Context
[
https://issues.apache.org/jira/browse/CAMEL-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829640#comment-17829640
]
John Poth commented on CAMEL-19667:
---
Unfortunately, naively putting,
{code:java}
from("timer:tick?period=5s)
.process("myProcessor");
public class MyProcessor implements Processor {
@Override
public void process(Exchange exchange) {
// OpenTelemetry Context is here
}
}
{code}
In a Unit Test does not reproduce the issue and the Context is correctly
propagated. We also have an OpenTelemetry example using Kafka [1] which
correctly propagates the Context.
[1]
[https://github.com/apache/camel-spring-boot-examples/tree/main/opentelemetry]
> camel-tracing: Context is not propagated from exchange header to
> OpenTelemetry Context
> --
>
> Key: CAMEL-19667
> URL: https://issues.apache.org/jira/browse/CAMEL-19667
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry, camel-tracing
>Affects Versions: 3.20.5, 3.20.6, 3.21.0, 4.0-M3
>Reporter: Roman Kvasnytskyi
>Priority: Major
> Labels: bug, opentelemetry, tracing
> Fix For: 4.x
>
> Attachments: screenshot-1.png
>
>
> I am using OpenTelemetry Agent for tracing along with
> camel-opentelemetry-starter that configures OpenTelemetryTracer for Camel
> aligned with camel-tracing.
> I see my spans for Camel inside a single trace, but after control is passed
> to the Processor process method next spans are disassociated from the trace
> and are created in the separate trace.
> The tracing context does not seem to get propagated, and the resulting spans
> end up being disassociated. For example:
> {code:java}
> from("timer:tick?period=5s)
> .process("myProcessor");
> {code}
> {code:java}
> public class MyProcessor implements Processor {
> private final HttpClient someClient = new HttpClient();
> @Override
> public void process(Exchange exchange) {
> // http client is instrumented and also produces spans
> someClient.get('/example');
> }
> }
> {code}
> This results in 2 spans. One for timer:tick & another for a client call. The
> problem is that the parent span for client calls is not set, so they appear
> as 2 distinct traces.
> My exchange headers contain traceparent header with all data which should be
> put inside the OpenTelemetry context, but they do not.
> I have come up with a workaround. The idea is trivial - get traceparent
> header if it is present in exchange, parse trace metadata from it, create a
> SpanContext object, and put it as a parent for the current OpenTelemetry
> context.
> It looks like this:
> {code:java}
> public class TraceEnrichingProcessor implements Processor {
> private final Processor delegate;
> public TraceEnrichingProcessor(Processor delegate) {
> this.delegate = delegate;
> }
> @Override
> public void process(Exchange exchange) throws Exception {
> // Get the existing traceparent header from the Exchange
> String traceparent = exchange.getIn().getHeader("traceparent",
> String.class);
> if (traceparent != null && !traceparent.isEmpty()) {
> // Extract the traceId, parentSpanId and sampleFlag
> String[] parts = traceparent.split("-");
> String traceId = parts[1];
> String parentSpanId = parts[2];
> boolean isSampled = parts[3].equals("01");
> // Create the parent SpanContext
> SpanContext parentContext = SpanContext.create(
> traceId,
> parentSpanId,
> isSampled ? TraceFlags.getSampled() : TraceFlags.getDefault(),
> TraceState.getDefault()
> );
> // Attach the parent SpanContext to the current Context
> try (Scope scope =
> Context.current().with(Span.wrap(parentContext)).makeCurrent()) {
> // Now, the current Context has the parent SpanContext
> attached,
> // and any new spans created within this scope will use it as
> their parent
>
> // Pass control to the delegate processor
> delegate.process(exchange);
> }
> } else {
> // If no traceparent header is found, just delegate without
> modifying the Context
> delegate.process(exchange);
> }
> }
> } {code}
> Inside OpenTelemetry Agent, they dropped support of Camel 3.x+, because Camel
> provides its module for tracing, and they will not help with it.
> [Link|https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/4052]
> I wonder if that can be done inside Camel to propagate context from the
[jira] [Commented] (CAMEL-19469) camel-opentelemetry: Context not propagated correctly when tracing bean or processor invocations with @WithSpan
[
https://issues.apache.org/jira/browse/CAMEL-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829634#comment-17829634
]
John Poth commented on CAMEL-19469:
---
I'm also curious about the use case. The
[OpenTelemetryTracingStrategy|https://github.com/apache/camel/blob/main/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracingStrategy.java#L64]
already creates a Span for Processors. It seems adding @WithSpan would just
create another identical Span.
Unfortunately, naively putting,
{code:java}
// Some comments here
from("timer:tick?period=5s)
.process("myProcessor");
public class MyProcessor implements Processor {
@WithSpan
@Override
public void process(Exchange exchange) {
// Useful work here...
}
}
{code}
In a Unit test does not reproduce the issue and the Context is correctly
propagated.
> camel-opentelemetry: Context not propagated correctly when tracing bean or
> processor invocations with @WithSpan
> ---
>
> Key: CAMEL-19469
> URL: https://issues.apache.org/jira/browse/CAMEL-19469
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry
>Affects Versions: 3.20.5, 4.0-M3
>Reporter: James Netherton
>Priority: Minor
>
> OpenTelemetry enables you to trace arbitrary method invocations by tagging
> them with the @WithSpan annotation:
> https://opentelemetry.io/docs/instrumentation/java/automatic/annotations/#creating-spans-around-methods-with-withspan
> For some scenarios, the tracing context does not seem to get propagated and
> the resulting spans end up being disassociated. For example:
> {code}
> from("timer:tick?period=5s)
> .process("myProcessor");
> {code}
> {code}
> public class MyProcessor implements Processor {
> @WithSpan
> @Override
> public void process(Exchange exchange) {
> // Useful work here...
> }
> }
> {code}
> This results in 2 spans. One for timer:tick & another for MyProcessor. The
> problem is that the parent span for MyProcessor is not set, so they appear as
> 2 distinct traces.
> There is a workaround where you can configure the route like this and the
> span hierarchy ends up being correct:
> {code}
> from("timer:tick?period=5s")
> .to("direct:start");
> from("direct:start")
> .process("myProcessor");
> {code}
> There's some more background in the original issue reported on Camel Quarkus:
> https://github.com/apache/camel-quarkus/issues/4981
> There's also a reproducer project here:
> https://github.com/jamesnetherton/camel-opentelemetry-demo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20567) Add support for restConfiguration in XML DSL IO
John Poth created CAMEL-20567: - Summary: Add support for restConfiguration in XML DSL IO Key: CAMEL-20567 URL: https://issues.apache.org/jira/browse/CAMEL-20567 Project: Camel Issue Type: Improvement Components: camel-xml-io Reporter: John Poth -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20567) Add support for restConfiguration in XML DSL IO
[ https://issues.apache.org/jira/browse/CAMEL-20567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-20567: - Assignee: John Poth > Add support for restConfiguration in XML DSL IO > --- > > Key: CAMEL-20567 > URL: https://issues.apache.org/jira/browse/CAMEL-20567 > Project: Camel > Issue Type: Improvement > Components: camel-xml-io >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20411) camel-mongodb: Add findAndModify Operation
[ https://issues.apache.org/jira/browse/CAMEL-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818377#comment-17818377 ] John Poth commented on CAMEL-20411: --- Thanks! Forgot to assign it to myself :) > camel-mongodb: Add findAndModify Operation > -- > > Key: CAMEL-20411 > URL: https://issues.apache.org/jira/browse/CAMEL-20411 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.x > > > Seems like it's implemented in three methods in the underlying MangoDB driver > Java API: > [findOneAndUpdate|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1529], > > [findOneAndReplace|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1452], > > [findOneAndDelete|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1397]. > I think it would make sense to mirror that and add three > [_MongoDbOperations_|https://github.com/apache/camel/blob/main/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbOperation.java#L19] > in Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20411) camel-mongodb: Add findAndModify Operation
[ https://issues.apache.org/jira/browse/CAMEL-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-20411: - Assignee: John Poth > camel-mongodb: Add findAndModify Operation > -- > > Key: CAMEL-20411 > URL: https://issues.apache.org/jira/browse/CAMEL-20411 > Project: Camel > Issue Type: Improvement > Components: camel-mongodb >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.x > > > Seems like it's implemented in three methods in the underlying MangoDB driver > Java API: > [findOneAndUpdate|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1529], > > [findOneAndReplace|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1452], > > [findOneAndDelete|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1397]. > I think it would make sense to mirror that and add three > [_MongoDbOperations_|https://github.com/apache/camel/blob/main/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbOperation.java#L19] > in Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20411) camel-mongodb: Add findAndModify Operation
John Poth created CAMEL-20411: - Summary: camel-mongodb: Add findAndModify Operation Key: CAMEL-20411 URL: https://issues.apache.org/jira/browse/CAMEL-20411 Project: Camel Issue Type: Improvement Components: camel-mongodb Reporter: John Poth Seems like it's implemented in three methods in the underlying MangoDB driver Java API: [findOneAndUpdate|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1529], [findOneAndReplace|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1452], [findOneAndDelete|https://github.com/mongodb/mongo-java-driver/blob/master/driver-sync/src/main/com/mongodb/client/MongoCollection.java#L1397]. I think it would make sense to mirror that and add three [_MongoDbOperations_|https://github.com/apache/camel/blob/main/components/camel-mongodb/src/main/java/org/apache/camel/component/mongodb/MongoDbOperation.java#L19] in Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20290) Camel Spring Boot Starters configuration in Java and ConfigurationProperties conflict
[
https://issues.apache.org/jira/browse/CAMEL-20290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth updated CAMEL-20290:
--
Affects Version/s: 4.x
(was: 4.3.0)
> Camel Spring Boot Starters configuration in Java and ConfigurationProperties
> conflict
> -
>
> Key: CAMEL-20290
> URL: https://issues.apache.org/jira/browse/CAMEL-20290
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Affects Versions: 4.x
>Reporter: John Poth
>Priority: Major
>
> It would be cool if we could find a way to reconcile:
> 1) Starter configurations via _ConfigurationProperties_
> 2) Stater configurations in Java
> in a way that's clear for the user. For example the following configuration
> attempt in Java fails :
> {code:java}
> @Bean("http")
> public HttpComponent http(){
> return ComponentsBuilderFactory.http()
> .connectionsPerRoute(1).
> .build();
> }
> {code}
> As the _ConfigurationProperties_ kicks in afterwards and the
> _connectionsPerRoute_ will be set to the default 20 at runtime. The user can
> disable this by setting camel.component.http.customizer.enabled=false but
> that removes the ability to configure the component from
> application.properties files etc...
> A workaround could be something like:
> {code:java}
> @Bean("http")
> public HttpComponent myHttp(HttpComponentConfiguration config,
> CamelContext camelContext) {
> HttpComponent httpComponent = new HttpComponent();
> httpComponent.setCamelContext(camelContext);
> // copy external configuration
> CamelPropertiesHelper.copyProperties(camelContext, config,
> httpComponent);
> // Custom config
> httpComponent.setConnectionsPerRoute(1);
> return httpComponent;
> }
> {code}
> It would be also cool to have a clear priority order e.g if
> _connectionsPerRoute_ is set in Java and application.properties which takes
> precedence. Also, configuring multiple instances of the same component comes
> to mind.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20290) Camel Spring Boot Starters configuration in Java and ConfigurationProperties conflict
John Poth created CAMEL-20290:
-
Summary: Camel Spring Boot Starters configuration in Java and
ConfigurationProperties conflict
Key: CAMEL-20290
URL: https://issues.apache.org/jira/browse/CAMEL-20290
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot
Affects Versions: 4.3.0
Reporter: John Poth
It would be cool if we could find a way to reconcile:
1) Starter configurations via _ConfigurationProperties_
2) Stater configurations in Java
in a way that's clear for the user. For example the following configuration
attempt in Java fails :
{code:java}
@Bean("http")
public HttpComponent http(){
return ComponentsBuilderFactory.http()
.connectionsPerRoute(1).
.build();
}
{code}
As the _ConfigurationProperties_ kicks in afterwards and the
_connectionsPerRoute_ will be set to the default 20 at runtime. The user can
disable this by setting camel.component.http.customizer.enabled=false but that
removes the ability to configure the component from application.properties
files etc...
A workaround could be something like:
{code:java}
@Bean("http")
public HttpComponent myHttp(HttpComponentConfiguration config, CamelContext
camelContext) {
HttpComponent httpComponent = new HttpComponent();
httpComponent.setCamelContext(camelContext);
// copy external configuration
CamelPropertiesHelper.copyProperties(camelContext, config,
httpComponent);
// Custom config
httpComponent.setConnectionsPerRoute(1);
return httpComponent;
}
{code}
It would be also cool to have a clear priority order e.g if
_connectionsPerRoute_ is set in Java and application.properties which takes
precedence. Also, configuring multiple instances of the same component comes to
mind.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20261) camel-http ignoreCookies option value has been renamed
[ https://issues.apache.org/jira/browse/CAMEL-20261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-20261: - Assignee: John Poth > camel-http ignoreCookies option value has been renamed > --- > > Key: CAMEL-20261 > URL: https://issues.apache.org/jira/browse/CAMEL-20261 > Project: Camel > Issue Type: Improvement >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 4.0.4, 4.4.0 > > > httpcomponents-client has > [changed|https://github.com/apache/httpcomponents-client/commit/0812192f46046068bb692355795b8071cb7eab09] > the cookieSpec option values. We should update our docs to reflect this. We > should also make it more explicit that the option only affects cookies > managed through the CookieStore; not the ones directly set in the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20261) camel-http ignoreCookies option value has been renamed
[ https://issues.apache.org/jira/browse/CAMEL-20261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-20261: -- Description: httpcomponents-client has [changed|https://github.com/apache/httpcomponents-client/commit/0812192f46046068bb692355795b8071cb7eab09] the cookieSpec option values. We should update our docs to reflect this. We should also make it more explicit that the option only affects cookies managed through the CookieStore; not the ones directly set in the header. (was: httpcomponents-client has [changed|[http://example.com|https://github.com/apache/httpcomponents-client/commit/0812192f46046068bb692355795b8071cb7eab09]] the cookieSpec option values. We should update our docs to reflect this. We should also make it more explicit that the option only affects cookies managed through the CookieStore; not the ones directly set in the header.) > camel-http ignoreCookies option value has been renamed > --- > > Key: CAMEL-20261 > URL: https://issues.apache.org/jira/browse/CAMEL-20261 > Project: Camel > Issue Type: Improvement >Reporter: John Poth >Priority: Minor > > httpcomponents-client has > [changed|https://github.com/apache/httpcomponents-client/commit/0812192f46046068bb692355795b8071cb7eab09] > the cookieSpec option values. We should update our docs to reflect this. We > should also make it more explicit that the option only affects cookies > managed through the CookieStore; not the ones directly set in the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20261) camel-http ignoreCookies option value has been renamed
John Poth created CAMEL-20261: - Summary: camel-http ignoreCookies option value has been renamed Key: CAMEL-20261 URL: https://issues.apache.org/jira/browse/CAMEL-20261 Project: Camel Issue Type: Improvement Reporter: John Poth httpcomponents-client has [changed|[http://example.com|https://github.com/apache/httpcomponents-client/commit/0812192f46046068bb692355795b8071cb7eab09]] the cookieSpec option values. We should update our docs to reflect this. We should also make it more explicit that the option only affects cookies managed through the CookieStore; not the ones directly set in the header. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20238) Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
[
https://issues.apache.org/jira/browse/CAMEL-20238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth updated CAMEL-20238:
--
Fix Version/s: Future
> Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
>
>
> Key: CAMEL-20238
> URL: https://issues.apache.org/jira/browse/CAMEL-20238
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot-starters
>Reporter: John Poth
>Assignee: John Poth
>Priority: Minor
> Fix For: Future
>
>
> I think it would be cool to add _spring-boot-starter-jdbc_ as a dependency to
> our {_}camel-spring-jdbc-starter{_}.
> This would bring in the Hikari connection pool and would create a pooled
> datasource by default instead of having the need to set
> 'spring.datasource.type' correctly and not having connection pooling out of
> the box by default.
> I think this is more inline with the opinionated SpringBoot way and there are
> probably other camel starters that could benefit from this logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20238) Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
[
https://issues.apache.org/jira/browse/CAMEL-20238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth resolved CAMEL-20238.
---
Resolution: Fixed
> Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
>
>
> Key: CAMEL-20238
> URL: https://issues.apache.org/jira/browse/CAMEL-20238
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot-starters
>Reporter: John Poth
>Assignee: John Poth
>Priority: Minor
> Fix For: Future
>
>
> I think it would be cool to add _spring-boot-starter-jdbc_ as a dependency to
> our {_}camel-spring-jdbc-starter{_}.
> This would bring in the Hikari connection pool and would create a pooled
> datasource by default instead of having the need to set
> 'spring.datasource.type' correctly and not having connection pooling out of
> the box by default.
> I think this is more inline with the opinionated SpringBoot way and there are
> probably other camel starters that could benefit from this logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20238) Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
[
https://issues.apache.org/jira/browse/CAMEL-20238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth reassigned CAMEL-20238:
-
Assignee: John Poth
> Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
>
>
> Key: CAMEL-20238
> URL: https://issues.apache.org/jira/browse/CAMEL-20238
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot-starters
>Reporter: John Poth
>Assignee: John Poth
>Priority: Minor
>
> I think it would be cool to add _spring-boot-starter-jdbc_ as a dependency to
> our {_}camel-spring-jdbc-starter{_}.
> This would bring in the Hikari connection pool and would create a pooled
> datasource by default instead of having the need to set
> 'spring.datasource.type' correctly and not having connection pooling out of
> the box by default.
> I think this is more inline with the opinionated SpringBoot way and there are
> probably other camel starters that could benefit from this logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20238) Add spring-boot-starter-jdbc dependency to camel-spring-jdbc-starter
John Poth created CAMEL-20238:
-
Summary: Add spring-boot-starter-jdbc dependency to
camel-spring-jdbc-starter
Key: CAMEL-20238
URL: https://issues.apache.org/jira/browse/CAMEL-20238
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot-starters
Reporter: John Poth
I think it would be cool to add _spring-boot-starter-jdbc_ as a dependency to
our {_}camel-spring-jdbc-starter{_}.
This would bring in the Hikari connection pool and would create a pooled
datasource by default instead of having the need to set
'spring.datasource.type' correctly and not having connection pooling out of the
box by default.
I think this is more inline with the opinionated SpringBoot way and there are
probably other camel starters that could benefit from this logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18915) Upgrade fhir component
[ https://issues.apache.org/jira/browse/CAMEL-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-18915. --- Resolution: Fixed > Upgrade fhir component > -- > > Key: CAMEL-18915 > URL: https://issues.apache.org/jira/browse/CAMEL-18915 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 4.0 > > > Would be an opportunity to upgrade FHIR in camel-fhir to a new major version > 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18915) Upgrade fhir component
[ https://issues.apache.org/jira/browse/CAMEL-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685191#comment-17685191 ] John Poth commented on CAMEL-18915: --- Sure, done ! > Upgrade fhir component > -- > > Key: CAMEL-18915 > URL: https://issues.apache.org/jira/browse/CAMEL-18915 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 4.0 > > > Would be an opportunity to upgrade FHIR in camel-fhir to a new major version > 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18915) Upgrade fhir component
[ https://issues.apache.org/jira/browse/CAMEL-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-18915: - Assignee: John Poth > Upgrade fhir component > -- > > Key: CAMEL-18915 > URL: https://issues.apache.org/jira/browse/CAMEL-18915 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 4.0 > > > Would be an opportunity to upgrade FHIR in camel-fhir to a new major version > 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18915) Upgrade fhir component
[ https://issues.apache.org/jira/browse/CAMEL-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677236#comment-17677236 ] John Poth commented on CAMEL-18915: --- Yes assigning it to me if that's ok > Upgrade fhir component > -- > > Key: CAMEL-18915 > URL: https://issues.apache.org/jira/browse/CAMEL-18915 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-fhir >Reporter: John Poth >Priority: Major > Fix For: 4.0 > > > Would be an opportunity to upgrade FHIR in camel-fhir to a new major version > 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18915) Upgrade fhir component
[ https://issues.apache.org/jira/browse/CAMEL-18915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-18915: -- Issue Type: Dependency upgrade (was: Improvement) > Upgrade fhir component > -- > > Key: CAMEL-18915 > URL: https://issues.apache.org/jira/browse/CAMEL-18915 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-fhir >Reporter: John Poth >Priority: Major > Fix For: 4.0 > > > Would be an opportunity to upgrade FHIR in camel-fhir to a new major version > 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18915) Upgrade fhir component
John Poth created CAMEL-18915: - Summary: Upgrade fhir component Key: CAMEL-18915 URL: https://issues.apache.org/jira/browse/CAMEL-18915 Project: Camel Issue Type: Improvement Components: camel-fhir Reporter: John Poth Fix For: 4.0 Would be an opportunity to upgrade FHIR in camel-fhir to a new major version 4.2.0 --> 6.2.4 (some breaking changes) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17933) Document how to configure camel spring boot starters
[ https://issues.apache.org/jira/browse/CAMEL-17933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17933. --- Resolution: Fixed > Document how to configure camel spring boot starters > > > Key: CAMEL-17933 > URL: https://issues.apache.org/jira/browse/CAMEL-17933 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters, documentation >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > It would be cool to add a section on the website describing the different > ways to configure Components, Dataformats and languages in camel spring boot > applications. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17933) Document how to configure camel spring boot starters
[ https://issues.apache.org/jira/browse/CAMEL-17933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-17933: - Assignee: John Poth > Document how to configure camel spring boot starters > > > Key: CAMEL-17933 > URL: https://issues.apache.org/jira/browse/CAMEL-17933 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters, documentation >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > It would be cool to add a section on the website describing the different > ways to configure Components, Dataformats and languages in camel spring boot > applications. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17933) Document how to configure camel spring boot starters
John Poth created CAMEL-17933: - Summary: Document how to configure camel spring boot starters Key: CAMEL-17933 URL: https://issues.apache.org/jira/browse/CAMEL-17933 Project: Camel Issue Type: Improvement Components: camel-spring-boot-starters, documentation Reporter: John Poth It would be cool to add a section on the website describing the different ways to configure Components, Dataformats and languages in camel spring boot applications. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17933) Document how to configure camel spring boot starters
[ https://issues.apache.org/jira/browse/CAMEL-17933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-17933: -- Priority: Minor (was: Major) > Document how to configure camel spring boot starters > > > Key: CAMEL-17933 > URL: https://issues.apache.org/jira/browse/CAMEL-17933 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot-starters, documentation >Reporter: John Poth >Priority: Minor > > It would be cool to add a section on the website describing the different > ways to configure Components, Dataformats and languages in camel spring boot > applications. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17932) EndpointInject happens before CamelContextConfiguration#beforeApplicationStart
John Poth created CAMEL-17932:
-
Summary: EndpointInject happens before
CamelContextConfiguration#beforeApplicationStart
Key: CAMEL-17932
URL: https://issues.apache.org/jira/browse/CAMEL-17932
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot, tests
Reporter: John Poth
Currently something like this fails in camel-spring-boot tests:
{code:java}
@EndpointInject("mock:result")
MockEndpoint mock;
@Test
public void testComponentConfigured() {
// this fails
assertTrue(mock.isLog());
}
@Bean
CamelContextConfiguration contextConfiguration() {
return new CamelContextConfiguration() {
@Override
public void beforeApplicationStart(CamelContext context) {
MockComponent mock = new MockComponent(context);
mock.setLog(true);
context.addComponent("mock", mock);
}
@Override
public void afterApplicationStart(CamelContext camelContext) {
//do nothing here
}
};
}
{code}
This is because the wiring for *@EndpointInject* happens before
*CamelContextConfiguration#beforeApplicationStart*. Workaround is to configure
the component via @Bean
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (CAMEL-17845) Create Kafka server once during IT
[ https://issues.apache.org/jira/browse/CAMEL-17845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514113#comment-17514113 ] John Poth commented on CAMEL-17845: --- Yep, closing ... > Create Kafka server once during IT > -- > > Key: CAMEL-17845 > URL: https://issues.apache.org/jira/browse/CAMEL-17845 > Project: Camel > Issue Type: Test > Components: camel-kafka, camel-test, camel-test-infra >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.17.0 > > > It would be cool to create a singleton Kafka server when running integration > tests and not recreate a Kafka instance for each test class -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17845) Create Kafka server once during IT
[ https://issues.apache.org/jira/browse/CAMEL-17845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17845. --- Resolution: Fixed > Create Kafka server once during IT > -- > > Key: CAMEL-17845 > URL: https://issues.apache.org/jira/browse/CAMEL-17845 > Project: Camel > Issue Type: Test > Components: camel-kafka, camel-test, camel-test-infra >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.17.0 > > > It would be cool to create a singleton Kafka server when running integration > tests and not recreate a Kafka instance for each test class -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17845) Create Kafka server once during IT
[ https://issues.apache.org/jira/browse/CAMEL-17845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513280#comment-17513280 ] John Poth commented on CAMEL-17845: --- Hi [~orpiske]! Looks like they were failing before too? https://ci-builds.apache.org/job/Camel/job/Apache%20Camel/job/main/203/ There's definitely a problem though. I'll try to take a look! > Create Kafka server once during IT > -- > > Key: CAMEL-17845 > URL: https://issues.apache.org/jira/browse/CAMEL-17845 > Project: Camel > Issue Type: Test > Components: camel-kafka, camel-test, camel-test-infra >Reporter: John Poth >Assignee: John Poth >Priority: Minor > > It would be cool to create a singleton Kafka server when running integration > tests and not recreate a Kafka instance for each test class -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17845) Create Kafka server once during IT
John Poth created CAMEL-17845: - Summary: Create Kafka server once during IT Key: CAMEL-17845 URL: https://issues.apache.org/jira/browse/CAMEL-17845 Project: Camel Issue Type: Test Components: camel-kafka, camel-test, camel-test-infra Reporter: John Poth Assignee: John Poth It would be cool to create a singleton Kafka server when running integration tests and not recreate a Kafka instance for each test class -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17838) Create FHIR server once during tests
John Poth created CAMEL-17838: - Summary: Create FHIR server once during tests Key: CAMEL-17838 URL: https://issues.apache.org/jira/browse/CAMEL-17838 Project: Camel Issue Type: Test Components: camel-fhir, camel-test-infra, tests Reporter: John Poth Assignee: John Poth It would be cool to create a singleton FHIR server when running tests and not recreate the server for each test class -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17805) add tests in camel-kafka-starter
[ https://issues.apache.org/jira/browse/CAMEL-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17805. --- Resolution: Fixed > add tests in camel-kafka-starter > > > Key: CAMEL-17805 > URL: https://issues.apache.org/jira/browse/CAMEL-17805 > Project: Camel > Issue Type: Test > Components: camel-kafka, camel-spring-boot, tests >Reporter: John Poth >Assignee: John Poth >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17805) add tests in camel-kafka-starter
[ https://issues.apache.org/jira/browse/CAMEL-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-17805: - Assignee: John Poth > add tests in camel-kafka-starter > > > Key: CAMEL-17805 > URL: https://issues.apache.org/jira/browse/CAMEL-17805 > Project: Camel > Issue Type: Test > Components: camel-kafka, camel-spring-boot, tests >Reporter: John Poth >Assignee: John Poth >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17805) add tests in camel-kafka-starter
John Poth created CAMEL-17805: - Summary: add tests in camel-kafka-starter Key: CAMEL-17805 URL: https://issues.apache.org/jira/browse/CAMEL-17805 Project: Camel Issue Type: Test Components: camel-kafka, camel-spring-boot, tests Reporter: John Poth -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17745. --- Resolution: Fixed > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (CAMEL-17745) camel-spring-boot - AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-17745: - Assignee: John Poth > camel-spring-boot - AutoConfigurations models aren't updated > > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17743) camel-spring-boot - Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17743. --- Resolution: Fixed > camel-spring-boot - Schema generation fails for > Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Task > Components: camel-core >Affects Versions: 3.16.0 >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.16.0 > > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
[ https://issues.apache.org/jira/browse/CAMEL-17745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501287#comment-17501287 ] John Poth commented on CAMEL-17745: --- https://github.com/apache/camel-spring-boot/pull/454 > camel-core-starter AutoConfigurations models aren't updated > --- > > Key: CAMEL-17745 > URL: https://issues.apache.org/jira/browse/CAMEL-17745 > Project: Camel > Issue Type: Bug >Reporter: John Poth >Priority: Major > > I think this relates to > [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be > worth creating a "real" camel-core-starter and a new > camel-core-engine-starter. > Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17743) SB2 Schema generation fails for Resilience4jConfigurationCommon
[ https://issues.apache.org/jira/browse/CAMEL-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501288#comment-17501288 ] John Poth commented on CAMEL-17743: --- https://github.com/apache/camel/pull/7107 > SB2 Schema generation fails for Resilience4jConfigurationCommon > --- > > Key: CAMEL-17743 > URL: https://issues.apache.org/jira/browse/CAMEL-17743 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: John Poth >Assignee: John Poth >Priority: Major > > SB2 schema generation fails for Resilience4jConfigurationDefinition because > the javaType is set to > [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] > when > [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] > the schema while a String is expected. This also gives a > ClassNotFoundException as the type isn't present on the classpath in SB2 > starters. Removing the problematic javaTypes for now. Thanks ! > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17745) camel-core-starter AutoConfigurations models aren't updated
John Poth created CAMEL-17745: - Summary: camel-core-starter AutoConfigurations models aren't updated Key: CAMEL-17745 URL: https://issues.apache.org/jira/browse/CAMEL-17745 Project: Camel Issue Type: Bug Reporter: John Poth I think this relates to [CAMEL-16192|https://issues.apache.org/jira/browse/CAMEL-16192]. It may be worth creating a "real" camel-core-starter and a new camel-core-engine-starter. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17744) SB actuator-http-metrics example fails
[
https://issues.apache.org/jira/browse/CAMEL-17744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17501282#comment-17501282
]
John Poth commented on CAMEL-17744:
---
Resolved with
https://github.com/apache/camel-spring-boot/commit/07b410a73855b4ecced4de2bb675466bd53ec5d2
> SB actuator-http-metrics example fails
> --
>
> Key: CAMEL-17744
> URL: https://issues.apache.org/jira/browse/CAMEL-17744
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: John Poth
>Assignee: John Poth
>Priority: Major
>
> Running the example from scratch gives:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Cannot configure option
> [apiContextListing] with value [false] as the bean class
> [org.apache.camel.spi.RestConfiguration] has no suitable setter method, or
> not possible to lookup a bean with the id [false] in Spring Boot registry
> at
> org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
> ~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
> ~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
> ~[spring-beans-5.3.16.jar:5.3.16]
> ... 37 common frames omitted
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (CAMEL-17744) SB actuator-http-metrics example fails
[
https://issues.apache.org/jira/browse/CAMEL-17744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth resolved CAMEL-17744.
---
Resolution: Fixed
> SB actuator-http-metrics example fails
> --
>
> Key: CAMEL-17744
> URL: https://issues.apache.org/jira/browse/CAMEL-17744
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: John Poth
>Assignee: John Poth
>Priority: Major
>
> Running the example from scratch gives:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Cannot configure option
> [apiContextListing] with value [false] as the bean class
> [org.apache.camel.spi.RestConfiguration] has no suitable setter method, or
> not possible to lookup a bean with the id [false] in Spring Boot registry
> at
> org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
> ~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
> ~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:na]
> at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
> at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
> ~[spring-beans-5.3.16.jar:5.3.16]
> ... 37 common frames omitted
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17744) SB actuator-http-metrics example fails
John Poth created CAMEL-17744:
-
Summary: SB actuator-http-metrics example fails
Key: CAMEL-17744
URL: https://issues.apache.org/jira/browse/CAMEL-17744
Project: Camel
Issue Type: Bug
Components: examples
Reporter: John Poth
Assignee: John Poth
Running the example from scratch gives:
{code:java}
Caused by: java.lang.IllegalArgumentException: Cannot configure option
[apiContextListing] with value [false] as the bean class
[org.apache.camel.spi.RestConfiguration] has no suitable setter method, or not
possible to lookup a bean with the id [false] in Spring Boot registry
at
org.apache.camel.spring.boot.util.CamelPropertiesHelper.setCamelProperties(CamelPropertiesHelper.java:125)
~[camel-spring-boot-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
at
org.apache.camel.model.rest.springboot.RestConfigurationDefinitionAutoConfiguration.configureRestConfigurationDefinition(RestConfigurationDefinitionAutoConfiguration.java:72)
~[camel-core-starter-3.16.0-SNAPSHOT.jar:3.16.0-SNAPSHOT]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[na:na]
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[na:na]
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:na]
at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
~[spring-beans-5.3.16.jar:5.3.16]
... 37 common frames omitted
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (CAMEL-17743) SB2 Schema generation fails for Resilience4jConfigurationCommon
John Poth created CAMEL-17743: - Summary: SB2 Schema generation fails for Resilience4jConfigurationCommon Key: CAMEL-17743 URL: https://issues.apache.org/jira/browse/CAMEL-17743 Project: Camel Issue Type: Bug Components: camel-core Reporter: John Poth Assignee: John Poth SB2 schema generation fails for Resilience4jConfigurationDefinition because the javaType is set to [*io.github.resilience4j.circuitbreaker.CircuitBreaker*|https://github.com/apache/camel/blob/6da63c1f884faa0b7981f78c8de0c818f994804e/core/camel-core-model/src/main/java/org/apache/camel/model/Resilience4jConfigurationCommon.java#L31] when [generating|https://github.com/apache/camel/blob/main/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaGeneratorMojo.java#L395] the schema while a String is expected. This also gives a ClassNotFoundException as the type isn't present on the classpath in SB2 starters. Removing the problematic javaTypes for now. Thanks ! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-17725) add tests in camel-fhir-starter
[ https://issues.apache.org/jira/browse/CAMEL-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499577#comment-17499577 ] John Poth commented on CAMEL-17725: --- https://github.com/apache/camel-spring-boot/pull/446 > add tests in camel-fhir-starter > --- > > Key: CAMEL-17725 > URL: https://issues.apache.org/jira/browse/CAMEL-17725 > Project: Camel > Issue Type: Test > Components: camel-fhir, camel-spring-boot-starters, tests >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (CAMEL-17725) add tests in camel-fhir-starter
[ https://issues.apache.org/jira/browse/CAMEL-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-17725: -- Fix Version/s: 3.16.0 > add tests in camel-fhir-starter > --- > > Key: CAMEL-17725 > URL: https://issues.apache.org/jira/browse/CAMEL-17725 > Project: Camel > Issue Type: Test > Components: camel-fhir, camel-spring-boot-starters, tests >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-17725) add tests in camel-fhir-starter
[ https://issues.apache.org/jira/browse/CAMEL-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-17725. --- Resolution: Fixed > add tests in camel-fhir-starter > --- > > Key: CAMEL-17725 > URL: https://issues.apache.org/jira/browse/CAMEL-17725 > Project: Camel > Issue Type: Test > Components: camel-fhir, camel-spring-boot-starters, tests >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.16.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (CAMEL-17725) add tests in camel-fhir-starter
John Poth created CAMEL-17725: - Summary: add tests in camel-fhir-starter Key: CAMEL-17725 URL: https://issues.apache.org/jira/browse/CAMEL-17725 Project: Camel Issue Type: Test Components: camel-fhir, camel-spring-boot-starters, tests Reporter: John Poth Assignee: John Poth -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (CAMEL-14104) Update FHIR to latest version
[ https://issues.apache.org/jira/browse/CAMEL-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17495482#comment-17495482 ] John Poth commented on CAMEL-14104: --- Hi [~paulfc] ! For sure! Contributions are welcome :) Let me know if you need any help with this! > Update FHIR to latest version > - > > Key: CAMEL-14104 > URL: https://issues.apache.org/jira/browse/CAMEL-14104 > Project: Camel > Issue Type: Improvement > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.x > > > This will introduce new features and minor breaking changes so should > probably be for Camel 3 only -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (CAMEL-16004) camel-fhir: Port the test to camel-test-infra
[ https://issues.apache.org/jira/browse/CAMEL-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-16004. --- Fix Version/s: 3.8.0 Resolution: Fixed > camel-fhir: Port the test to camel-test-infra > - > > Key: CAMEL-16004 > URL: https://issues.apache.org/jira/browse/CAMEL-16004 > Project: Camel > Issue Type: Improvement >Reporter: John Poth >Assignee: John Poth >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-16004) camel-fhir: Port the test to camel-test-infra
[ https://issues.apache.org/jira/browse/CAMEL-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-16004: - Assignee: John Poth > camel-fhir: Port the test to camel-test-infra > - > > Key: CAMEL-16004 > URL: https://issues.apache.org/jira/browse/CAMEL-16004 > Project: Camel > Issue Type: Improvement >Reporter: John Poth >Assignee: John Poth >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16004) camel-fhir: Port the test to camel-test-infra
John Poth created CAMEL-16004: - Summary: camel-fhir: Port the test to camel-test-infra Key: CAMEL-16004 URL: https://issues.apache.org/jira/browse/CAMEL-16004 Project: Camel Issue Type: Improvement Reporter: John Poth -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14973) camel-springboot-starter bom
John Poth created CAMEL-14973: - Summary: camel-springboot-starter bom Key: CAMEL-14973 URL: https://issues.apache.org/jira/browse/CAMEL-14973 Project: Camel Issue Type: Improvement Affects Versions: 3.2.0 Reporter: John Poth it would be cool to have a BOM for springboot-starters similar to what camel-parent provided -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth closed CAMEL-14493. - > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-14493. --- Resolution: Fixed [https://github.com/apache/camel/pull/3546] > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Fix Version/s: 2.25.1 > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.25.1 > > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Description: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmonmous for reporting the issue ! was: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmou > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmonmous for reporting the issue ! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14493: -- Description: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) Thanks @cmou was: java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) > > Thanks @cmou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
[ https://issues.apache.org/jira/browse/CAMEL-14493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-14493: - Assignee: John Poth > camel 2: mvn camel:run fails on spring projects > --- > > Key: CAMEL-14493 > URL: https://issues.apache.org/jira/browse/CAMEL-14493 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.0 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > java.lang.ClassNotFoundException: org.apache.camel.spring.Main > at java.net.URLClassLoader.findClass (URLClassLoader.java:382) > at java.lang.ClassLoader.loadClass (ClassLoader.java:418) > at java.lang.ClassLoader.loadClass (ClassLoader.java:351) > at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) > at java.lang.Thread.run (Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14493) camel 2: mvn camel:run fails on spring projects
John Poth created CAMEL-14493: - Summary: camel 2: mvn camel:run fails on spring projects Key: CAMEL-14493 URL: https://issues.apache.org/jira/browse/CAMEL-14493 Project: Camel Issue Type: Bug Affects Versions: 2.25.0 Reporter: John Poth java.lang.ClassNotFoundException: org.apache.camel.spring.Main at java.net.URLClassLoader.findClass (URLClassLoader.java:382) at java.lang.ClassLoader.loadClass (ClassLoader.java:418) at java.lang.ClassLoader.loadClass (ClassLoader.java:351) at org.apache.camel.maven.RunMojo$1.run (RunMojo.java:498) at java.lang.Thread.run (Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14104) Update FHIR to latest version
[ https://issues.apache.org/jira/browse/CAMEL-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972646#comment-16972646 ] John Poth commented on CAMEL-14104: --- Yeah it's broken at the moment it's on my TODO list to fix it > Update FHIR to latest version > - > > Key: CAMEL-14104 > URL: https://issues.apache.org/jira/browse/CAMEL-14104 > Project: Camel > Issue Type: Improvement > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.x > > > This will introduce new features and minor breaking changes so should > probably be for Camel 3 only -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14104) Update FHIR to latest version
[ https://issues.apache.org/jira/browse/CAMEL-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972336#comment-16972336 ] John Poth commented on CAMEL-14104: --- Hi [~davsclaus], I have it ready to be pushed. I was thinking of doing it sometime this week. I think this should ideally be done before 3.0 GA. Karaf support is dropped for now (until next hapi-fhir release), would that be okay ? > Update FHIR to latest version > - > > Key: CAMEL-14104 > URL: https://issues.apache.org/jira/browse/CAMEL-14104 > Project: Camel > Issue Type: Improvement > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.x > > > This will introduce new features and minor breaking changes so should > probably be for Camel 3 only -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14154) Add option to create cache if it doesn't exists in camel-infinispan
John Poth created CAMEL-14154: - Summary: Add option to create cache if it doesn't exists in camel-infinispan Key: CAMEL-14154 URL: https://issues.apache.org/jira/browse/CAMEL-14154 Project: Camel Issue Type: Improvement Components: camel-infinispan Affects Versions: 3.0.0.RC3 Reporter: John Poth It might be nice to have an option in camel-infinispan to create the cache if it doesn't exits. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14149) Upgrade Infinispan version to 10.0.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968421#comment-16968421 ] John Poth commented on CAMEL-14149: --- [~acosentino] yes, I just push two commits that should resolve this - don't think this can be backported easily > Upgrade Infinispan version to 10.0.1.Final > -- > > Key: CAMEL-14149 > URL: https://issues.apache.org/jira/browse/CAMEL-14149 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Affects Versions: 3.0.0.RC3 >Reporter: John Poth >Priority: Major > Fix For: 3.0.0.RC4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14149) Upgrade Infinispan version to 10.0.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-14149. --- Resolution: Fixed > Upgrade Infinispan version to 10.0.1.Final > -- > > Key: CAMEL-14149 > URL: https://issues.apache.org/jira/browse/CAMEL-14149 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Affects Versions: 3.0.0.RC3 >Reporter: John Poth >Priority: Major > Fix For: 3.0.0.RC4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14149) Upgrade Infinispan version to 10.0.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-14149: -- Fix Version/s: 3.0.0.RC4 > Upgrade Infinispan version to 10.0.1.Final > -- > > Key: CAMEL-14149 > URL: https://issues.apache.org/jira/browse/CAMEL-14149 > Project: Camel > Issue Type: Improvement > Components: camel-infinispan >Affects Versions: 3.0.0.RC3 >Reporter: John Poth >Priority: Major > Fix For: 3.0.0.RC4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14149) Uprage Infinispan version to 10.0.1.Final
John Poth created CAMEL-14149: - Summary: Uprage Infinispan version to 10.0.1.Final Key: CAMEL-14149 URL: https://issues.apache.org/jira/browse/CAMEL-14149 Project: Camel Issue Type: Improvement Components: camel-infinispan Affects Versions: 3.0.0.RC3 Reporter: John Poth -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14104) Update FHIR to latest version
[ https://issues.apache.org/jira/browse/CAMEL-14104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-14104: - Assignee: John Poth > Update FHIR to latest version > - > > Key: CAMEL-14104 > URL: https://issues.apache.org/jira/browse/CAMEL-14104 > Project: Camel > Issue Type: Improvement > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > > This will introduce new features and minor breaking changes so should > probably be for Camel 3 only -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14104) Update FHIR to latest version
John Poth created CAMEL-14104: - Summary: Update FHIR to latest version Key: CAMEL-14104 URL: https://issues.apache.org/jira/browse/CAMEL-14104 Project: Camel Issue Type: Improvement Components: camel-fhir Reporter: John Poth This will introduce new features and minor breaking changes so should probably be for Camel 3 only -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14000) ServicePool can cause memory leak
[ https://issues.apache.org/jira/browse/CAMEL-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth reassigned CAMEL-14000: - Assignee: John Poth > ServicePool can cause memory leak > - > > Key: CAMEL-14000 > URL: https://issues.apache.org/jira/browse/CAMEL-14000 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.24.2, 3.0.0.RC1 >Reporter: John Poth >Assignee: John Poth >Priority: Major > > The > [ServicePool|[https://github.com/apache/camel/blob/master/core/camel-base/src/main/java/org/apache/camel/impl/engine/ServicePool.java#L50]] > or (DefaultServicePool in 2.x) uses a unbounded ConcurrentHashMap to cash > producers. This can cause memory leaks in highly dynamic routes using > recipient lists creating many temporary endpoint which will never be evicted > even when the route stops. Even though workarounds exists, we might consider > using an LRUCache for eviction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14000) ServicePool can cause memory leak
John Poth created CAMEL-14000: - Summary: ServicePool can cause memory leak Key: CAMEL-14000 URL: https://issues.apache.org/jira/browse/CAMEL-14000 Project: Camel Issue Type: Improvement Affects Versions: 3.0.0.RC1, 2.24.2 Reporter: John Poth The [ServicePool|[https://github.com/apache/camel/blob/master/core/camel-base/src/main/java/org/apache/camel/impl/engine/ServicePool.java#L50]] or (DefaultServicePool in 2.x) uses a unbounded ConcurrentHashMap to cash producers. This can cause memory leaks in highly dynamic routes using recipient lists creating many temporary endpoint which will never be evicted even when the route stops. Even though workarounds exists, we might consider using an LRUCache for eviction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865797#comment-16865797 ] John Poth edited comment on CAMEL-13650 at 6/17/19 5:17 PM: Should be fixed with [https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805] was (Author: jpoth): Should have been fixed with https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805 > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865797#comment-16865797 ] John Poth commented on CAMEL-13650: --- Should have been fixed with https://github.com/apache/camel/commit/684378fcfd5a4e57a6290761bc7a5faaf43c9805 > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13539) Upgrade retrofit to 2.5.0
[ https://issues.apache.org/jira/browse/CAMEL-13539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-13539. --- Resolution: Fixed > Upgrade retrofit to 2.5.0 > - > > Key: CAMEL-13539 > URL: https://issues.apache.org/jira/browse/CAMEL-13539 > Project: Camel > Issue Type: Improvement > Components: camel-consul, camel-influxdb, camel-pubnub >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > [https://nvd.nist.gov/vuln/detail/CVE-2018-1000850,] working on a PR -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13539) Upgrade retrofit to 2.5.0
John Poth created CAMEL-13539: - Summary: Upgrade retrofit to 2.5.0 Key: CAMEL-13539 URL: https://issues.apache.org/jira/browse/CAMEL-13539 Project: Camel Issue Type: Improvement Components: camel-consul, camel-influxdb, camel-pubnub Reporter: John Poth Assignee: John Poth [https://nvd.nist.gov/vuln/detail/CVE-2018-1000850,] working on a PR -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13523) Support Java 12
John Poth created CAMEL-13523: - Summary: Support Java 12 Key: CAMEL-13523 URL: https://issues.apache.org/jira/browse/CAMEL-13523 Project: Camel Issue Type: Improvement Reporter: John Poth Fix For: 3.0.0 Builds fine but needs [https://github.com/mvel/mvel/issues/185/] to be merged and released. Thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13436) Set TLS default to TLSv1.3 once we move to JDK11
[ https://issues.apache.org/jira/browse/CAMEL-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-13436: -- Component/s: camel-solr camel-restlet camel-jetty camel-http > Set TLS default to TLSv1.3 once we move to JDK11 > - > > Key: CAMEL-13436 > URL: https://issues.apache.org/jira/browse/CAMEL-13436 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-http, camel-jetty, camel-restlet, > camel-solr >Affects Versions: 3.0.0 >Reporter: John Poth >Priority: Major > > Also add tests to different components that use TLS > http://openjdk.java.net/jeps/332 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13436) Set TLS default to TLSv1.3 once we move to JDK11
John Poth created CAMEL-13436: - Summary: Set TLS default to TLSv1.3 once we move to JDK11 Key: CAMEL-13436 URL: https://issues.apache.org/jira/browse/CAMEL-13436 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 3.0.0 Reporter: John Poth Also add tests to different components that use TLS http://openjdk.java.net/jeps/332 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13408) Investigate camel-jibx
John Poth created CAMEL-13408: - Summary: Investigate camel-jibx Key: CAMEL-13408 URL: https://issues.apache.org/jira/browse/CAMEL-13408 Project: Camel Issue Type: New Feature Components: camel-jibx Reporter: John Poth Tests for camel-jibx have been [disabled|https://github.com/apache/camel/blob/b93c32756fe097163bf3cd642f53ecc30b457f8e/components/camel-jibx/pom.xml#L151] for a while. JDK-8 [support|https://github.com/jibx/jibx/issues/3] was added in 1.3.1 but it seems it's not a simple upgrade. JDK9+ support is still an open [issue|https://github.com/jibx/jibx/issues/9] So we should either mark the component as deprecated in 2.x and remove it in 3.x or try to fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13127) Camel-Fhir-Example-osgi doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth resolved CAMEL-13127.
---
Resolution: Fixed
> Camel-Fhir-Example-osgi doesn't work
>
>
> Key: CAMEL-13127
> URL: https://issues.apache.org/jira/browse/CAMEL-13127
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: Andrea Cosentino
>Assignee: John Poth
>Priority: Major
> Fix For: 3.0.0
>
>
> {code:java}
> 12:47:27.332 WARN [pipe-install -s
> mvn:org.apache.camel.example/camel-example-fhir-osgi/3.0.0-SNAPSHOT] Listener
> caused an exception, will be ignored
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError:
> org/apache/camel/util/concurrent/ThreadPoolRejectedPolicy
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?]
> at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:193)
> ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:225)
> ~[?:?]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:188)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:427)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> [?:?]
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) [?:?]
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) [?:?]
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) [?:?]
> at
[jira] [Commented] (CAMEL-13127) Camel-Fhir-Example-osgi doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753833#comment-16753833
]
John Poth commented on CAMEL-13127:
---
Closed with
https://github.com/apache/camel/commit/2c63df2ecfa3f8cdf15bf08febfcad6b720bea01
> Camel-Fhir-Example-osgi doesn't work
>
>
> Key: CAMEL-13127
> URL: https://issues.apache.org/jira/browse/CAMEL-13127
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: Andrea Cosentino
>Assignee: John Poth
>Priority: Major
> Fix For: 3.0.0
>
>
> {code:java}
> 12:47:27.332 WARN [pipe-install -s
> mvn:org.apache.camel.example/camel-example-fhir-osgi/3.0.0-SNAPSHOT] Listener
> caused an exception, will be ignored
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError:
> org/apache/camel/util/concurrent/ThreadPoolRejectedPolicy
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?]
> at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:193)
> ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:225)
> ~[?:?]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:188)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:427)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> [?:?]
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) [?:?]
> at
[jira] [Assigned] (CAMEL-13127) Camel-Fhir-Example-osgi doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Poth reassigned CAMEL-13127:
-
Assignee: John Poth
> Camel-Fhir-Example-osgi doesn't work
>
>
> Key: CAMEL-13127
> URL: https://issues.apache.org/jira/browse/CAMEL-13127
> Project: Camel
> Issue Type: Bug
> Components: examples
>Reporter: Andrea Cosentino
>Assignee: John Poth
>Priority: Major
> Fix For: 3.0.0
>
>
> {code:java}
> 12:47:27.332 WARN [pipe-install -s
> mvn:org.apache.camel.example/camel-example-fhir-osgi/3.0.0-SNAPSHOT] Listener
> caused an exception, will be ignored
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError:
> org/apache/camel/util/concurrent/ThreadPoolRejectedPolicy
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?]
> at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:193)
> ~[?:?]
> at
> java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:225)
> ~[?:?]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180)
> ~[48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:188)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:427)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:278)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:299)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:268)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:264)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:254)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
> [48:org.apache.aries.blueprint.core:1.10.1]
> at
> org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730)
> [?:?]
> at
> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485)
> [?:?]
> at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) [?:?]
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) [?:?]
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
[jira] [Updated] (CAMEL-12625) Create FHIR Camel component with example
[ https://issues.apache.org/jira/browse/CAMEL-12625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-12625: -- Description: Create Camel component to integrate with [FHIR|http://hapifhir.io] endpoints. I'll submit a PR (was: Create Camel component to integrate with [FHIR|[http://example.com|http://hapifhir.io/doc_rest_server.html]] endpoints. I'll submit a PR) > Create FHIR Camel component with example > > > Key: CAMEL-12625 > URL: https://issues.apache.org/jira/browse/CAMEL-12625 > Project: Camel > Issue Type: New Feature > Components: camel-fhir >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.23.0 > > > Create Camel component to integrate with [FHIR|http://hapifhir.io] endpoints. > I'll submit a PR -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12625) Create FHIR Camel component with example
John Poth created CAMEL-12625: - Summary: Create FHIR Camel component with example Key: CAMEL-12625 URL: https://issues.apache.org/jira/browse/CAMEL-12625 Project: Camel Issue Type: New Feature Reporter: John Poth Assignee: John Poth Create Camel component to integrate with [FHIR|[http://example.com|http://hapifhir.io/doc_rest_server.html]] endpoints. I'll submit a PR -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12613) Camel file endpoint loses modification date and length information when preMove is used
[ https://issues.apache.org/jira/browse/CAMEL-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-12613: -- Fix Version/s: 2.23.0 > Camel file endpoint loses modification date and length information when > preMove is used > --- > > Key: CAMEL-12613 > URL: https://issues.apache.org/jira/browse/CAMEL-12613 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.21.1 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.23.0 > > > I'll work on a PR with a unit test, thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12613) Camel file endpoint loses modification date and length information when preMove is used
[ https://issues.apache.org/jira/browse/CAMEL-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth resolved CAMEL-12613. --- Resolution: Fixed > Camel file endpoint loses modification date and length information when > preMove is used > --- > > Key: CAMEL-12613 > URL: https://issues.apache.org/jira/browse/CAMEL-12613 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.21.1 >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.23.0 > > > I'll work on a PR with a unit test, thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12613) Camel file endpoint loses modification date and length information when preMove is used
John Poth created CAMEL-12613: - Summary: Camel file endpoint loses modification date and length information when preMove is used Key: CAMEL-12613 URL: https://issues.apache.org/jira/browse/CAMEL-12613 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.21.1 Reporter: John Poth Assignee: John Poth I'll work on a PR with a unit test, thanks! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12493) Remove recently added additional HL7 Type Converters
[
https://issues.apache.org/jira/browse/CAMEL-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467379#comment-16467379
]
John Poth commented on CAMEL-12493:
---
PRs are welcome :)
> Remove recently added additional HL7 Type Converters
>
>
> Key: CAMEL-12493
> URL: https://issues.apache.org/jira/browse/CAMEL-12493
> Project: Camel
> Issue Type: Improvement
> Components: camel-hl7
>Affects Versions: 2.21.0
>Reporter: christian ohr
>Priority: Major
>
> In Camel 2.21.0, HL7-version/event-specific type converters were added to
> camel-hl7. IMHO this was a bad idea:
> * it transitively pulls in *all* HL7 structure libraries, regardless whether
> you need them in your application or not. That's nearly 10MB. Btw, type
> converters for the newer HL7 versions 2.7, 2.8, 2.8.1 were simply
> disregarded, which would have gifted you with another ~ 7.5MB.
> * manually excluding one or more of them causes the
> AnnotationTypeConverterLoader to throw ugly NoClassDefFoundError stack traces
> in the log
> * the component documentation states that you have to manually add structure
> library dependencies (the way it should be, really)
> Proposal: remove these type converters. I think it's acceptable to do a
> simple type cast in a processor or add a manual \{{convertBodyTo(HL7Class)}}
> in the route instead.
> Opinions? (I'm happy to provide a PR :))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12493) Remove recently added additional HL7 Type Converters
[
https://issues.apache.org/jira/browse/CAMEL-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467350#comment-16467350
]
John Poth commented on CAMEL-12493:
---
This makes sense IMO.
[~christian.ohr] would marking the dependencies as optional and using
[org.apache.camel.Converter#ignoreOnLoadError|https://github.com/apache/camel/blob/00fef5857c0bcb0fc7a02f19f5ba51ef0382133d/camel-core/src/main/java/org/apache/camel/Converter.java#L54]
fit this purpose?
> Remove recently added additional HL7 Type Converters
>
>
> Key: CAMEL-12493
> URL: https://issues.apache.org/jira/browse/CAMEL-12493
> Project: Camel
> Issue Type: Improvement
> Components: camel-hl7
>Affects Versions: 2.21.0
>Reporter: christian ohr
>Priority: Major
>
> In Camel 2.21.0, HL7-version/event-specific type converters were added to
> camel-hl7. IMHO this was a bad idea:
> * it transitively pulls in *all* HL7 structure libraries, regardless whether
> you need them in your application or not. That's nearly 10MB. Btw, type
> converters for the newer HL7 versions 2.7, 2.8, 2.8.1 were simply
> disregarded, which would have gifted you with another ~ 7.5MB.
> * manually excluding one or more of them causes the
> AnnotationTypeConverterLoader to throw ugly NoClassDefFoundError stack traces
> in the log
> * the component documentation states that you have to manually add structure
> library dependencies (the way it should be, really)
> Proposal: remove these type converters. I think it's acceptable to do a
> simple type cast in a processor or add a manual \{{convertBodyTo(HL7Class)}}
> in the route instead.
> Opinions? (I'm happy to provide a PR :))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387564#comment-16387564 ] John Poth edited comment on CAMEL-12221 at 3/6/18 10:15 AM: I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. Or SMX as you mentioned. was (Author: jpoth): I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387564#comment-16387564 ] John Poth commented on CAMEL-12221: --- I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-5469) CxfRsProducer is not thread safe
[
https://issues.apache.org/jira/browse/CAMEL-5469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363711#comment-16363711
]
John Poth commented on CAMEL-5469:
--
Hi [~batwad], you may want to try out CAMEL-9628 which is available since 2.17.
With the singleton property set to true, Camel will only create one instance of
CxfRsProducer and ConcurrentModificationException should be avoided. HTH
> CxfRsProducer is not thread safe
>
>
> Key: CAMEL-5469
> URL: https://issues.apache.org/jira/browse/CAMEL-5469
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
>Affects Versions: 2.10.0
> Environment: apache-maven-3.0
> tomcat 6.0.35
>Reporter: Dumitru Pascu
>Assignee: Willem Jiang
>Priority: Major
> Fix For: 2.11.0
>
> Attachments: CamelRoute.java,
> CxfRsProducerClientFactoryCacheTest.java,
> CxfRsProducerClientFactoryCacheTest1.xml, camel-example-cxf-tomcat.zip
>
>
> The example is based on the camel-example-cxf-tomcat.
> Components:
> 1. Have a CXF rest web service configured in camel-config.
> 2. Have a Camel CXF client cxf:rsClient used to call web service from point 1.
> 3. Have a Camel CXF server cxf:rsServer which acts as a proxy for service
> from point 1 by passing inbount message towards client from point 2.
> Flow:
> 1. Service 3 receives message
> 2. Message is passed to component 2 (Camel cxf client)
> 3. Component 2 invokes service 1
> 4. Response received is transformed using a custom processor
> Problem:
> When having multiple requests in parallel, following error appears
> (CxfRsProducer does not seem to be thread safe):
> {noformat}
> java.lang.RuntimeException: java.util.ConcurrentModificationException
> at
> org.apache.cxf.jaxrs.client.JAXRSClientFactoryBean.createWebClient(JAXRSClientFactoryBean.java:217)[cxf-rt-frontend-jaxrs-2.6.1.jar:2.6.1]
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsProducer.invokeHttpClient(CxfRsProducer.java:100)[camel-cxf-2.10.0.jar:2.10.0]
> at
> org.apache.camel.component.cxf.jaxrs.CxfRsProducer.process(CxfRsProducer.java:87)[camel-cxf-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:120)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:292)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:115)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:330)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:45)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:303)[camel-core-2.10.0.jar:2.10.0]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)[camel-core-2.10.0.jar:2.10.0]
> at
>
[jira] [Updated] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-12221: -- Description: Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] I can take care of the PR. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Poth updated CAMEL-12221: -- Summary: Let's create a camel-fhir component (was: Let) > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12221) Let
John Poth created CAMEL-12221: - Summary: Let Key: CAMEL-12221 URL: https://issues.apache.org/jira/browse/CAMEL-12221 Project: Camel Issue Type: New Feature Reporter: John Poth -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context
John Poth created CAMEL-12082:
-
Summary: Camel route commands should set the TCCL when working
with local camel context
Key: CAMEL-12082
URL: https://issues.apache.org/jira/browse/CAMEL-12082
Project: Camel
Issue Type: Bug
Affects Versions: 2.20.2
Reporter: John Poth
This causes class not found issues in Karaf when restarting routes for example:
{code}
13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
java.lang.RuntimeException: Unable to load
org.eclipse.jetty.websocket.server.WebSocketServerFactory
at
org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
~[?:?]
at
org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
~[?:?]
at javax.servlet.GenericServlet.init(GenericServlet.java:244)
~[34:javax.servlet-api:3.1.0]
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at
org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
[226:org.apache.camel.camel-websocket:2.21.0]
at
org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
[226:org.apache.camel.camel-websocket:2.21.0]
at
org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
[226:org.apache.camel.camel-websocket:2.21.0]
at
org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
[226:org.apache.camel.camel-websocket:2.21.0]
at
org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
[226:org.apache.camel.camel-websocket:2.21.0]
at
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1472)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:44)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:31)
[54:org.apache.camel.camel-core:2.21.0]
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75)
[54:org.apache.camel.camel-core:2.21.0]
at
[jira] [Created] (CAMEL-12064) Create a camel-example-olingo4-blueprint example
John Poth created CAMEL-12064: - Summary: Create a camel-example-olingo4-blueprint example Key: CAMEL-12064 URL: https://issues.apache.org/jira/browse/CAMEL-12064 Project: Camel Issue Type: Task Reporter: John Poth It would be nice have an example for camel-olingo4 in OSGI environment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
