[jira] [Commented] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
[ https://issues.apache.org/jira/browse/CAMEL-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224460#comment-17224460 ] Vladimir commented on CAMEL-15787: -- https://github.com/apache/camel/pull/4548/commits/4d45fda928b67bc731bce289b0e2d3130955bcd5 > Netty in client mode (with pool) recreate sockets every 5 minutes > - > > Key: CAMEL-15787 > URL: https://issues.apache.org/jira/browse/CAMEL-15787 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Affects Versions: 3.4.4, 3.6.0 >Reporter: Vladimir >Priority: Minor > > When using netty in client mode (create pool of connections). And do not send > any requests, all sockets in pool recreate every 5 minutes. > It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L > config for apache common pool. Default value must be bigger and do not > recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
[ https://issues.apache.org/jira/browse/CAMEL-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224442#comment-17224442 ] Vladimir commented on CAMEL-15787: -- But keepAlive mode is enabled, sockets wait data. I see keeAlive timers in system, but sockets close and recreate. When i create sockets from route and then send data with Channed.write from processors, sockets recreate every 5 minutes. I lost data, this is problem. > Netty in client mode (with pool) recreate sockets every 5 minutes > - > > Key: CAMEL-15787 > URL: https://issues.apache.org/jira/browse/CAMEL-15787 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Affects Versions: 3.4.4, 3.6.0 >Reporter: Vladimir >Priority: Minor > > When using netty in client mode (create pool of connections). And do not send > any requests, all sockets in pool recreate every 5 minutes. > It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L > config for apache common pool. Default value must be bigger and do not > recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15775) Upgrade to spring boot 2.3.5
[ https://issues.apache.org/jira/browse/CAMEL-15775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-15775. -- Resolution: Fixed > Upgrade to spring boot 2.3.5 > > > Key: CAMEL-15775 > URL: https://issues.apache.org/jira/browse/CAMEL-15775 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.7.0 > > > There is a new release today -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
[ https://issues.apache.org/jira/browse/CAMEL-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224433#comment-17224433 ] Claus Ibsen commented on CAMEL-15787: - No why do you think that, they are idle for 5 min and gets re-created. You can configure a higher value if you want. > Netty in client mode (with pool) recreate sockets every 5 minutes > - > > Key: CAMEL-15787 > URL: https://issues.apache.org/jira/browse/CAMEL-15787 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Affects Versions: 3.4.4, 3.6.0 >Reporter: Vladimir >Priority: Major > > When using netty in client mode (create pool of connections). And do not send > any requests, all sockets in pool recreate every 5 minutes. > It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L > config for apache common pool. Default value must be bigger and do not > recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
[ https://issues.apache.org/jira/browse/CAMEL-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15787: Priority: Minor (was: Major) > Netty in client mode (with pool) recreate sockets every 5 minutes > - > > Key: CAMEL-15787 > URL: https://issues.apache.org/jira/browse/CAMEL-15787 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Affects Versions: 3.4.4, 3.6.0 >Reporter: Vladimir >Priority: Minor > > When using netty in client mode (create pool of connections). And do not send > any requests, all sockets in pool recreate every 5 minutes. > It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L > config for apache common pool. Default value must be bigger and do not > recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
[ https://issues.apache.org/jira/browse/CAMEL-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-15787: Issue Type: Improvement (was: Bug) > Netty in client mode (with pool) recreate sockets every 5 minutes > - > > Key: CAMEL-15787 > URL: https://issues.apache.org/jira/browse/CAMEL-15787 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Affects Versions: 3.4.4, 3.6.0 >Reporter: Vladimir >Priority: Major > > When using netty in client mode (create pool of connections). And do not send > any requests, all sockets in pool recreate every 5 minutes. > It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L > config for apache common pool. Default value must be bigger and do not > recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15787) Netty in client mode (with pool) recreate sockets every 5 minutes
Vladimir created CAMEL-15787: Summary: Netty in client mode (with pool) recreate sockets every 5 minutes Key: CAMEL-15787 URL: https://issues.apache.org/jira/browse/CAMEL-15787 Project: Camel Issue Type: Bug Components: camel-netty Affects Versions: 3.6.0, 3.4.4 Reporter: Vladimir When using netty in client mode (create pool of connections). And do not send any requests, all sockets in pool recreate every 5 minutes. It is strange private long producerPoolMinEvictableIdle = 5 * 60 * 1000L config for apache common pool. Default value must be bigger and do not recreate all sockets every 5 minutes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15766) camel-spring-boot - No converter found capable of converting from type [java.lang.String] to type [org.apache.camel.component.http.HttpClientConfigurer]
[
https://issues.apache.org/jira/browse/CAMEL-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Volodin reassigned CAMEL-15766:
--
Assignee: (was: Dmitry Volodin)
> camel-spring-boot - No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
>
>
> Key: CAMEL-15766
> URL: https://issues.apache.org/jira/browse/CAMEL-15766
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-spring-boot
>Affects Versions: 3.6.0
>Reporter: Marco Santarelli
>Priority: Major
> Fix For: 3.7.0
>
>
> When trying to use a custom http-configurer, I believe I am experiencing a
> regression when upgrading to Camel 3.6.0
> I am using spring-boot 2.3.4.RELEASE, and I am declaring my custom configurer
> bean using:
> {code:java}
> camel.component.http.http-client-configurer=#httpClientConfig
> {code}
> When updating to Camel 3.6.0, that configuration results in:
> {code:java}
> ***
> APPLICATION FAILED TO START
> ***
> Description:
> Failed to bind properties under 'camel.component.http.http-client-configurer'
> to org.apache.camel.component.http.HttpClientConfigurer:
> Property: camel.component.http.http-client-configurer
> Value: httpClientConfig
> Origin: class path resource [application.properties]:1:45
> Reason: No converter found capable of converting from type
> [java.lang.String] to type
> [org.apache.camel.component.http.HttpClientConfigurer]
> Action:
> Update your application's configuration{code}
>
> See [https://github.com/santam85/camel-3.6.0-http-configurer-bean] for a
> reproduction example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15679) LevelDB: Consider replacing of serizalization via org.fusesource.hawtbuf:hawtbuf with Jackson
[ https://issues.apache.org/jira/browse/CAMEL-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15679. - Resolution: Fixed > LevelDB: Consider replacing of serizalization via > org.fusesource.hawtbuf:hawtbuf with Jackson > - > > Key: CAMEL-15679 > URL: https://issues.apache.org/jira/browse/CAMEL-15679 > Project: Camel > Issue Type: Improvement > Components: camel-leveldb >Affects Versions: 3.5.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.7.0 > > > Current implementation of serialization is based on > `org.fusesource.hawtbuf:hawtbuf` and java object serialization. It would be > better to use Jackson instead. Here are some reasons: > # Serialization with Jackson is faster (see > [http://rick-hightower.blogspot.com/2014/04/which-is-faster-java-object.html]) > # Camel-quarkus can not use java object serialization in native (see > [https://github.com/oracle/graal/issues/460]) Current workaround uses Jackson > instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15772) camel-pulsar - should support readCompacted configuration
[ https://issues.apache.org/jira/browse/CAMEL-15772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15772. - Resolution: Fixed > camel-pulsar - should support readCompacted configuration > - > > Key: CAMEL-15772 > URL: https://issues.apache.org/jira/browse/CAMEL-15772 > Project: Camel > Issue Type: New Feature > Components: camel-pulsar >Affects Versions: 3.6.0 >Reporter: Ludovic Boutros >Priority: Major > Fix For: 3.7.0 > > > In order to read compacted topics, the component (consumer) should support > the _readCompacted_ option. > [readCompacted > documentation|https://pulsar.apache.org/docs/en/cookbooks-compaction/#java] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15735) levelDB: create starter for camel-leveldb-legacy
[ https://issues.apache.org/jira/browse/CAMEL-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15735. - Fix Version/s: 3.7.0 Resolution: Fixed > levelDB: create starter for camel-leveldb-legacy > > > Key: CAMEL-15735 > URL: https://issues.apache.org/jira/browse/CAMEL-15735 > Project: Camel > Issue Type: Improvement > Components: camel-leveldb >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.7.0 > > > New component 'camel-leveldb-legacy' was created as a result of issue > https://issues.apache.org/jira/browse/CAMEL-15679. > > Starter has to be added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15786) Camel OpenAPI ignores apiVendorExtension option for REST binding
[
https://issues.apache.org/jira/browse/CAMEL-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-15786:
Fix Version/s: 3.7.0
> Camel OpenAPI ignores apiVendorExtension option for REST binding
>
>
> Key: CAMEL-15786
> URL: https://issues.apache.org/jira/browse/CAMEL-15786
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.4.1, 3.6.0
>Reporter: Tomek
>Priority: Major
> Fix For: 3.7.0
>
>
> According to [https://camel.apache.org/manual/latest/rest-dsl.html] by
> default the apiVendorExtension option should be set to false. But even when I
> set it manually to false, the produced JSON for OpenAPI still contains the x-
> fields like "x-camelContextId", "x-routeId" etc.
> I've tried to set this option both in Java using
> restConfiguration().apiVendorExtension(false) and in application.yml file of
> my Spring Boot application:
> {code:java}
> camel:
> rest:
> api-vendor-extension: false{code}
> I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
> result.
> Part of my pom.xml file:
> {code:java}
>
> org.apache.camel.springboot
> camel-rest-starter
> 3.4.1
>
>
> org.apache.camel.springboot
> camel-openapi-java-starter
> 3.4.1
>
> {code}
> Could you please check it? I don't want to expose internal implementation
> details via OpenAPI JSON file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15786) Camel OpenAPI ignores apiVendorExtension option for REST binding
[
https://issues.apache.org/jira/browse/CAMEL-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224423#comment-17224423
]
Claus Ibsen commented on CAMEL-15786:
-
If you have the time then you may want to look in the source code if that
feature is missing and then look in the -swagger component how it does it, and
copy that over to openapi and submit a PR. We love contributions
> Camel OpenAPI ignores apiVendorExtension option for REST binding
>
>
> Key: CAMEL-15786
> URL: https://issues.apache.org/jira/browse/CAMEL-15786
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.4.1, 3.6.0
>Reporter: Tomek
>Priority: Major
>
> According to [https://camel.apache.org/manual/latest/rest-dsl.html] by
> default the apiVendorExtension option should be set to false. But even when I
> set it manually to false, the produced JSON for OpenAPI still contains the x-
> fields like "x-camelContextId", "x-routeId" etc.
> I've tried to set this option both in Java using
> restConfiguration().apiVendorExtension(false) and in application.yml file of
> my Spring Boot application:
> {code:java}
> camel:
> rest:
> api-vendor-extension: false{code}
> I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
> result.
> Part of my pom.xml file:
> {code:java}
>
> org.apache.camel.springboot
> camel-rest-starter
> 3.4.1
>
>
> org.apache.camel.springboot
> camel-openapi-java-starter
> 3.4.1
>
> {code}
> Could you please check it? I don't want to expose internal implementation
> details via OpenAPI JSON file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15748) Paho consumer never connects if the broker is not reachable at startup
[
https://issues.apache.org/jira/browse/CAMEL-15748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-15748.
-
Resolution: Fixed
> Paho consumer never connects if the broker is not reachable at startup
> --
>
> Key: CAMEL-15748
> URL: https://issues.apache.org/jira/browse/CAMEL-15748
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
>Affects Versions: 3.5.0, 3.4.4, 3.6.0
>Reporter: Marco Collovati
>Priority: Major
> Fix For: 3.4.5, 3.7.0
>
> Attachments: PahoConsumerRestartTest.java
>
>
> Having a route with a paho consumer in a route, if the broker is not
> reachable at startup, camel context fail fast and shuts down.
> This can be avoided by setting the *SupervisingRouteController*, but this
> way, even if camel context does not fail, the consumer is never able to
> establish a connection.
> The reason is that when *PahoConsumer* starts for the first time, it creates
> a *MqttClient* and stores it into *client* field; the call to
> *client.connect* throws an exception due to broker down;
>
> {code:java}
>
> @Override
> protected void doStart() throws Exception {
> super.doStart();connectOptions =
> PahoEndpoint.createMqttConnectOptions(getEndpoint().getConfiguration());
> if (client == null) {
> clientId = getEndpoint().getConfiguration().getClientId();
> if (clientId == null) {
> clientId = "camel-" + MqttClient.generateClientId();
> }
> stopClient = true;
> client = new MqttClient(
> getEndpoint().getConfiguration().getBrokerUrl(),
> clientId,
>
> PahoEndpoint.createMqttClientPersistence(getEndpoint().getConfiguration()));
> LOG.debug("Connecting client: {} to broker: {}", clientId,
> getEndpoint().getConfiguration().getBrokerUrl());
> client.connect(connectOptions);
> }
>
> // other code omitted for brevity
>
> client.subscribe(getEndpoint().getTopic(),
> getEndpoint().getConfiguration().getQos());{code}
>
> after that *doStop* is invoked but the *client* instance is not nullified,
> because it is not connected
>
> {code:java}
> @Override
> protected void doStop() throws Exception {
> super.doStop();if (stopClient && client != null &&
> client.isConnected()) {
> String topic = getEndpoint().getTopic();
> // only unsubscribe if we are not durable
> if (getEndpoint().getConfiguration().isCleanSession()) {
> LOG.debug("Unsubscribing client: {} from topic: {}",
> clientId, topic);
> client.unsubscribe(topic);
> } else {
> LOG.debug("Client: {} is durable so will not unsubscribe from
> topic: {}", clientId, topic);
> }
> LOG.debug("Disconnecting client: {} from broker: {}", clientId,
> getEndpoint().getConfiguration().getBrokerUrl());
> client.disconnect();
> client = null;
> }
> }
> {code}
>
> when the supervisor tries to restart the route, *client* instance already
> exists, but the call to *client.subscribe* fails because the client is not
> connected.
> Perhaps always nullify *client* in *doStop* should resolve the issue; however
> I have no idea it this solution will impact in other ways.
> A better solution may be to handle automatic reconnect in the consumer, like
> *RabbitConsumer* does, for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15748) Paho consumer never connects if the broker is not reachable at startup
[
https://issues.apache.org/jira/browse/CAMEL-15748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224326#comment-17224326
]
Marco Collovati commented on CAMEL-15748:
-
Created the PR for master.
The problem was in the test, not in paho client.
When adding a connector to ActiveMQ **BrokerService** the server socket is
immediately available,even if *BrokerService.start* is not invoked.
So paho client can establish a connection, but it receives *null* messages do
to socket read time out, and this leads to an infinite loop.
Moving *addConnector* immediately before broker start in test does the trick.
> Paho consumer never connects if the broker is not reachable at startup
> --
>
> Key: CAMEL-15748
> URL: https://issues.apache.org/jira/browse/CAMEL-15748
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
>Affects Versions: 3.5.0, 3.4.4, 3.6.0
>Reporter: Marco Collovati
>Priority: Major
> Fix For: 3.4.5, 3.7.0
>
> Attachments: PahoConsumerRestartTest.java
>
>
> Having a route with a paho consumer in a route, if the broker is not
> reachable at startup, camel context fail fast and shuts down.
> This can be avoided by setting the *SupervisingRouteController*, but this
> way, even if camel context does not fail, the consumer is never able to
> establish a connection.
> The reason is that when *PahoConsumer* starts for the first time, it creates
> a *MqttClient* and stores it into *client* field; the call to
> *client.connect* throws an exception due to broker down;
>
> {code:java}
>
> @Override
> protected void doStart() throws Exception {
> super.doStart();connectOptions =
> PahoEndpoint.createMqttConnectOptions(getEndpoint().getConfiguration());
> if (client == null) {
> clientId = getEndpoint().getConfiguration().getClientId();
> if (clientId == null) {
> clientId = "camel-" + MqttClient.generateClientId();
> }
> stopClient = true;
> client = new MqttClient(
> getEndpoint().getConfiguration().getBrokerUrl(),
> clientId,
>
> PahoEndpoint.createMqttClientPersistence(getEndpoint().getConfiguration()));
> LOG.debug("Connecting client: {} to broker: {}", clientId,
> getEndpoint().getConfiguration().getBrokerUrl());
> client.connect(connectOptions);
> }
>
> // other code omitted for brevity
>
> client.subscribe(getEndpoint().getTopic(),
> getEndpoint().getConfiguration().getQos());{code}
>
> after that *doStop* is invoked but the *client* instance is not nullified,
> because it is not connected
>
> {code:java}
> @Override
> protected void doStop() throws Exception {
> super.doStop();if (stopClient && client != null &&
> client.isConnected()) {
> String topic = getEndpoint().getTopic();
> // only unsubscribe if we are not durable
> if (getEndpoint().getConfiguration().isCleanSession()) {
> LOG.debug("Unsubscribing client: {} from topic: {}",
> clientId, topic);
> client.unsubscribe(topic);
> } else {
> LOG.debug("Client: {} is durable so will not unsubscribe from
> topic: {}", clientId, topic);
> }
> LOG.debug("Disconnecting client: {} from broker: {}", clientId,
> getEndpoint().getConfiguration().getBrokerUrl());
> client.disconnect();
> client = null;
> }
> }
> {code}
>
> when the supervisor tries to restart the route, *client* instance already
> exists, but the call to *client.subscribe* fails because the client is not
> connected.
> Perhaps always nullify *client* in *doStop* should resolve the issue; however
> I have no idea it this solution will impact in other ways.
> A better solution may be to handle automatic reconnect in the consumer, like
> *RabbitConsumer* does, for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15786) Camel OpenAPI ignores apiVendorExtension option for REST binding
[
https://issues.apache.org/jira/browse/CAMEL-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek updated CAMEL-15786:
--
Description:
According to [https://camel.apache.org/manual/latest/rest-dsl.html] by default
the apiVendorExtension option should be set to false. But even when I set it
manually to false, the produced JSON for OpenAPI still contains the x- fields
like "x-camelContextId", "x-routeId" etc.
I've tried to set this option both in Java using
restConfiguration().apiVendorExtension(false) and in application.yml file of my
Spring Boot application:
{code:java}
camel:
rest:
api-vendor-extension: false{code}
I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
result.
Part of my pom.xml file:
{code:java}
org.apache.camel.springboot
camel-rest-starter
3.4.1
org.apache.camel.springboot
camel-openapi-java-starter
3.4.1
{code}
Could you please check it? I don't want to expose internal implementation
details via OpenAPI JSON file.
was:
According to [https://camel.apache.org/manual/latest/rest-dsl.html] by default
the apiVendorExtension option should be set to false. But even when I set it
manually to false, the produced JSON for OpenAPI still contains the x- fields
like "x-camelContextId", "x-routeId" etc.
I've tried to set this option both in Java using
restConfiguration().apiVendorExtension(false) and in application.yml file of my
Spring Boot application:
{code:java}
camel:
rest:
api-vendor-extension: false{code}
I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
result.
Part of my pom.xml file:
{code:java}
org.apache.camel.springboot
camel-rest-starter
3.4.1
org.apache.camel.springboot
camel-openapi-java-starter
3.4.1
{code}
Could you please check it? I don't want to expose internal development details
via OpenAPI JSON file.
> Camel OpenAPI ignores apiVendorExtension option for REST binding
>
>
> Key: CAMEL-15786
> URL: https://issues.apache.org/jira/browse/CAMEL-15786
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.4.1, 3.6.0
>Reporter: Tomek
>Priority: Major
>
> According to [https://camel.apache.org/manual/latest/rest-dsl.html] by
> default the apiVendorExtension option should be set to false. But even when I
> set it manually to false, the produced JSON for OpenAPI still contains the x-
> fields like "x-camelContextId", "x-routeId" etc.
> I've tried to set this option both in Java using
> restConfiguration().apiVendorExtension(false) and in application.yml file of
> my Spring Boot application:
> {code:java}
> camel:
> rest:
> api-vendor-extension: false{code}
> I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
> result.
> Part of my pom.xml file:
> {code:java}
>
> org.apache.camel.springboot
> camel-rest-starter
> 3.4.1
>
>
> org.apache.camel.springboot
> camel-openapi-java-starter
> 3.4.1
>
> {code}
> Could you please check it? I don't want to expose internal implementation
> details via OpenAPI JSON file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-15786) Camel OpenAPI ignores apiVendorExtension option for REST binding
[
https://issues.apache.org/jira/browse/CAMEL-15786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek updated CAMEL-15786:
--
Description:
According to [https://camel.apache.org/manual/latest/rest-dsl.html] by default
the apiVendorExtension option should be set to false. But even when I set it
manually to false, the produced JSON for OpenAPI still contains the x- fields
like "x-camelContextId", "x-routeId" etc.
I've tried to set this option both in Java using
restConfiguration().apiVendorExtension(false) and in application.yml file of my
Spring Boot application:
{code:java}
camel:
rest:
api-vendor-extension: false{code}
I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
result.
Part of my pom.xml file:
{code:java}
org.apache.camel.springboot
camel-rest-starter
3.4.1
org.apache.camel.springboot
camel-openapi-java-starter
3.4.1
{code}
Could you please check it? I don't want to expose internal development details
via OpenAPI JSON file.
was:
According to [https://camel.apache.org/manual/latest/rest-dsl.html] by default
the apiVendorExtension option should be set to false. But even when I set it
manually to false, the produced JSON for OpenAPI still contains the x- fields
like "x-camelContextId", "x-routeId" etc.
I've tried to set this option both in Java using
restConfiguration().apiVendorExtension(false) and in application.yml file of my
Spring Boot application:
{code:java}
camel:
rest:
api-vendor-extension: false{code}
I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
result.
Part of my pom.xml file:
{code:java}
org.apache.camel.springboot
camel-rest-starter
3.4.1
org.apache.camel.springboot
camel-openapi-java-starter
3.4.1
{code}
Could you please check it? I don't want to expose interlan development details
via OpenAPI JSON file.
> Camel OpenAPI ignores apiVendorExtension option for REST binding
>
>
> Key: CAMEL-15786
> URL: https://issues.apache.org/jira/browse/CAMEL-15786
> Project: Camel
> Issue Type: Bug
> Components: camel-openapi-java
>Affects Versions: 3.4.1, 3.6.0
>Reporter: Tomek
>Priority: Major
>
> According to [https://camel.apache.org/manual/latest/rest-dsl.html] by
> default the apiVendorExtension option should be set to false. But even when I
> set it manually to false, the produced JSON for OpenAPI still contains the x-
> fields like "x-camelContextId", "x-routeId" etc.
> I've tried to set this option both in Java using
> restConfiguration().apiVendorExtension(false) and in application.yml file of
> my Spring Boot application:
> {code:java}
> camel:
> rest:
> api-vendor-extension: false{code}
> I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
> result.
> Part of my pom.xml file:
> {code:java}
>
> org.apache.camel.springboot
> camel-rest-starter
> 3.4.1
>
>
> org.apache.camel.springboot
> camel-openapi-java-starter
> 3.4.1
>
> {code}
> Could you please check it? I don't want to expose internal development
> details via OpenAPI JSON file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15784) camel-core - Optimize with Bootstrap marker interface
[ https://issues.apache.org/jira/browse/CAMEL-15784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224296#comment-17224296 ] Claus Ibsen commented on CAMEL-15784: - See if we can optimize to avoid all those lambda classes for reifiers that stay in the jvm after starting and clearing the reifier models. > camel-core - Optimize with Bootstrap marker interface > - > > Key: CAMEL-15784 > URL: https://issues.apache.org/jira/browse/CAMEL-15784 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.0 > > > We can mark services that are used only during bootstrap with a marker > interface, and then when camel has been started it can detect those bootstrap > services and unload / clear them so they reduce memory etc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15786) Camel OpenAPI ignores apiVendorExtension option for REST binding
Tomek created CAMEL-15786:
-
Summary: Camel OpenAPI ignores apiVendorExtension option for REST
binding
Key: CAMEL-15786
URL: https://issues.apache.org/jira/browse/CAMEL-15786
Project: Camel
Issue Type: Bug
Components: camel-openapi-java
Affects Versions: 3.6.0, 3.4.1
Reporter: Tomek
According to [https://camel.apache.org/manual/latest/rest-dsl.html] by default
the apiVendorExtension option should be set to false. But even when I set it
manually to false, the produced JSON for OpenAPI still contains the x- fields
like "x-camelContextId", "x-routeId" etc.
I've tried to set this option both in Java using
restConfiguration().apiVendorExtension(false) and in application.yml file of my
Spring Boot application:
{code:java}
camel:
rest:
api-vendor-extension: false{code}
I've checked it on two versions of Camel (3.4.1, 3.6.0), both with the same
result.
Part of my pom.xml file:
{code:java}
org.apache.camel.springboot
camel-rest-starter
3.4.1
org.apache.camel.springboot
camel-openapi-java-starter
3.4.1
{code}
Could you please check it? I don't want to expose interlan development details
via OpenAPI JSON file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15782) camel-main - Optimize to clear camel-main own initial properties after startup
[ https://issues.apache.org/jira/browse/CAMEL-15782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-15782. - Resolution: Won't Fix You could in theory use the properties component to resolve those properties > camel-main - Optimize to clear camel-main own initial properties after startup > -- > > Key: CAMEL-15782 > URL: https://issues.apache.org/jira/browse/CAMEL-15782 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.0 > > > After camel-main has been started up, then its own properties that it loads > into an OrderedProperties is no longer in use, and we can clear it to reclaim > memory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15782) camel-main - Optimize to clear camel-main own initial properties after startup
[ https://issues.apache.org/jira/browse/CAMEL-15782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224273#comment-17224273 ] Claus Ibsen edited comment on CAMEL-15782 at 11/1/20, 4:25 PM: --- You could in theory use the properties component to resolve those properties at runtime. was (Author: davsclaus): You could in theory use the properties component to resolve those properties > camel-main - Optimize to clear camel-main own initial properties after startup > -- > > Key: CAMEL-15782 > URL: https://issues.apache.org/jira/browse/CAMEL-15782 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.0 > > > After camel-main has been started up, then its own properties that it loads > into an OrderedProperties is no longer in use, and we can clear it to reclaim > memory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15785) Camel-AWS2: make possibile to use a client based on DefaultCredentialProvider in all the interested components
Andrea Cosentino created CAMEL-15785: Summary: Camel-AWS2: make possibile to use a client based on DefaultCredentialProvider in all the interested components Key: CAMEL-15785 URL: https://issues.apache.org/jira/browse/CAMEL-15785 Project: Camel Issue Type: Task Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.x Like https://issues.apache.org/jira/browse/CAMEL-15779 This will make things easier for people using AWS services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-15784) camel-core - Optimize with Bootstrap marker interface
[ https://issues.apache.org/jira/browse/CAMEL-15784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-15784: --- Assignee: Claus Ibsen > camel-core - Optimize with Bootstrap marker interface > - > > Key: CAMEL-15784 > URL: https://issues.apache.org/jira/browse/CAMEL-15784 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.7.0 > > > We can mark services that are used only during bootstrap with a marker > interface, and then when camel has been started it can detect those bootstrap > services and unload / clear them so they reduce memory etc -- This message was sent by Atlassian Jira (v8.3.4#803005)
