[jira] [Updated] (CAMEL-13791) incoming message: Add QoS Information into a header
[ https://issues.apache.org/jira/browse/CAMEL-13791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-13791: - Summary: incoming message: Add QoS Information into a header (was: incoming message: Add QoS Information into an header ) > incoming message: Add QoS Information into a header > > > Key: CAMEL-13791 > URL: https://issues.apache.org/jira/browse/CAMEL-13791 > Project: Camel > Issue Type: Improvement > Components: camel-paho >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > > Today is impossible known QoS published MQTT message. > Add this information into an specific header -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13791) incoming message: Add QoS Information into an header
Fabrizio Spataro created CAMEL-13791: Summary: incoming message: Add QoS Information into an header Key: CAMEL-13791 URL: https://issues.apache.org/jira/browse/CAMEL-13791 Project: Camel Issue Type: Improvement Components: camel-paho Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Today is impossible known QoS published MQTT message. Add this information into an specific header -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13030) Thread lock using same mqtt endpoint into SpringDSL and Bean
[
https://issues.apache.org/jira/browse/CAMEL-13030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-13030:
-
Description:
Into my camel application, the thread is blocked when use same mqtt endpoint
specified into:
- Spring Application Context (Spring DSL)
- Spring bean (using ProducerTemplate inject by *EndpointInject* annotation)
I wrote a junit file into my github repo
https://github.com/Fabryprog/camel/tree/CAMEL-13030
You can reproduce it by:
{code:java}
mvn clean -Dtest=org.apache.camel.component.mqtt.MQTTEndpointInjectTemplateTest
test
{code}
was:
Into my camel application, the thread is blocked when use same mqtt endpoint
specified into:
- Spring Application Context (Spring DSL)
- Spring bean (using ProducerTemplate inject by *EndpointInject* annotation)
I wrote a junit file into my github repo
You can reproduce it by:
{code:java}
mvn clean -Dtest=org.apache.camel.component.mqtt.MQTTEndpointInjectTemplateTest
test
{code}
> Thread lock using same mqtt endpoint into SpringDSL and Bean
>
>
> Key: CAMEL-13030
> URL: https://issues.apache.org/jira/browse/CAMEL-13030
> Project: Camel
> Issue Type: Bug
> Components: camel-mqtt
>Affects Versions: 3.0.0
>Reporter: Fabrizio Spataro
>Priority: Blocker
>
> Into my camel application, the thread is blocked when use same mqtt endpoint
> specified into:
> - Spring Application Context (Spring DSL)
> - Spring bean (using ProducerTemplate inject by *EndpointInject* annotation)
> I wrote a junit file into my github repo
> https://github.com/Fabryprog/camel/tree/CAMEL-13030
> You can reproduce it by:
> {code:java}
> mvn clean
> -Dtest=org.apache.camel.component.mqtt.MQTTEndpointInjectTemplateTest test
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13030) Thread lock using same mqtt endpoint into SpringDSL and Bean
Fabrizio Spataro created CAMEL-13030:
Summary: Thread lock using same mqtt endpoint into SpringDSL and
Bean
Key: CAMEL-13030
URL: https://issues.apache.org/jira/browse/CAMEL-13030
Project: Camel
Issue Type: Bug
Components: camel-mqtt
Affects Versions: 3.0.0
Reporter: Fabrizio Spataro
Into my camel application, the thread is blocked when use same mqtt endpoint
specified into:
- Spring Application Context (Spring DSL)
- Spring bean (using ProducerTemplate inject by *EndpointInject* annotation)
I wrote a junit file into my github repo
You can reproduce it by:
{code:java}
mvn clean -Dtest=org.apache.camel.component.mqtt.MQTTEndpointInjectTemplateTest
test
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13014) camel mqtt crash using high volume traffic
Fabrizio Spataro created CAMEL-13014:
Summary: camel mqtt crash using high volume traffic
Key: CAMEL-13014
URL: https://issues.apache.org/jira/browse/CAMEL-13014
Project: Camel
Issue Type: Bug
Components: camel-mqtt
Affects Versions: 2.23.0
Reporter: Fabrizio Spataro
Assignee: Fabrizio Spataro
Into current version we cannot use 2 (or more) sequential camel-mqtt producer.
With high volume traffic use case, we have this looped error:
{quote}2018-12-18 16:27:12,609 [.0.1:36172@1101] WARN RegionBroker - Stealing
link for clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36176
2018-12-18 16:27:12,609 [.0.1:36170@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36172
2018-12-18 16:27:12,614 [.0.1:36180@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36170
2018-12-18 16:27:12,639 [.0.1:36182@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36180
2018-12-18 16:27:12,639 [.0.1:36184@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36182
2018-12-18 16:27:12,662 [.0.1:36186@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36184
2018-12-18 16:27:12,662 [.0.1:36190@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36186
2018-12-18 16:27:12,666 [.0.1:36178@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36190
2018-12-18 16:27:12,668 [.0.1:36188@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36192
2018-12-18 16:27:12,668 [.0.1:36192@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36178
2018-12-18 16:27:12,669 [.0.1:36196@1101] WARN RegionBroker - Stealing link for
clientId 7f01e92a5c1911c9 From Connection Transport Connection to:
tcp://127.0.0.1:36194
{quote}
You can reproduce it using junit class
*org.apache.camel.component.mqtt.MQTTLoopProducerTest*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12810) [IPFS] Add support for IPFS
[ https://issues.apache.org/jira/browse/CAMEL-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617460#comment-16617460 ] Fabrizio Spataro commented on CAMEL-12810: -- Are you thinking to integrate this lib? https://github.com/ipfs/java-ipfs-api > [IPFS] Add support for IPFS > --- > > Key: CAMEL-12810 > URL: https://issues.apache.org/jira/browse/CAMEL-12810 > Project: Camel > Issue Type: New Feature >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > https://ipfs.io/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12815) A new Component IOTA
Fabrizio Spataro created CAMEL-12815: Summary: A new Component IOTA Key: CAMEL-12815 URL: https://issues.apache.org/jira/browse/CAMEL-12815 Project: Camel Issue Type: New Feature Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Hello everyone. i am able to write a new component to integrate DLT. IOTA Project is an open-source distributed ledger project that is being built to power the future of the Internet of Things with feeless microtransactions and data integrity for machines (from its website) I am writing Producer component (to send data to the tangle), later i will write other functionalities. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12807) Avoid to use endpoint attribute when MqttConnectOptions is declared once
Fabrizio Spataro created CAMEL-12807: Summary: Avoid to use endpoint attribute when MqttConnectOptions is declared once Key: CAMEL-12807 URL: https://issues.apache.org/jira/browse/CAMEL-12807 Project: Camel Issue Type: Bug Components: camel-paho Affects Versions: 2.22.2 Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Hello, In my system i have a default MqttConnectOptions declared into spring context and some other camel consumers/producers connected to others mqtt servers. So today i cannot use endpoint parameters without declare an another mqttConnectOptions class because the endpoint code suppose that use ALWAYS MqttConnectOptions (if it is declared once) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12122) S3: Add createDownloadLink functionality
Fabrizio Spataro created CAMEL-12122: Summary: S3: Add createDownloadLink functionality Key: CAMEL-12122 URL: https://issues.apache.org/jira/browse/CAMEL-12122 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Hello! I write code to add a new operation into producer to create a download s3 link The functionality, according with *CamelAwsS3DownloadLinkExpiration* header, must return an header *CamelAwsS3DownloadLink* -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-12118) DynamoDB: Execute query using secondary indexes
Fabrizio Spataro created CAMEL-12118: Summary: DynamoDB: Execute query using secondary indexes Key: CAMEL-12118 URL: https://issues.apache.org/jira/browse/CAMEL-12118 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Current code isn't able to indicate a secondary index name into a query operation -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11628) MQTT Connection loop
[ https://issues.apache.org/jira/browse/CAMEL-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123022#comment-16123022 ] Fabrizio Spataro commented on CAMEL-11628: -- No. I tried to fix it but the bug is on the fuse library > MQTT Connection loop > > > Key: CAMEL-11628 > URL: https://issues.apache.org/jira/browse/CAMEL-11628 > Project: Camel > Issue Type: Bug > Components: camel-mqtt >Reporter: Fabrizio Spataro > > Hello everyone, i found an particular bug situation > I have same mqtt producer with high volume traffic. When my application losts > tcp connection to mqtt server i have follow connection loop error. This bug > is sometime verified because it depend by multiple factors (load machine, > load mqtt server, payload, etc) > I am reading source code and i suppose that the bug is introduced by volatile > variable connected (it isn't thread-safe) > To resolve this bug you must refactoring all MQTTEndpoint connection code. > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 > [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT > Connection connected to tcp://mqtt:1883 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11642) Broker Credentials should be set from endpoint
[ https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-11642: - Summary: Broker Credentials should be set from endpoint (was: Broken Credentials should be set from endpoint) > Broker Credentials should be set from endpoint > -- > > Key: CAMEL-11642 > URL: https://issues.apache.org/jira/browse/CAMEL-11642 > Project: Camel > Issue Type: Improvement > Components: camel-paho >Affects Versions: 2.19.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > current camel-paho component uses a MqttConnectOptions to set broker > credentials. > It is a very limit into a dynamically application. The credential should be > configured from endpoint too (like qos and retain flag) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11642) Broken Credentials should be set from endpoint
[ https://issues.apache.org/jira/browse/CAMEL-11642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro reassigned CAMEL-11642: Assignee: Fabrizio Spataro > Broken Credentials should be set from endpoint > -- > > Key: CAMEL-11642 > URL: https://issues.apache.org/jira/browse/CAMEL-11642 > Project: Camel > Issue Type: Improvement > Components: camel-paho >Affects Versions: 2.19.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > current camel-paho component uses a MqttConnectOptions to set broker > credentials. > It is a very limit into a dynamically application. The credential should be > configured from endpoint too (like qos and retain flag) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11642) Broken Credentials should be set from endpoint
Fabrizio Spataro created CAMEL-11642: Summary: Broken Credentials should be set from endpoint Key: CAMEL-11642 URL: https://issues.apache.org/jira/browse/CAMEL-11642 Project: Camel Issue Type: Improvement Components: camel-paho Affects Versions: 2.19.2 Reporter: Fabrizio Spataro current camel-paho component uses a MqttConnectOptions to set broker credentials. It is a very limit into a dynamically application. The credential should be configured from endpoint too (like qos and retain flag) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11633) Upgrade client mqtt paho base lib
[ https://issues.apache.org/jira/browse/CAMEL-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114449#comment-16114449 ] Fabrizio Spataro commented on CAMEL-11633: -- I'm so sorry! > Upgrade client mqtt paho base lib > - > > Key: CAMEL-11633 > URL: https://issues.apache.org/jira/browse/CAMEL-11633 > Project: Camel > Issue Type: Task > Components: camel-paho >Affects Versions: 2.19.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > Fix For: 2.20.0 > > > camel-paho use an old library. There is an update! > 1.1.1 Mar, 2017 > 1.1.0 Jun, 2016 (current) > source: > https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11633) Upgrade client mqtt paho base lib
[ https://issues.apache.org/jira/browse/CAMEL-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro resolved CAMEL-11633. -- Resolution: Fixed Fix Version/s: (was: 2.19.2) 2.19.3 > Upgrade client mqtt paho base lib > - > > Key: CAMEL-11633 > URL: https://issues.apache.org/jira/browse/CAMEL-11633 > Project: Camel > Issue Type: Task > Components: camel-paho >Affects Versions: 2.19.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > Fix For: 2.19.3 > > > camel-paho use an old library. There is an update! > 1.1.1 Mar, 2017 > 1.1.0 Jun, 2016 (current) > source: > https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11633) Upgrade client mqtt paho base lib
[ https://issues.apache.org/jira/browse/CAMEL-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-11633: - Affects Version/s: 2.19.2 > Upgrade client mqtt paho base lib > - > > Key: CAMEL-11633 > URL: https://issues.apache.org/jira/browse/CAMEL-11633 > Project: Camel > Issue Type: Task > Components: camel-paho >Affects Versions: 2.19.2 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > Fix For: 2.20.0 > > > camel-paho use an old library. There is an update! > 1.1.1 Mar, 2017 > 1.1.0 Jun, 2016 (current) > source: > https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11633) Upgrade client mqtt paho base lib
[ https://issues.apache.org/jira/browse/CAMEL-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-11633: - Fix Version/s: 2.19.2 > Upgrade client mqtt paho base lib > - > > Key: CAMEL-11633 > URL: https://issues.apache.org/jira/browse/CAMEL-11633 > Project: Camel > Issue Type: Task > Components: camel-paho >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > Fix For: 2.19.2 > > > camel-paho use an old library. There is an update! > 1.1.1 Mar, 2017 > 1.1.0 Jun, 2016 (current) > source: > https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11633) Upgrade client mqtt paho base lib
[ https://issues.apache.org/jira/browse/CAMEL-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro reassigned CAMEL-11633: Assignee: Fabrizio Spataro > Upgrade client mqtt paho base lib > - > > Key: CAMEL-11633 > URL: https://issues.apache.org/jira/browse/CAMEL-11633 > Project: Camel > Issue Type: Task > Components: camel-paho >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > > camel-paho use an old library. There is an update! > 1.1.1 Mar, 2017 > 1.1.0 Jun, 2016 (current) > source: > https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11633) Upgrade client mqtt paho base lib
Fabrizio Spataro created CAMEL-11633: Summary: Upgrade client mqtt paho base lib Key: CAMEL-11633 URL: https://issues.apache.org/jira/browse/CAMEL-11633 Project: Camel Issue Type: Task Components: camel-paho Reporter: Fabrizio Spataro Priority: Minor camel-paho use an old library. There is an update! 1.1.1 Mar, 2017 1.1.0 Jun, 2016 (current) source: https://mvnrepository.com/artifact/org.eclipse.paho/org.eclipse.paho.client.mqttv3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11631) Camel-Paho Missiong reconnect logic
[
https://issues.apache.org/jira/browse/CAMEL-11631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro resolved CAMEL-11631.
--
Resolution: Fixed
Fix Version/s: 2.19.3
> Camel-Paho Missiong reconnect logic
> ---
>
> Key: CAMEL-11631
> URL: https://issues.apache.org/jira/browse/CAMEL-11631
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
> Fix For: 2.19.3
>
>
> When it loses the connection, it is not restored.
> You have to write the reconnection logic
> {noformat}
> [thread #2 - seda://sendToMqtt2] SedaConsumer WARN Error
> processing exchange. Exchange[]. Caused by:
> [org.eclipse.paho.client.mqttv3.MqttException - Client is not connected]
> Client is not connected (32104)
> at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:166)
> at
> org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:1027)
> at
> org.eclipse.paho.client.mqttv3.MqttClient.publish(MqttClient.java:399)
> at
> org.apache.camel.component.paho.PahoProducer.process(PahoProducer.java:43)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:298)
> at
> org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:207)
> at
> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:154)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11631) Camel-Paho Missiong reconnect logic
[
https://issues.apache.org/jira/browse/CAMEL-11631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-11631:
-
Affects Version/s: (was: 2.19.1)
2.19.2
> Camel-Paho Missiong reconnect logic
> ---
>
> Key: CAMEL-11631
> URL: https://issues.apache.org/jira/browse/CAMEL-11631
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
>Affects Versions: 2.19.2
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> When it loses the connection, it is not restored.
> You have to write the reconnection logic
> {noformat}
> [thread #2 - seda://sendToMqtt2] SedaConsumer WARN Error
> processing exchange. Exchange[]. Caused by:
> [org.eclipse.paho.client.mqttv3.MqttException - Client is not connected]
> Client is not connected (32104)
> at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:166)
> at
> org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:1027)
> at
> org.eclipse.paho.client.mqttv3.MqttClient.publish(MqttClient.java:399)
> at
> org.apache.camel.component.paho.PahoProducer.process(PahoProducer.java:43)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:298)
> at
> org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:207)
> at
> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:154)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11631) Camel-Paho Missiong reconnect logic
[
https://issues.apache.org/jira/browse/CAMEL-11631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro reassigned CAMEL-11631:
Assignee: Fabrizio Spataro
> Camel-Paho Missiong reconnect logic
> ---
>
> Key: CAMEL-11631
> URL: https://issues.apache.org/jira/browse/CAMEL-11631
> Project: Camel
> Issue Type: Bug
> Components: camel-paho
>Affects Versions: 2.19.1
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> When it loses the connection, it is not restored.
> You have to write the reconnection logic
> {noformat}
> [thread #2 - seda://sendToMqtt2] SedaConsumer WARN Error
> processing exchange. Exchange[]. Caused by:
> [org.eclipse.paho.client.mqttv3.MqttException - Client is not connected]
> Client is not connected (32104)
> at
> org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
> at
> org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:166)
> at
> org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:1027)
> at
> org.eclipse.paho.client.mqttv3.MqttClient.publish(MqttClient.java:399)
> at
> org.apache.camel.component.paho.PahoProducer.process(PahoProducer.java:43)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
> at
> org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:298)
> at
> org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:207)
> at
> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:154)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11631) Camel-Paho Missiong reconnect logic
Fabrizio Spataro created CAMEL-11631:
Summary: Camel-Paho Missiong reconnect logic
Key: CAMEL-11631
URL: https://issues.apache.org/jira/browse/CAMEL-11631
Project: Camel
Issue Type: Bug
Components: camel-paho
Affects Versions: 2.19.1
Reporter: Fabrizio Spataro
When it loses the connection, it is not restored.
You have to write the reconnection logic
{noformat}
[thread #2 - seda://sendToMqtt2] SedaConsumer WARN Error
processing exchange. Exchange[]. Caused by:
[org.eclipse.paho.client.mqttv3.MqttException - Client is not connected]
Client is not connected (32104)
at
org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
at
org.eclipse.paho.client.mqttv3.internal.ClientComms.sendNoWait(ClientComms.java:166)
at
org.eclipse.paho.client.mqttv3.MqttAsyncClient.publish(MqttAsyncClient.java:1027)
at
org.eclipse.paho.client.mqttv3.MqttClient.publish(MqttClient.java:399)
at
org.apache.camel.component.paho.PahoProducer.process(PahoProducer.java:43)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:541)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:198)
at
org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:298)
at
org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:207)
at
org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:154)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11628) MQTT Connection loop
[ https://issues.apache.org/jira/browse/CAMEL-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-11628: - Description: Hello everyone, i found an particular bug situation I have same mqtt producer with high volume traffic. When my application losts tcp connection to mqtt server i have follow connection loop error. This bug is sometime verified because it depend by multiple factors (load machine, load mqtt server, payload, etc) I am reading source code and i suppose that the bug is introduced by volatile variable connected (it isn't thread-safe) To resolve this bug you must refactoring all MQTTEndpoint connection code. [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 was: Hello everyone, i found an particular bug situation I have same mqtt producer with high volume traffic. When my application losts tcp connection to mqtt server i have follow connection loop error. This bug is sometime verified because it depend by multiple factors (load machine, load mqtt server, payload, etc) I am reading source code and i suppose that the bug is introduced by volatile variable connected (it isn't thread-safe) To resolve this bug you must refactoring all MQTTEndpoint connection code. ``` [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [
[jira] [Updated] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Priority: Minor (was: Major) > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast, documentation >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.18.0 > > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, this feature is > already present into code using headers: CamelHazelcastObjectTtlValue and > CamelHazelcastObjectTtlUnit > unfortunately it is not present in documentation!!! > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Priority: Major (was: Minor) > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast, documentation >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen > Fix For: 2.18.0 > > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, this feature is > already present into code using headers: CamelHazelcastObjectTtlValue and > CamelHazelcastObjectTtlUnit > unfortunately it is not present in documentation!!! > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11628) MQTT Connection loop
Fabrizio Spataro created CAMEL-11628: Summary: MQTT Connection loop Key: CAMEL-11628 URL: https://issues.apache.org/jira/browse/CAMEL-11628 Project: Camel Issue Type: Bug Components: camel-mqtt Reporter: Fabrizio Spataro Hello everyone, i found an particular bug situation I have same mqtt producer with high volume traffic. When my application losts tcp connection to mqtt server i have follow connection loop error. This bug is sometime verified because it depend by multiple factors (load machine, load mqtt server, payload, etc) I am reading source code and i suppose that the bug is introduced by volatile variable connected (it isn't thread-safe) To resolve this bug you must refactoring all MQTTEndpoint connection code. ``` [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 [hawtdispatch-DEFAULT-3] MQTTEndpoint INFO MQTT Connection connected to tcp://mqtt:1883 ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097572#comment-16097572 ] Fabrizio Spataro commented on CAMEL-11455: -- sorry guys but i cannot fix it before 1st August! > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen > Fix For: 2.20.0, 2.19.3 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11541) Telegram Button / Keyboard / Position
Fabrizio Spataro created CAMEL-11541: Summary: Telegram Button / Keyboard / Position Key: CAMEL-11541 URL: https://issues.apache.org/jira/browse/CAMEL-11541 Project: Camel Issue Type: Improvement Components: camel-telegram Reporter: Fabrizio Spataro Priority: Minor Telegram component manage a basic type of message (text, video, image, audio) but there are any functionalities not implemeted yet. For example: Keyboards, buttons, Positions (lat/lon) etc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro reassigned CAMEL-11455: Assignee: Fabrizio Spataro > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > Fix For: 2.19.2, 2.20.0 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16066463#comment-16066463 ] Fabrizio Spataro commented on CAMEL-11455: -- [~davsclaus] now it is work fine. I am fixing test files and i am going to send the github PR. Thanks > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro > Fix For: 2.19.2, 2.20.0 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-11455: - Attachment: jsonFormatterDisappear.zip The source code > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-core, camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
Fabrizio Spataro created CAMEL-11455: Summary: Automatic transform String to DBObject after previous conversion error Key: CAMEL-11455 URL: https://issues.apache.org/jira/browse/CAMEL-11455 Project: Camel Issue Type: Bug Components: camel-core, camel-mongodb, camel-mongodb3 Affects Versions: 2.19.1 Reporter: Fabrizio Spataro Hello, i found a bug. To reproduce it you can execute the code (see attachment file). The bug is simple: After an invalid conversion, the automatic String -> JSON transformation used to put a document into MongoDB collection, fail! Application flow: # First document can be convert to JSON, Mongodb create a document (correct) # Second document has an error, Mongodb cannot create a document (correct) # Third document can be convert to JSON but Mongodb cannot create a document into collection because automatic conversion is broken!!! (BUG) Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-10353) Enable Hazelcast Distributed Computing
[ https://issues.apache.org/jira/browse/CAMEL-10353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010224#comment-16010224 ] Fabrizio Spataro commented on CAMEL-10353: -- Hello luca, Sure, Give me 2 weeks to resolve this issue! > Enable Hazelcast Distributed Computing > -- > > Key: CAMEL-10353 > URL: https://issues.apache.org/jira/browse/CAMEL-10353 > Project: Camel > Issue Type: Improvement > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > Add the ability to execute distributed task through Hazelcast Cluster > http://docs.hazelcast.org/docs/3.7/manual/html-single/index.html#distributed-computing -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CAMEL-10337) camel-asterix - Endpoint should be singleton
[
https://issues.apache.org/jira/browse/CAMEL-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932539#comment-15932539
]
Fabrizio Spataro commented on CAMEL-10337:
--
I pull your code and running JUnit test using our asterisk server.
There are results:
AsteriskProducerTest is done.
AsteriskConfigTest is done.
AsteristConsumerTest is failure with error:
{code}
java.lang.AssertionError: mock://result Received message count 0, expected at
least 1
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1452)
at
org.apache.camel.component.mock.MockEndpoint.assertTrue(MockEndpoint.java:1440)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:414)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:386)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:374)
at
org.apache.camel.component.asterisk.AsteriskConsumerTest.testReceiveTraps(AsteriskConsumerTest.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
{code}
> camel-asterix - Endpoint should be singleton
>
>
> Key: CAMEL-10337
> URL: https://issues.apache.org/jira/browse/CAMEL-10337
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
>Priority: Minor
> Fix For: 2.19.0
>
>
> We should favor to not store state on the endpoint but keep them as plain
> configuration.
> I added a TODO in the endpoint source code.
> Also is the hostname option required to be configured? I think so, and if so
> then add required=true to the UriParam. And also add some logic to check its
> configured.
> And also when the consumer stops, then the listener should be removed, eg
> when you add a listetener, you should consider to also remove it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-10337) camel-asterix - Endpoint should be singleton
[ https://issues.apache.org/jira/browse/CAMEL-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15930037#comment-15930037 ] Fabrizio Spataro commented on CAMEL-10337: -- I saw the code, Give me more time to try it with junit test using our asterisk server. > camel-asterix - Endpoint should be singleton > > > Key: CAMEL-10337 > URL: https://issues.apache.org/jira/browse/CAMEL-10337 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 2.19.0 > > > We should favor to not store state on the endpoint but keep them as plain > configuration. > I added a TODO in the endpoint source code. > Also is the hostname option required to be configured? I think so, and if so > then add required=true to the UriParam. And also add some logic to check its > configured. > And also when the consumer stops, then the listener should be removed, eg > when you add a listetener, you should consider to also remove it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (CAMEL-10560) Add submittedFileName into AttachmentHttpBinding
Fabrizio Spataro created CAMEL-10560: Summary: Add submittedFileName into AttachmentHttpBinding Key: CAMEL-10560 URL: https://issues.apache.org/jira/browse/CAMEL-10560 Project: Camel Issue Type: Task Components: camel-servlet Affects Versions: 2.18.0 Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Priority: Minor Add new proxy method getSubmittedFileName() into PartDataSource nested class. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701770#comment-15701770
]
Fabrizio Spataro commented on CAMEL-10492:
--
I found a workaround to fix my problem:
Updating my software to 2.18 version my attachments aren't available, now my
servlet code is:
{code:xml}
{code}
i am using two parameters:
- disableStreamCache, *is original problem*. With streamcache enable
attachment files aren't available to jetty multicast parser
- attachmentMultipartBinding, to enable AttachmentHttpBinding into servlet
endpoint
my old code is:
{code:xml}
{code}
[~davsclaus] evaluate you what to do with this issue!
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15701561#comment-15701561
]
Fabrizio Spataro commented on CAMEL-10492:
--
I have found a bug into this code.
I am trying to fix it!
{code:java}
final class AttachmentHttpBinding extends DefaultHttpBinding {
..
protected void populateAttachments(HttpServletRequest request, HttpMessage
message) {
try {
Collection parts = request.getParts();
for (Part part : parts) {
DataSource ds = new PartDataSource(part);
Attachment attachment = new DefaultAttachment(ds);
for (String headerName : part.getHeaderNames()) {
for (String headerValue : part.getHeaders(headerName)) {
attachment.addHeader(headerName, headerValue);
}
}
message.addAttachmentObject(part.getName(), attachment);
}
} catch (Exception e) {
throw new RuntimeCamelException("Cannot populate attachments", e);
}
}
...
}
{code}
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: Future
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro reopened CAMEL-10492:
--
please, look at my last comment
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15683561#comment-15683561
]
Fabrizio Spataro commented on CAMEL-10492:
--
[~davsclaus] This bug is more complex than it looks. When i set
attachmentMultipartBinding property i have another error.
It isn't a jetty bug (i had test it with junit) but it, i suppose, is a camel
body trasformation bug. I do not know so thoroughly to understand it. Can you
help me?
You can use my zip attach file to debug it!
Stacktrace
{code}
org.apache.camel.RuntimeCamelException: Cannot populate attachments
at
org.apache.camel.component.servlet.AttachmentHttpBinding.populateAttachments(AttachmentHttpBinding.java:58)
at
org.apache.camel.http.common.DefaultHttpBinding.readBody(DefaultHttpBinding.java:209)
at
org.apache.camel.http.common.DefaultHttpBinding.readRequest(DefaultHttpBinding.java:107)
at org.apache.camel.http.common.HttpMessage.(HttpMessage.java:52)
at
org.apache.camel.http.common.CamelServlet.doService(CamelServlet.java:169)
at
org.apache.camel.http.common.CamelServlet.service(CamelServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:830)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:551)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1589)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1213)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:486)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1552)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1126)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:118)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:549)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:254)
at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:269)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:97)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Missing content for multipart request
at
org.eclipse.jetty.util.MultiPartInputStreamParser.parse(MultiPartInputStreamParser.java:541)
at
org.eclipse.jetty.util.MultiPartInputStreamParser.getParts(MultiPartInputStreamParser.java:429)
at org.eclipse.jetty.server.Request.getParts(Request.java:2300)
at org.eclipse.jetty.server.Request.getParts(Request.java:2279)
{code}
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Claus Ibsen
> Fix For: 2.18.1, 2.19.0
>
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-10492:
-
Description:
I send a multipart form data to my camel servlet, before camel 2.18 attachment
object is ok now is empty!
Now i have an *header* every form field but every field is java.lang.String
So, I can not post any binary file.
This is my web.xml filter
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
was:
I send a multipart form data to my camel servlet, before camel 2.18 attachment
object is empty.
Now i have an *header* every form field but every field is java.lang.String
So, I can not post any binary file.
This is my web.xml filter
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is ok now is empty!
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10492) Camel Servlet, attachment object is empty
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-10492:
-
Affects Version/s: 2.18.0
Priority: Major (was: Minor)
Description:
I send a multipart form data to my camel servlet, before camel 2.18 attachment
object is empty.
Now i have an *header* every form field but every field is java.lang.String
So, I can not post any binary file.
This is my web.xml filter
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
was:
Since 2.18 i have a new bug!
I send a multipart form data to my camel servlet, before camel 2.18 i have an
*attachment object* every form field.
Now i have an *header* every form field.
It is ok but ALL header (form field) are instance of java.lang.String
So, I can not post any binary file.
Is it a camel bug?
This is my filter into web.xml
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
Component/s: camel-http-common
Summary: Camel Servlet, attachment object is empty (was: Camel
Servlet, headers instance of String)
> Camel Servlet, attachment object is empty
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-servlet
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
> Attachments: camel-example-servlet-attachment.zip
>
>
> I send a multipart form data to my camel servlet, before camel 2.18
> attachment object is empty.
> Now i have an *header* every form field but every field is java.lang.String
> So, I can not post any binary file.
> This is my web.xml filter
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (CAMEL-10492) Camel Servlet, headers instance of String
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676309#comment-15676309
]
Fabrizio Spataro edited comment on CAMEL-10492 at 11/18/16 9:38 AM:
i am reading camel source code.
Into camel 2.18 the attribute atttachmentMultipartBinding is never set
(look at
https://github.com/apache/camel/search?utf8=%E2%9C%93=setAttachmentMultipartBinding)
{code:java}
/**
* Whether to automatic bind multipart/form-data as attachments on the
Camel {@link Exchange}.
*
* This is turn off by default as this may require servet specific
configuration to enable this when using Servlet's.
*/
public void setAttachmentMultipartBinding(boolean attachmentMultipartBinding) {
this.attachmentMultipartBinding = attachmentMultipartBinding;
}
{code}
so this check is always false:
{code:java}
public class ServletEndpoint extends HttpCommonEndpoint {
.
.
public HttpBinding getHttpBinding() {
// make sure we include servlet variant of the http binding
if (this.binding == null) {
// is attachment binding enabled?
if (getComponent().isAttachmentMultipartBinding()) {
this.binding = new AttachmentHttpBinding();
} else {
this.binding = new DefaultHttpBinding();
}
...
...
}
return this.binding;
}
{code}
was (Author: fabryprog):
i am reading camel source code.
Into camel 2.18 the attribute atttachmentMultipartBinding is never set
(look at
https://github.com/apache/camel/search?utf8=%E2%9C%93=setAttachmentMultipartBinding)
{code:java}
/**
* Whether to automatic bind multipart/form-data as attachments on the
Camel {@link Exchange}.
*
* This is turn off by default as this may require servet specific
configuration to enable this when using Servlet's.
*/
public void setAttachmentMultipartBinding(boolean attachmentMultipartBinding) {
this.attachmentMultipartBinding = attachmentMultipartBinding;
}
{code}
> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an
> *attachment object* every form field.
> Now i have an *header* every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug?
> This is my filter into web.xml
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10492) Camel Servlet, headers instance of String
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676309#comment-15676309
]
Fabrizio Spataro commented on CAMEL-10492:
--
i am reading camel source code.
Into camel 2.18 the attribute atttachmentMultipartBinding is never set
(look at
https://github.com/apache/camel/search?utf8=%E2%9C%93=setAttachmentMultipartBinding)
{code:java}
/**
* Whether to automatic bind multipart/form-data as attachments on the
Camel {@link Exchange}.
*
* This is turn off by default as this may require servet specific
configuration to enable this when using Servlet's.
*/
public void setAttachmentMultipartBinding(boolean attachmentMultipartBinding) {
this.attachmentMultipartBinding = attachmentMultipartBinding;
}
{code}
> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an
> *attachment object* every form field.
> Now i have an *header* every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug?
> This is my filter into web.xml
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10492) Camel Servlet, headers instance of String
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-10492:
-
Attachment: camel-example-servlet-attachment.zip
> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an
> attachment object every form field.
> Now i have an header every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug?
> This is my filter into web.xml
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10492) Camel Servlet, headers instance of String
[
https://issues.apache.org/jira/browse/CAMEL-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-10492:
-
Description:
Since 2.18 i have a new bug!
I send a multipart form data to my camel servlet, before camel 2.18 i have an
*attachment object* every form field.
Now i have an *header* every form field.
It is ok but ALL header (form field) are instance of java.lang.String
So, I can not post any binary file.
Is it a camel bug?
This is my filter into web.xml
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
was:
Since 2.18 i have a new bug!
I send a multipart form data to my camel servlet, before camel 2.18 i have an
attachment object every form field.
Now i have an header every form field.
It is ok but ALL header (form field) are instance of java.lang.String
So, I can not post any binary file.
Is it a camel bug?
This is my filter into web.xml
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
> Camel Servlet, headers instance of String
> -
>
> Key: CAMEL-10492
> URL: https://issues.apache.org/jira/browse/CAMEL-10492
> Project: Camel
> Issue Type: Bug
> Components: camel-servlet
>Reporter: Fabrizio Spataro
>Priority: Minor
> Attachments: camel-example-servlet-attachment.zip
>
>
> Since 2.18 i have a new bug!
> I send a multipart form data to my camel servlet, before camel 2.18 i have an
> *attachment object* every form field.
> Now i have an *header* every form field.
> It is ok but ALL header (form field) are instance of java.lang.String
> So, I can not post any binary file.
> Is it a camel bug?
> This is my filter into web.xml
> {code:xml}
>
> MultipartFilter
>
> org.eclipse.jetty.servlets.MultiPartFilter
>
>
> MultipartFilter
> CamelServlet
>
> {code}
> Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-10492) Camel Servlet, headers instance of String
Fabrizio Spataro created CAMEL-10492:
Summary: Camel Servlet, headers instance of String
Key: CAMEL-10492
URL: https://issues.apache.org/jira/browse/CAMEL-10492
Project: Camel
Issue Type: Bug
Components: camel-servlet
Reporter: Fabrizio Spataro
Priority: Minor
Since 2.18 i have a new bug!
I send a multipart form data to my camel servlet, before camel 2.18 i have an
attachment object every form field.
Now i have an header every form field.
It is ok but ALL header (form field) are instance of java.lang.String
So, I can not post any binary file.
Is it a camel bug?
This is my filter into web.xml
{code:xml}
MultipartFilter
org.eclipse.jetty.servlets.MultiPartFilter
MultipartFilter
CamelServlet
{code}
Into zip file, you can found an example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (CAMEL-10428) Cannot compile master code
[ https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro closed CAMEL-10428. > Cannot compile master code > -- > > Key: CAMEL-10428 > URL: https://issues.apache.org/jira/browse/CAMEL-10428 > Project: Camel > Issue Type: Task >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > mvn clean install -Pfastinstall > i have this error, i am skipping JMX component to compile master code: > [INFO] Camel :: Jing .. SUCCESS [ 8.585 > s] > [INFO] Camel :: JIRA .. SUCCESS [ 27.211 > s] > [INFO] Camel :: JMX ... FAILURE [ 4.836 > s] > [INFO] Camel :: Jolt .. SKIPPED > [INFO] Camel :: Johnzon ... SKIPPED > > > [INFO] Camel :: Example :: Zipkin :: Service 1 SKIPPED > [INFO] Camel :: Example :: Zipkin :: Service 2 SKIPPED > [INFO] Camel :: Assembly .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 29:14 min > [INFO] Finished at: 2016-11-01T08:10:53+01:00 > [INFO] Final Memory: 1212M/2906M > [INFO] > > [ERROR] Failed to execute goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project > camel-jmx: Execution default of goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal > pattern character 'g' -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-10428) Cannot compile master code
[ https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro resolved CAMEL-10428. -- Resolution: Not A Problem Assignee: Fabrizio Spataro I resolve it using english language > Cannot compile master code > -- > > Key: CAMEL-10428 > URL: https://issues.apache.org/jira/browse/CAMEL-10428 > Project: Camel > Issue Type: Task >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > mvn clean install -Pfastinstall > i have this error, i am skipping JMX component to compile master code: > [INFO] Camel :: Jing .. SUCCESS [ 8.585 > s] > [INFO] Camel :: JIRA .. SUCCESS [ 27.211 > s] > [INFO] Camel :: JMX ... FAILURE [ 4.836 > s] > [INFO] Camel :: Jolt .. SKIPPED > [INFO] Camel :: Johnzon ... SKIPPED > > > [INFO] Camel :: Example :: Zipkin :: Service 1 SKIPPED > [INFO] Camel :: Example :: Zipkin :: Service 2 SKIPPED > [INFO] Camel :: Assembly .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 29:14 min > [INFO] Finished at: 2016-11-01T08:10:53+01:00 > [INFO] Final Memory: 1212M/2906M > [INFO] > > [ERROR] Failed to execute goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project > camel-jmx: Execution default of goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal > pattern character 'g' -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10428) Cannot compile master code
[ https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624685#comment-15624685 ] Fabrizio Spataro commented on CAMEL-10428: -- i have maven default settings + "-Xms3000m -Xmx3000m" and italian language! I will try to change language so there is a new mandatory compile option? With camel-2.18 it is all ok > Cannot compile master code > -- > > Key: CAMEL-10428 > URL: https://issues.apache.org/jira/browse/CAMEL-10428 > Project: Camel > Issue Type: Task >Reporter: Fabrizio Spataro > > mvn clean install -Pfastinstall > i have this error, i am skipping JMX component to compile master code: > [INFO] Camel :: Jing .. SUCCESS [ 8.585 > s] > [INFO] Camel :: JIRA .. SUCCESS [ 27.211 > s] > [INFO] Camel :: JMX ... FAILURE [ 4.836 > s] > [INFO] Camel :: Jolt .. SKIPPED > [INFO] Camel :: Johnzon ... SKIPPED > > > [INFO] Camel :: Example :: Zipkin :: Service 1 SKIPPED > [INFO] Camel :: Example :: Zipkin :: Service 2 SKIPPED > [INFO] Camel :: Assembly .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 29:14 min > [INFO] Finished at: 2016-11-01T08:10:53+01:00 > [INFO] Final Memory: 1212M/2906M > [INFO] > > [ERROR] Failed to execute goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project > camel-jmx: Execution default of goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal > pattern character 'g' -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10428) Cannot compile master code
[ https://issues.apache.org/jira/browse/CAMEL-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15624642#comment-15624642 ] Fabrizio Spataro commented on CAMEL-10428: -- There is another compile error: [INFO] Camel :: Olingo2 :: Parent . SUCCESS [ 0.117 s] [INFO] Camel :: Olingo2 :: API SUCCESS [ 4.143 s] [INFO] Camel :: Olingo2 :: Component .. FAILURE [ 3.385 s] [INFO] Camel :: OpenShift (deprecated) SKIPPED [INFO] Camel :: OptaPlanner ... SKIPPED .. [INFO] Camel :: Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:11 min [INFO] Finished at: 2016-11-01T08:25:50+01:00 [INFO] Final Memory: 1089M/2929M [INFO] [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (generate-sources) on project camel-olingo2: Command execution failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > Cannot compile master code > -- > > Key: CAMEL-10428 > URL: https://issues.apache.org/jira/browse/CAMEL-10428 > Project: Camel > Issue Type: Task >Reporter: Fabrizio Spataro > > mvn clean install -Pfastinstall > i have this error, i am skipping JMX component to compile master code: > [INFO] Camel :: Jing .. SUCCESS [ 8.585 > s] > [INFO] Camel :: JIRA .. SUCCESS [ 27.211 > s] > [INFO] Camel :: JMX ... FAILURE [ 4.836 > s] > [INFO] Camel :: Jolt .. SKIPPED > [INFO] Camel :: Johnzon ... SKIPPED > > > [INFO] Camel :: Example :: Zipkin :: Service 1 SKIPPED > [INFO] Camel :: Example :: Zipkin :: Service 2 SKIPPED > [INFO] Camel :: Assembly .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 29:14 min > [INFO] Finished at: 2016-11-01T08:10:53+01:00 > [INFO] Final Memory: 1212M/2906M > [INFO] > > [ERROR] Failed to execute goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project > camel-jmx: Execution default of goal > org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal > pattern character 'g' -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10428) Cannot compile master code
Fabrizio Spataro created CAMEL-10428: Summary: Cannot compile master code Key: CAMEL-10428 URL: https://issues.apache.org/jira/browse/CAMEL-10428 Project: Camel Issue Type: Task Reporter: Fabrizio Spataro mvn clean install -Pfastinstall i have this error, i am skipping JMX component to compile master code: [INFO] Camel :: Jing .. SUCCESS [ 8.585 s] [INFO] Camel :: JIRA .. SUCCESS [ 27.211 s] [INFO] Camel :: JMX ... FAILURE [ 4.836 s] [INFO] Camel :: Jolt .. SKIPPED [INFO] Camel :: Johnzon ... SKIPPED [INFO] Camel :: Example :: Zipkin :: Service 1 SKIPPED [INFO] Camel :: Example :: Zipkin :: Service 2 SKIPPED [INFO] Camel :: Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 29:14 min [INFO] Finished at: 2016-11-01T08:10:53+01:00 [INFO] Final Memory: 1212M/2906M [INFO] [ERROR] Failed to execute goal org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate (default) on project camel-jmx: Execution default of goal org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.8.3:generate failed: Illegal pattern character 'g' -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10418) Deploy route with an error
[ https://issues.apache.org/jira/browse/CAMEL-10418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10418: - Description: When i create a route with an sintax error, it cannot be started but remains into camelcontext. An example to replicate it: 1. Deploy a route with an know id at runtime (using route definition). The route will be invalid (with an sintax error) 2. Redeploy correct route with same id Camel throw an example because i cannot deploy a route with same id!!! was: Sometime, when i create a route with an sintax error, it cannot be started but remains into camelcontext. An example to replicate it: 1. Deploy a route with an know id at runtime (using route definition). The route will be invalid (with an sintax error) 2. Redeploy correct route with same id Camel throw an example because i cannot deploy a route with same id!!! > Deploy route with an error > -- > > Key: CAMEL-10418 > URL: https://issues.apache.org/jira/browse/CAMEL-10418 > Project: Camel > Issue Type: Bug > Components: camel-core >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > > When i create a route with an sintax error, it cannot be started but remains > into camelcontext. > An example to replicate it: > 1. Deploy a route with an know id at runtime (using route definition). The > route will be invalid (with an sintax error) > 2. Redeploy correct route with same id > Camel throw an example because i cannot deploy a route with same id!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10418) Deploy route with an error
Fabrizio Spataro created CAMEL-10418: Summary: Deploy route with an error Key: CAMEL-10418 URL: https://issues.apache.org/jira/browse/CAMEL-10418 Project: Camel Issue Type: Bug Components: camel-core Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Priority: Minor Sometime, when i create a route with an sintax error, it cannot be started but remains into camelcontext. An example to replicate it: 1. Deploy a route with an know id at runtime (using route definition). The route will be invalid (with an sintax error) 2. Redeploy correct route with same id Camel throw an example because i cannot deploy a route with same id!!! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work stopped] (CAMEL-10327) New Apache drill component
[ https://issues.apache.org/jira/browse/CAMEL-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10327 stopped by Fabrizio Spataro. > New Apache drill component > -- > > Key: CAMEL-10327 > URL: https://issues.apache.org/jira/browse/CAMEL-10327 > Project: Camel > Issue Type: New Feature >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > > Hello, > the main idea is to create a producer to run queries on the apache drill > cluster. Can i start to develop this "simple" producer? > kings regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-10330) Complete support to API Docker
[ https://issues.apache.org/jira/browse/CAMEL-10330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro reassigned CAMEL-10330: Assignee: Fabrizio Spataro > Complete support to API Docker > -- > > Key: CAMEL-10330 > URL: https://issues.apache.org/jira/browse/CAMEL-10330 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Affects Versions: 2.18.0 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > Labels: docker > > Today, through the work of the CAMEL-10307 the docker-java library it has > been updated. > A open this jira to complete work by covering the services still not > available (for example "docker swarm") > Note: i will do it soon as possible -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10353) Enable Hazelcast Distributed Computing
Fabrizio Spataro created CAMEL-10353: Summary: Enable Hazelcast Distributed Computing Key: CAMEL-10353 URL: https://issues.apache.org/jira/browse/CAMEL-10353 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Fix For: 2.18.1 Add the ability to execute distributed task through Hazelcast Cluster http://docs.hazelcast.org/docs/3.7/manual/html-single/index.html#distributed-computing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529792#comment-15529792
]
Fabrizio Spataro commented on CAMEL-10349:
--
fixed. Can you approve my PR?
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529566#comment-15529566
]
Fabrizio Spataro commented on CAMEL-10349:
--
[~davsclaus] read this:
https://wiki.openjdk.java.net/display/Nashorn/Nashorn+jsr223+engine+notes
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-10349 started by Fabrizio Spataro.
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro reassigned CAMEL-10349:
Assignee: Fabrizio Spataro
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>Assignee: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528743#comment-15528743
]
Fabrizio Spataro commented on CAMEL-10349:
--
ok, I start to work immediately to reproduce it.
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-10349) javaScript setHeader conversion fault
[
https://issues.apache.org/jira/browse/CAMEL-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabrizio Spataro updated CAMEL-10349:
-
Description:
I may have found a bug derived from 2.18
Before 2.18, i can specified an header like:
{code}
[ {"firstField": "firstValue", "secondField":"secondValue"}
]
{code}
I pass it into a method inside my bean. It was cast to
ArrayList>
After 2.18 upgrade i had an error
'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
cannot be cast to java.util.List'
Can you help me? Is it a camel bug or an jdk8 issue?
was:
I may have found a bug derived from 2.18
Before 2.18, i can specified an header like:
[ {"firstField": "firstValue", "secondField":"secondValue"}
]
I pass it into a method inside my bean. It was cast to
ArrayList>
After 2.18 upgrade i had an error
'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
cannot be cast to java.util.List'
Can you help me? Is it a camel bug or an jdk8 issue?
> javaScript setHeader conversion fault
> -
>
> Key: CAMEL-10349
> URL: https://issues.apache.org/jira/browse/CAMEL-10349
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Fabrizio Spataro
>
> I may have found a bug derived from 2.18
> Before 2.18, i can specified an header like:
> {code}
>
> [ {"firstField": "firstValue", "secondField":"secondValue"}
> ]
>
> {code}
> I pass it into a method inside my bean. It was cast to
> ArrayList>
> After 2.18 upgrade i had an error
> 'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
> cannot be cast to java.util.List'
> Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-10349) javaScript setHeader conversion fault
Fabrizio Spataro created CAMEL-10349:
Summary: javaScript setHeader conversion fault
Key: CAMEL-10349
URL: https://issues.apache.org/jira/browse/CAMEL-10349
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.18.0
Reporter: Fabrizio Spataro
I may have found a bug derived from 2.18
Before 2.18, i can specified an header like:
[ {"firstField": "firstValue", "secondField":"secondValue"}
]
I pass it into a method inside my bean. It was cast to
ArrayList>
After 2.18 upgrade i had an error
'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
cannot be cast to java.util.List'
Can you help me? Is it a camel bug or an jdk8 issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (CAMEL-10327) New Apache drill component
[ https://issues.apache.org/jira/browse/CAMEL-10327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10327 started by Fabrizio Spataro. > New Apache drill component > -- > > Key: CAMEL-10327 > URL: https://issues.apache.org/jira/browse/CAMEL-10327 > Project: Camel > Issue Type: New Feature >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro >Priority: Minor > > Hello, > the main idea is to create a producer to run queries on the apache drill > cluster. Can i start to develop this "simple" producer? > kings regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (CAMEL-10331) Camel Docker Consumer
[ https://issues.apache.org/jira/browse/CAMEL-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-10331 started by Fabrizio Spataro. > Camel Docker Consumer > - > > Key: CAMEL-10331 > URL: https://issues.apache.org/jira/browse/CAMEL-10331 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Affects Versions: 2.18.0 >Reporter: Fabrizio Spataro >Assignee: Fabrizio Spataro > > Today, through the work of the CAMEL-10307 the docker-java library it has > been updated deleting camel consumer. > A open this jira to restore it. > Note: I am working to it soon as possible! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10336) Complete AMI features
Fabrizio Spataro created CAMEL-10336: Summary: Complete AMI features Key: CAMEL-10336 URL: https://issues.apache.org/jira/browse/CAMEL-10336 Project: Camel Issue Type: New Feature Affects Versions: 2.18.0 Reporter: Fabrizio Spataro Assignee: Fabrizio Spataro Fix For: 2.18.1 After resolution of CAMEL-10321 apache camel have a new component: "camel-asterisk". This initial release support a little subset of AMI API This issue to remember me to insert new functionalities. http://www.voip-info.org/wiki/view/Asterisk+manager+API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10330) Complete support to API Docker
[ https://issues.apache.org/jira/browse/CAMEL-10330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10330: - Description: Today, through the work of the CAMEL-10307 the docker-java library it has been updated. A open this jira to complete work by covering the services still not available (for example "docker swarm") Note: i will do it was: Today, through the work of the CAMEL-10307 the docker-java library it has been updated. A open this jira to complete work by covering the services still not available (for example "docker swarm") Note: I am working to it now! > Complete support to API Docker > -- > > Key: CAMEL-10330 > URL: https://issues.apache.org/jira/browse/CAMEL-10330 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Affects Versions: 2.18.0 >Reporter: Fabrizio Spataro > Labels: docker > > Today, through the work of the CAMEL-10307 the docker-java library it has > been updated. > A open this jira to complete work by covering the services still not > available (for example "docker swarm") > Note: i will do it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10331) Camel Docker Consumer
Fabrizio Spataro created CAMEL-10331: Summary: Camel Docker Consumer Key: CAMEL-10331 URL: https://issues.apache.org/jira/browse/CAMEL-10331 Project: Camel Issue Type: Improvement Components: camel-docker Affects Versions: 2.18.0 Reporter: Fabrizio Spataro Today, through the work of the CAMEL-10307 the docker-java library it has been updated deleting camel consumer. A open this jira to restore it. Note: I am working to it soon as possible! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10330) Complete support to API Docker
Fabrizio Spataro created CAMEL-10330: Summary: Complete support to API Docker Key: CAMEL-10330 URL: https://issues.apache.org/jira/browse/CAMEL-10330 Project: Camel Issue Type: Improvement Components: camel-docker Affects Versions: 2.18.0 Reporter: Fabrizio Spataro Today, through the work of the CAMEL-10307 the docker-java library it has been updated. A open this jira to complete work by covering the services still not available (for example "docker swarm") Note: I am working to it now! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503442#comment-15503442 ] Fabrizio Spataro commented on CAMEL-10307: -- I decided to start again, then the times are getting longer :-( > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15499081#comment-15499081 ] Fabrizio Spataro commented on CAMEL-10307: -- I resolve my problem, it is a simple powermock problem. Resolution is use @PowerMockIgnore annotation!!! i will test the component soon as possible and then send the PR Kings regards > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10327) New Apache drill component
Fabrizio Spataro created CAMEL-10327: Summary: New Apache drill component Key: CAMEL-10327 URL: https://issues.apache.org/jira/browse/CAMEL-10327 Project: Camel Issue Type: New Feature Reporter: Fabrizio Spataro Priority: Minor Hello, the main idea is to create a producer to run queries on the apache drill cluster. Can i start to develop this "simple" producer? kings regards -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10321) New Component camel-asterisk
[ https://issues.apache.org/jira/browse/CAMEL-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497563#comment-15497563 ] Fabrizio Spataro commented on CAMEL-10321: -- Hello, I just finished writing tests and documentation. I am ready for send PR but I would wait to get back in the office (monday morning) to test component with own asterisk server. Good Night Fabrizio > New Component camel-asterisk > > > Key: CAMEL-10321 > URL: https://issues.apache.org/jira/browse/CAMEL-10321 > Project: Camel > Issue Type: New Feature >Reporter: Fabrizio Spataro > > Hello, > i wrote a component to send and receive event from an asterisk VOIP server. > Can i send my PR? Is it compatible with apache camel code license? > King Regard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10321) New Component camel-asterisk
[ https://issues.apache.org/jira/browse/CAMEL-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493414#comment-15493414 ] Fabrizio Spataro commented on CAMEL-10321: -- Can i have a guide to write documentation (adoc file?) > New Component camel-asterisk > > > Key: CAMEL-10321 > URL: https://issues.apache.org/jira/browse/CAMEL-10321 > Project: Camel > Issue Type: New Feature >Reporter: Fabrizio Spataro > > Hello, > i wrote a component to send and receive event from an asterisk VOIP server. > Can i send my PR? Is it compatible with apache camel code license? > King Regard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10321) New Component camel-asterisk
[ https://issues.apache.org/jira/browse/CAMEL-10321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493234#comment-15493234 ] Fabrizio Spataro commented on CAMEL-10321: -- This is my component's summary : - lib: https://github.com/asterisk-java/asterisk-java (Apache License, Version 2.0.) - Producer - send action: 'QueueStatus', 'SipPeers', 'ExtensionState' - Consumer is an Asterisk Manager Interface (AMI) Event Listener is it ok? Naturally next step will be extend functionalities! > New Component camel-asterisk > > > Key: CAMEL-10321 > URL: https://issues.apache.org/jira/browse/CAMEL-10321 > Project: Camel > Issue Type: New Feature >Reporter: Fabrizio Spataro > > Hello, > i wrote a component to send and receive event from an asterisk VOIP server. > Can i send my PR? Is it compatible with apache camel code license? > King Regard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10321) New Component camel-asterisk
Fabrizio Spataro created CAMEL-10321: Summary: New Component camel-asterisk Key: CAMEL-10321 URL: https://issues.apache.org/jira/browse/CAMEL-10321 Project: Camel Issue Type: New Feature Reporter: Fabrizio Spataro Hello, i wrote a component to send and receive event from an asterisk VOIP server. Can i send my PR? Is it compatible with apache camel code license? King Regard -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10319) SNMP Producer
Fabrizio Spataro created CAMEL-10319: Summary: SNMP Producer Key: CAMEL-10319 URL: https://issues.apache.org/jira/browse/CAMEL-10319 Project: Camel Issue Type: New Feature Components: camel-snmp Reporter: Fabrizio Spataro Hello, I have already developed a SNMP Producer to send snmp packet. I am sending the PR Fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487587#comment-15487587 ] Fabrizio Spataro commented on CAMEL-10307: -- :-( http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-td5787511.html > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487209#comment-15487209 ] Fabrizio Spataro commented on CAMEL-10307: -- Hello everybody, my code is OK, i have connected succerfully with docker rest api 1.24 (docker 1.12.x) Now i am fixing test stay tuned! > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10314) cannot execute mvn install -Pfastinstall
[ https://issues.apache.org/jira/browse/CAMEL-10314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15486744#comment-15486744 ] Fabrizio Spataro commented on CAMEL-10314: -- Thanks andrea! > cannot execute mvn install -Pfastinstall > - > > Key: CAMEL-10314 > URL: https://issues.apache.org/jira/browse/CAMEL-10314 > Project: Camel > Issue Type: Task > Components: camel-jsch >Reporter: Fabrizio Spataro >Assignee: Andrea Cosentino > > Hello, i am using master source. > When i execute *mvn clean install -Pfastinstall* i have an error > > [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch > --- > [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused > Import-Package instructions: [org.springframework.ws.*, > org.springframework.xml.*, org.springframework.*, > org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, > org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, > org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, > org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, > net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, > org.apache.lucene.*, org.apache.solr.*] > [INFO] > [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components > (validate) @ camel-jsch --- > [WARNING] The component: scp has validation errors > [WARNING] Missing endpoint documentation for the following options: > host > port > directoryName > disconnect > disconnectOnBatchComplete > fileName > flatten > allowNullBody > connectTimeout > soTimeout > timeout > password > username > > king regards > fabryprog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10314) cannot execute mvn install -Pfastinstall
Fabrizio Spataro created CAMEL-10314: Summary: cannot execute mvn install -Pfastinstall Key: CAMEL-10314 URL: https://issues.apache.org/jira/browse/CAMEL-10314 Project: Camel Issue Type: Task Components: camel-jsch Reporter: Fabrizio Spataro Hello, i am using master source. When i execute *mvn clean install -Pfastinstall* i have an error [INFO] --- maven-bundle-plugin:3.2.0:manifest (bundle-manifest) @ camel-jsch --- [WARNING] Manifest org.apache.camel:camel-jsch:jar:2.18.0-SNAPSHOT : Unused Import-Package instructions: [org.springframework.ws.*, org.springframework.xml.*, org.springframework.*, org.apache.commons.logging.*, org.apache.cxf.*, org.apache.qpid.*, org.apache.abdera.*, org.apache.commons.httpclient.*, org.apache.velocity.*, org.apache.xmlbeans.*, org.eclipse.jetty.*, com.thoughtworks.xstream.*, org.antlr.stringtemplate.*, org.ccil.cowan.tagsoup.*, org.mortbay.cometd.*, net.sf.flatpack.*, net.sf.saxon.*, freemarker.*, javax.persistence.*, org.apache.lucene.*, org.apache.solr.*] [INFO] [INFO] --- camel-package-maven-plugin:2.18.0-SNAPSHOT:validate-components (validate) @ camel-jsch --- [WARNING] The component: scp has validation errors [WARNING] Missing endpoint documentation for the following options: host port directoryName disconnect disconnectOnBatchComplete fileName flatten allowNullBody connectTimeout soTimeout timeout password username king regards fabryprog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484502#comment-15484502 ] Fabrizio Spataro commented on CAMEL-10307: -- Hello, i am fixing tests with new version and send my PR For this PR i have deprecate all docker consumer's features > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483442#comment-15483442 ] Fabrizio Spataro commented on CAMEL-10307: -- :-) thanks claus, i am working to this issue. Later I'll let you know what to keep and what to take off > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483223#comment-15483223 ] Fabrizio Spataro commented on CAMEL-10307: -- Exactly andrea, we wait Claus also because the amount of code written is very high. > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483207#comment-15483207 ] Fabrizio Spataro commented on CAMEL-10307: -- Ok Andrea, It might be an idea to do over again the implementation with the basic functionality and deprecate the features not yet updated. Today the docker-java version is not compatible with the excellent latest release (1.12), I think it's important to also update the deprecating features. Claus, what do you think? > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10307) Upgrade docker java version
[ https://issues.apache.org/jira/browse/CAMEL-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482350#comment-15482350 ] Fabrizio Spataro commented on CAMEL-10307: -- Hello, i tried to update the component but much code is very different (for example, the event management). Can i send PR equally? > Upgrade docker java version > --- > > Key: CAMEL-10307 > URL: https://issues.apache.org/jira/browse/CAMEL-10307 > Project: Camel > Issue Type: Improvement > Components: camel-docker >Reporter: Fabrizio Spataro > > Hello, > Today the component use a very old docker-java lib 1.0.4, current docker-java > version is 3.0.5 > Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10307) Upgrade docker java version
Fabrizio Spataro created CAMEL-10307: Summary: Upgrade docker java version Key: CAMEL-10307 URL: https://issues.apache.org/jira/browse/CAMEL-10307 Project: Camel Issue Type: Improvement Components: camel-docker Reporter: Fabrizio Spataro Hello, Today the component use a very old docker-java lib 1.0.4, current docker-java version is 3.0.5 Could be nice to upgrade all component code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
[
https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481862#comment-15481862
]
Fabrizio Spataro commented on CAMEL-10306:
--
Hello everybody, now all tests are ok
It isn't a wrong lock features but only newHazelcastInstance() that with new
version gone wrong.
I had change this code with newHazelcastInstance(new Config("A NAME")) and all
tests are ok!
Can you merge my PR? (https://github.com/apache/camel/pull/1166)
king regards
FabryProg
LOG OUTPUT
Results :
Flaked tests:
org.apache.camel.processor.aggregate.hazelcast.HazelcastAggregationRepositoryOperationsTest.checkOptimisticPersistentRemove(org.apache.camel.processor.aggregate.hazelcast.HazelcastAggregationRepositoryOperationsTest)
Run 1:
HazelcastAggregationRepositoryOperationsTest.checkOptimisticPersistentRemove:149
▒ OptimisticLocking
Run 2: PASS
Tests run: 186, Failures: 0, Errors: 0, Skipped: 0, Flakes: 1
[
> Upgrade from 3.6.5 to 3.7.1
> ---
>
> Key: CAMEL-10306
> URL: https://issues.apache.org/jira/browse/CAMEL-10306
> Project: Camel
> Issue Type: Task
> Components: camel-hazelcast
>Reporter: Fabrizio Spataro
>Priority: Minor
>
> Upgrade hazelcast version.
> The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized
> In-Memory Data Grid
> (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
[ https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481255#comment-15481255 ] Fabrizio Spataro commented on CAMEL-10306: -- Exactly! I am sending PR... > Upgrade from 3.6.5 to 3.7.1 > --- > > Key: CAMEL-10306 > URL: https://issues.apache.org/jira/browse/CAMEL-10306 > Project: Camel > Issue Type: Task > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Upgrade hazelcast version. > The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized > In-Memory Data Grid > (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
[ https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15480192#comment-15480192 ] Fabrizio Spataro commented on CAMEL-10306: -- The spring test using Bean reference is broken with this upgrade. I still can not understand ... > Upgrade from 3.6.5 to 3.7.1 > --- > > Key: CAMEL-10306 > URL: https://issues.apache.org/jira/browse/CAMEL-10306 > Project: Camel > Issue Type: Task > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Upgrade hazelcast version. > The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized > In-Memory Data Grid > (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
[ https://issues.apache.org/jira/browse/CAMEL-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15479986#comment-15479986 ] Fabrizio Spataro commented on CAMEL-10306: -- I am working to this jira!! I have some problem with a springtest... soon as possible send PR Kings regards > Upgrade from 3.6.5 to 3.7.1 > --- > > Key: CAMEL-10306 > URL: https://issues.apache.org/jira/browse/CAMEL-10306 > Project: Camel > Issue Type: Task > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Upgrade hazelcast version. > The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized > In-Memory Data Grid > (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-10306) Upgrade from 3.6.5 to 3.7.1
Fabrizio Spataro created CAMEL-10306: Summary: Upgrade from 3.6.5 to 3.7.1 Key: CAMEL-10306 URL: https://issues.apache.org/jira/browse/CAMEL-10306 Project: Camel Issue Type: Task Components: camel-hazelcast Reporter: Fabrizio Spataro Priority: Minor Upgrade hazelcast version. The 3.7.x version is Cloud-Enabled and 30% Faster and Fully Modularized In-Memory Data Grid (http://insidebigdata.com/2016/09/02/hazelcast-releases-3-7-cloud-enabled-30-faster-and-the-first-fully-modularized-in-memory-data-grid) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Comment: was deleted (was: Hello, i create PR https://github.com/apache/camel/pull/1165) > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, this feature is > already present into code using headers: CamelHazelcastObjectTtlValue and > CamelHazelcastObjectTtlUnit > unfortunately it is not present in documentation!!! > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15479860#comment-15479860 ] Fabrizio Spataro commented on CAMEL-10295: -- Hello, i create PR https://github.com/apache/camel/pull/1165 > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, this feature is > already present into code using headers: CamelHazelcastObjectTtlValue and > CamelHazelcastObjectTtlUnit > unfortunately it is not present in documentation!!! > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Description: Hello, Into some hazelcast distribuited object (for instance hashmap.put (...) ) can be set element's eviction time. Eviction time is very useful into big cluster structure, this feature is already present into code using headers: CamelHazelcastObjectTtlValue and CamelHazelcastObjectTtlUnit unfortunately it is not present in documentation!!! See you soon. fabrizio was: Hello, Into some hazelcast distribuited object (for instance hashmap.put (...) ) can be set element's eviction time. Eviction time is very useful into big cluster structure, today using camel components i cannot set it. this feature is already present into code using headers: CamelHazelcastObjectTtlValue and CamelHazelcastObjectTtlUnit See you soon. fabrizio > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, this feature is > already present into code using headers: CamelHazelcastObjectTtlValue and > CamelHazelcastObjectTtlUnit > unfortunately it is not present in documentation!!! > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Summary: hazelcast map data store documentation (was: Eviction policy into hazelcast operation) > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, today using camel > components i cannot set it. > I open this jira to improve camel-hazelcast component but i would be happy to > fix it using a git-hub push request. > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-10295) hazelcast map data store documentation
[ https://issues.apache.org/jira/browse/CAMEL-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabrizio Spataro updated CAMEL-10295: - Description: Hello, Into some hazelcast distribuited object (for instance hashmap.put (...) ) can be set element's eviction time. Eviction time is very useful into big cluster structure, today using camel components i cannot set it. this feature is already present into code using headers: CamelHazelcastObjectTtlValue and CamelHazelcastObjectTtlUnit See you soon. fabrizio was: Hello, Into some hazelcast distribuited object (for instance hashmap.put (...) ) can be set element's eviction time. Eviction time is very useful into big cluster structure, today using camel components i cannot set it. I open this jira to improve camel-hazelcast component but i would be happy to fix it using a git-hub push request. See you soon. fabrizio > hazelcast map data store documentation > -- > > Key: CAMEL-10295 > URL: https://issues.apache.org/jira/browse/CAMEL-10295 > Project: Camel > Issue Type: New Feature > Components: camel-hazelcast >Reporter: Fabrizio Spataro >Priority: Minor > > Hello, > Into some hazelcast distribuited object (for instance hashmap.put (...) ) can > be set element's eviction time. > Eviction time is very useful into big cluster structure, today using camel > components i cannot set it. > this feature is already present into code using headers: > CamelHazelcastObjectTtlValue and CamelHazelcastObjectTtlUnit > See you soon. > fabrizio -- This message was sent by Atlassian JIRA (v6.3.4#6332)
