[jira] [Commented] (CAMEL-14495) OPC UA Client samplingInterval parameter seems not take any effect
[
https://issues.apache.org/jira/browse/CAMEL-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039604#comment-17039604
]
Hobbert commented on CAMEL-14495:
-
I think I have discovered the point
Exploring the Milo library, I found a *createsubscription* parameter that is
set to 1000 ms of requesting subscription interval
{quote}// create a subscription @ 1000ms
UaSubscription subscription =
client.getSubscriptionManager().*createSubscription(1000.0)*.get();{quote}
[https://github.com/eclipse/milo/blob/master/milo-examples/client-examples/src/main/java/org/eclipse/milo/examples/client/SubscriptionExample.java]
Looking for the parameter over the milo library, it confirms the idea:
{quote}* @param *requestedPublishingInterval* the requested publishing interval
of the subscription.
* @return a \{@link CompletableFuture} containing the \{@link
UaSubscription}.
*/
CompletableFuture createSubscription(double
*_requestedPublishingInterval_*);{quote}
[https://github.com/eclipse/milo/blob/5ed4edad57be181b3b0d08fb124e252cf2decc56/opc-ua-sdk/sdk-client/src/main/java/org/eclipse/milo/opcua/sdk/client/api/subscriptions/UaSubscriptionManager.java]
And when I looked at this parameter in the Camel, seems that its really fixed
at 1000 ms
{quote}final UaSubscription manager =
client.getSubscriptionManager().*createSubscription(1_000.0)*.get();{quote}
[https://github.com/apache/camel/blob/b78d16f720b7ee54b16bde820d9439b56e8fea7d/components/camel-milo/src/main/java/org/apache/camel/component/milo/client/internal/SubscriptionManager.java]
I believe that this parameter needs to be included at the Camel OPC UA Client
configuration!!
Anyone knows how to do that??
Thanks
> OPC UA Client samplingInterval parameter seems not take any effect
> --
>
> Key: CAMEL-14495
> URL: https://issues.apache.org/jira/browse/CAMEL-14495
> Project: Camel
> Issue Type: Bug
> Components: camel-milo
>Affects Versions: 2.25.0
>Reporter: Hobbert
>Priority: Minor
>
> When I set the *samplingInterval* parameter on a Milo OPC UA Client route,
> the interval not changes on the real OPC application! Remains 1000 mili
> seconds even after configuring!! Can anyone confirm that??
> Heres my route
> http://camel.apache.org/schema/spring; >
>
> uri="milo-client:tcp://192.168.0.2:4840?samplingInterval=50=RAW(ns=4;i=12)"/>
>
> ${in.body}
>
>
>
> Thanks
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14579) Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039506#comment-17039506
]
Pascal Schumacher commented on CAMEL-14579:
---
Thank you very much for looking into this. It is much appreciated.
I retested with your fix for "CAMEL-14586 camel-core - Disable cache on some
EIPs seems to not be working".
For:
{code:java}
.recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
{code}
The MailEndpoint leak is fixed, but the RedeliveryPolicy leak remains (see the
attached CamelMail_RecipientList_MemoryLeak_3.1.0-SNAPSHOT-2020-02-18.16.PNG
screenshot).
For dynamic to the behavior is the same as before, but I guess that is as
expected.
By the way: I was able to work around this issue by implementing a custom
JavaMailSender.
> Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
>
>
> Key: CAMEL-14579
> URL: https://issues.apache.org/jira/browse/CAMEL-14579
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.0.1
>Reporter: Pascal Schumacher
>Priority: Minor
> Attachments: CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG,
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG,
> CamelMail_RecipientList_MemoryLeak_3.1.0-SNAPSHOT-2020-02-18.16.PNG
>
>
> In Camel 3.0.1 there seems to be a memory leak when you use camel-mail to
> send mails with a recipient list (see attached screenshot
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG).
> Code to reproduce:
> {code:java}
> public class SendMailDynamicToMemoryLeakTest extends CamelTestSupport {
> @Override
> protected RouteBuilder createRouteBuilder() {
> return new RouteBuilder() {
> public void configure() {
> from("scheduler:start?delay=1")
> .setBody(constant("Hello"))
> .setHeader("smtpFrom", method(UUID.class, "randomUUID"))
>
> .recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
> //
> .toD("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}");
> }
> };
> }
> @Test
> public void test() throws Exception {
> Thread.sleep(100_000_000L);
> }
> }
> {code}
> {code:xml}
>
> com.bitmechanic
> dumbster
> 1.9.0.2
>
> {code}
> {code:java}
> public class TestMailServer {
> public static void main(String[] args) throws Exception {
> ServerOptions serverOptions = new ServerOptions();
> serverOptions.port = 1234;
> SmtpServerFactory.startServer(serverOptions);
> }
> }
> {code}
> To make reproduction easier I pushed everything to
> https://github.com/PascalSchumacher/CamelSendMailMemoryLeak
> Run the TestMailServer class, then run SendMailDynamicToMemoryLeakTest.
> Using Camel 3.1.0-SNAPSHOT to run the test shows the same behavior.
> Using Camel 2.24.2 there is no memory leak.
> ---
> The original code is using toD (see commented out code in the test case
> above) instead of a recipient list. For dynamic to there seems to be a slower
> memory leak in Camel 3.0.1 (not completely sure, a lot of objects get garbage
> collected, but overall object count seems to slowly increase.)
> Using Camel 2.24.2 there is no memory leak.
> Using Camel 3.1.0-SNAPSHOT with dynamic to there seems to be a memory leak,
> see the attached screenshot CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG.
> I am not sure if the recipientList/toD behavior is limited to camel-mail or
> if it would occur for other components too. I could not replicate the
> behavior with camel-http, but this component uses optimized dynamic to and
> this may prevent the occurrence of a memory leak.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14579) Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated CAMEL-14579:
--
Attachment:
CamelMail_RecipientList_MemoryLeak_3.1.0-SNAPSHOT-2020-02-18.16.PNG
> Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
>
>
> Key: CAMEL-14579
> URL: https://issues.apache.org/jira/browse/CAMEL-14579
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.0.1
>Reporter: Pascal Schumacher
>Priority: Minor
> Attachments: CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG,
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG,
> CamelMail_RecipientList_MemoryLeak_3.1.0-SNAPSHOT-2020-02-18.16.PNG
>
>
> In Camel 3.0.1 there seems to be a memory leak when you use camel-mail to
> send mails with a recipient list (see attached screenshot
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG).
> Code to reproduce:
> {code:java}
> public class SendMailDynamicToMemoryLeakTest extends CamelTestSupport {
> @Override
> protected RouteBuilder createRouteBuilder() {
> return new RouteBuilder() {
> public void configure() {
> from("scheduler:start?delay=1")
> .setBody(constant("Hello"))
> .setHeader("smtpFrom", method(UUID.class, "randomUUID"))
>
> .recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
> //
> .toD("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}");
> }
> };
> }
> @Test
> public void test() throws Exception {
> Thread.sleep(100_000_000L);
> }
> }
> {code}
> {code:xml}
>
> com.bitmechanic
> dumbster
> 1.9.0.2
>
> {code}
> {code:java}
> public class TestMailServer {
> public static void main(String[] args) throws Exception {
> ServerOptions serverOptions = new ServerOptions();
> serverOptions.port = 1234;
> SmtpServerFactory.startServer(serverOptions);
> }
> }
> {code}
> To make reproduction easier I pushed everything to
> https://github.com/PascalSchumacher/CamelSendMailMemoryLeak
> Run the TestMailServer class, then run SendMailDynamicToMemoryLeakTest.
> Using Camel 3.1.0-SNAPSHOT to run the test shows the same behavior.
> Using Camel 2.24.2 there is no memory leak.
> ---
> The original code is using toD (see commented out code in the test case
> above) instead of a recipient list. For dynamic to there seems to be a slower
> memory leak in Camel 3.0.1 (not completely sure, a lot of objects get garbage
> collected, but overall object count seems to slowly increase.)
> Using Camel 2.24.2 there is no memory leak.
> Using Camel 3.1.0-SNAPSHOT with dynamic to there seems to be a memory leak,
> see the attached screenshot CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG.
> I am not sure if the recipientList/toD behavior is limited to camel-mail or
> if it would occur for other components too. I could not replicate the
> behavior with camel-http, but this component uses optimized dynamic to and
> this may prevent the occurrence of a memory leak.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14590) Camel-Pulsar consumer calls unsubscribe on doStop/doSuspend, potentially deleting subscription
Connor McAuliffe created CAMEL-14590: Summary: Camel-Pulsar consumer calls unsubscribe on doStop/doSuspend, potentially deleting subscription Key: CAMEL-14590 URL: https://issues.apache.org/jira/browse/CAMEL-14590 Project: Camel Issue Type: Bug Components: camel-pulsar Reporter: Connor McAuliffe In the PulsarUtils [stopConsumers method|https://github.com/apache/camel/blob/master/components/camel-pulsar/src/main/java/org/apache/camel/component/pulsar/utils/PulsarUtils.java] all the consumers call unsubscribe(). This causes the subscription to be deleted if this call comes from the last consumer. I do not know if this is intentional behavior but it seems to be dangerous (and has caused some issues for us without realizing it). If this is intentional, can we make it configurable to avoid doing this? Or if it is not intentional can we just remove the call entirely? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14588) MailConsumer: Move mail after processing
[ https://issues.apache.org/jira/browse/CAMEL-14588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14588: Affects Version/s: (was: Future) > MailConsumer: Move mail after processing > > > Key: CAMEL-14588 > URL: https://issues.apache.org/jira/browse/CAMEL-14588 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Reporter: Manuel Shenavai >Priority: Major > Fix For: 3.2.0 > > Attachments: 0001-New-property-MoveTo.patch > > Time Spent: 10m > Remaining Estimate: 0h > > After processing a mail with the mailConsumer, I like to mark the message as > read and move it to another folder. > > I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14588) MailConsumer: Move mail after processing
[ https://issues.apache.org/jira/browse/CAMEL-14588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14588: Fix Version/s: (was: Future) 3.2.0 > MailConsumer: Move mail after processing > > > Key: CAMEL-14588 > URL: https://issues.apache.org/jira/browse/CAMEL-14588 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Affects Versions: Future >Reporter: Manuel Shenavai >Priority: Major > Fix For: 3.2.0 > > Attachments: 0001-New-property-MoveTo.patch > > Time Spent: 10m > Remaining Estimate: 0h > > After processing a mail with the mailConsumer, I like to mark the message as > read and move it to another folder. > > I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14589) camel-cxf - Service beans can only be set via context
[ https://issues.apache.org/jira/browse/CAMEL-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14589: Priority: Minor (was: Major) > camel-cxf - Service beans can only be set via context > - > > Key: CAMEL-14589 > URL: https://issues.apache.org/jira/browse/CAMEL-14589 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 3.0.0, 3.0.1 >Reporter: Jens Kleine-Herzbruch >Priority: Minor > Attachments: cxf-service-beans.diff > > > Since version 3.x it is no longer possible to set service beans directly. > They can only be resolved from the context instead. This was possible in 2.x. > The attached patch readds this configuration path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14589) camel-cxf - Service beans can only be set via context
[ https://issues.apache.org/jira/browse/CAMEL-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14589: Issue Type: Improvement (was: Bug) > camel-cxf - Service beans can only be set via context > - > > Key: CAMEL-14589 > URL: https://issues.apache.org/jira/browse/CAMEL-14589 > Project: Camel > Issue Type: Improvement > Components: camel-cxfrs >Affects Versions: 3.0.0, 3.0.1 >Reporter: Jens Kleine-Herzbruch >Priority: Major > Attachments: cxf-service-beans.diff > > > Since version 3.x it is no longer possible to set service beans directly. > They can only be resolved from the context instead. This was possible in 2.x. > The attached patch readds this configuration path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14589) camel-c8f - Service beans can only be set via context
[ https://issues.apache.org/jira/browse/CAMEL-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039206#comment-17039206 ] Jens Kleine-Herzbruch commented on CAMEL-14589: --- I'm afraid I'm not allowed to do that. > camel-cxf - Service beans can only be set via context > - > > Key: CAMEL-14589 > URL: https://issues.apache.org/jira/browse/CAMEL-14589 > Project: Camel > Issue Type: Bug > Components: camel-cxfrs >Affects Versions: 3.0.0, 3.0.1 >Reporter: Jens Kleine-Herzbruch >Priority: Major > Attachments: cxf-service-beans.diff > > > Since version 3.x it is no longer possible to set service beans directly. > They can only be resolved from the context instead. This was possible in 2.x. > The attached patch readds this configuration path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14588) MailConsumer: Move mail after processing
[ https://issues.apache.org/jira/browse/CAMEL-14588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039171#comment-17039171 ] Manuel Shenavai commented on CAMEL-14588: - Hi [~dmvolod], thanks for your message. I created a pull request: [https://github.com/apache/camel/pull/3587] Regarding the change: I adapted this from the copyTo setting which seems to allow overwrite the configuration via header. I could not verify how this configuration via header is working. This should be checked further I think. Thank you & Best regards, Manuel > MailConsumer: Move mail after processing > > > Key: CAMEL-14588 > URL: https://issues.apache.org/jira/browse/CAMEL-14588 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Affects Versions: Future >Reporter: Manuel Shenavai >Priority: Major > Fix For: Future > > Attachments: 0001-New-property-MoveTo.patch > > Time Spent: 10m > Remaining Estimate: 0h > > After processing a mail with the mailConsumer, I like to mark the message as > read and move it to another folder. > > I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14588) MailConsumer: Move mail after processing
[ https://issues.apache.org/jira/browse/CAMEL-14588?focusedWorklogId=388858=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-388858 ] ASF GitHub Bot logged work on CAMEL-14588: -- Author: ASF GitHub Bot Created on: 18/Feb/20 15:27 Start Date: 18/Feb/20 15:27 Worklog Time Spent: 10m Work Description: mash-sap commented on pull request #3587: CAMEL-14588: New setting to allow mails to be moved after processing URL: https://github.com/apache/camel/pull/3587 New setting to allow mails to be moved after processing This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 388858) Remaining Estimate: 0h Time Spent: 10m > MailConsumer: Move mail after processing > > > Key: CAMEL-14588 > URL: https://issues.apache.org/jira/browse/CAMEL-14588 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Affects Versions: Future >Reporter: Manuel Shenavai >Priority: Major > Fix For: Future > > Attachments: 0001-New-property-MoveTo.patch > > Time Spent: 10m > Remaining Estimate: 0h > > After processing a mail with the mailConsumer, I like to mark the message as > read and move it to another folder. > > I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14589) camel-cxf - Service beans can only be set via context
[ https://issues.apache.org/jira/browse/CAMEL-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039142#comment-17039142 ] Dmitry Volodin commented on CAMEL-14589: [~jen...@gmx.net] , could you please to raise PR against GitHub if possible. > camel-cxf - Service beans can only be set via context > - > > Key: CAMEL-14589 > URL: https://issues.apache.org/jira/browse/CAMEL-14589 > Project: Camel > Issue Type: Bug > Components: camel-cxfrs >Affects Versions: 3.0.0, 3.0.1 >Reporter: Jens Kleine-Herzbruch >Priority: Major > Attachments: cxf-service-beans.diff > > > Since version 3.x it is no longer possible to set service beans directly. > They can only be resolved from the context instead. This was possible in 2.x. > The attached patch readds this configuration path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14588) MailConsumer: Move mail after processing
[ https://issues.apache.org/jira/browse/CAMEL-14588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039141#comment-17039141 ] Dmitry Volodin commented on CAMEL-14588: [~mash-sap], could you please to raise PR against GitHub if possible. > MailConsumer: Move mail after processing > > > Key: CAMEL-14588 > URL: https://issues.apache.org/jira/browse/CAMEL-14588 > Project: Camel > Issue Type: New Feature > Components: camel-mail >Affects Versions: Future >Reporter: Manuel Shenavai >Priority: Major > Fix For: Future > > Attachments: 0001-New-property-MoveTo.patch > > > After processing a mail with the mailConsumer, I like to mark the message as > read and move it to another folder. > > I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14589) camel-cxf - Service beans can only be set via context
Jens Kleine-Herzbruch created CAMEL-14589: - Summary: camel-cxf - Service beans can only be set via context Key: CAMEL-14589 URL: https://issues.apache.org/jira/browse/CAMEL-14589 Project: Camel Issue Type: Bug Components: camel-cxfrs Affects Versions: 3.0.1, 3.0.0 Reporter: Jens Kleine-Herzbruch Attachments: cxf-service-beans.diff Since version 3.x it is no longer possible to set service beans directly. They can only be resolved from the context instead. This was possible in 2.x. The attached patch readds this configuration path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14587) AWS Components To Support useIAMCredentials
[ https://issues.apache.org/jira/browse/CAMEL-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039119#comment-17039119 ] Bojan Zekanovic commented on CAMEL-14587: - [~acosentino] thank you for taking this into consideration. > AWS Components To Support useIAMCredentials > > > Key: CAMEL-14587 > URL: https://issues.apache.org/jira/browse/CAMEL-14587 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Affects Versions: 3.0.0 >Reporter: Bojan Zekanovic >Assignee: Andrea Cosentino >Priority: Major > Fix For: Future > > > It would be great if we could use useIAMCredentials with other AWS Camel > Components like you guys have it available with S3 Component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14588) MailConsumer: Move mail after processing
Manuel Shenavai created CAMEL-14588: --- Summary: MailConsumer: Move mail after processing Key: CAMEL-14588 URL: https://issues.apache.org/jira/browse/CAMEL-14588 Project: Camel Issue Type: New Feature Components: camel-mail Affects Versions: Future Reporter: Manuel Shenavai Fix For: Future Attachments: 0001-New-property-MoveTo.patch After processing a mail with the mailConsumer, I like to mark the message as read and move it to another folder. I attached a proposal how to add this feature. Kindly have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14587) AWS Components To Support useIAMCredentials
[ https://issues.apache.org/jira/browse/CAMEL-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039103#comment-17039103 ] Andrea Cosentino commented on CAMEL-14587: -- I think we can add this to the Aws2 components. > AWS Components To Support useIAMCredentials > > > Key: CAMEL-14587 > URL: https://issues.apache.org/jira/browse/CAMEL-14587 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Affects Versions: 3.0.0 >Reporter: Bojan Zekanovic >Priority: Major > Fix For: Future > > > It would be great if we could use useIAMCredentials with other AWS Camel > Components like you guys have it available with S3 Component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14587) AWS Components To Support useIAMCredentials
[ https://issues.apache.org/jira/browse/CAMEL-14587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-14587: Assignee: Andrea Cosentino > AWS Components To Support useIAMCredentials > > > Key: CAMEL-14587 > URL: https://issues.apache.org/jira/browse/CAMEL-14587 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Affects Versions: 3.0.0 >Reporter: Bojan Zekanovic >Assignee: Andrea Cosentino >Priority: Major > Fix For: Future > > > It would be great if we could use useIAMCredentials with other AWS Camel > Components like you guys have it available with S3 Component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14587) AWS Components To Support useIAMCredentials
Bojan Zekanovic created CAMEL-14587: --- Summary: AWS Components To Support useIAMCredentials Key: CAMEL-14587 URL: https://issues.apache.org/jira/browse/CAMEL-14587 Project: Camel Issue Type: New Feature Components: camel-aws Affects Versions: 3.0.0 Reporter: Bojan Zekanovic Fix For: Future It would be great if we could use useIAMCredentials with other AWS Camel Components like you guys have it available with S3 Component. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14542) camel-core - Optimize simple language
[ https://issues.apache.org/jira/browse/CAMEL-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039083#comment-17039083 ] Claus Ibsen commented on CAMEL-14542: - Did a little optimizations but there are likely more potential > camel-core - Optimize simple language > - > > Key: CAMEL-14542 > URL: https://issues.apache.org/jira/browse/CAMEL-14542 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > There are potentially some improvements we can for simple language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039076#comment-17039076 ] Andrea Cosentino commented on CAMEL-14532: -- Yes, it's related to that. I'm running a full build, probably you did not. In the dataformat in xml, the javatype can be whatever you want but the concrete type in the class must be a String. If you declare it as int or boolean, it will break the xml-io module with unsupported operation exception. Dataformats are really tricky, so once you add an option, I always suggest to run a full build. I usually suggest to run a full build anyway, > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039069#comment-17039069 ] Colm O hEigeartaigh commented on CAMEL-14532: - I see there are some sourcecheck errors - I'll fix them. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039067#comment-17039067 ] Colm O hEigeartaigh commented on CAMEL-14532: - Are you sure it's related to my merges? I don't see anything obvious that could have caused it > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039060#comment-17039060 ] Andrea Cosentino commented on CAMEL-14532: -- xml-io module is now failing. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039056#comment-17039056 ] Colm O hEigeartaigh commented on CAMEL-14532: - [~davsclaus] Thanks, that's done. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039042#comment-17039042 ] Colm O hEigeartaigh commented on CAMEL-14532: - [~acosentino] - It's merged to master now. Just a question though - I added two configuration options to [https://github.com/apache/camel/blob/ffda93ae1dd43d18a88b498c4c073f8f0f58b1be/components/camel-snakeyaml/src/main/java/org/apache/camel/component/snakeyaml/SnakeYAMLDataFormat.java] However I don't see them added to the adoc after I run mvn clean install. What am I missing here? > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039045#comment-17039045 ] Claus Ibsen commented on CAMEL-14532: - For data formats you need to add them to the model in core/camel-core-engine in YAMLDataFormat > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039043#comment-17039043 ] Andrea Cosentino commented on CAMEL-14532: -- Probably you need to rebuild the whole Camel project. There were big changes. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038997#comment-17038997 ] Andrea Cosentino commented on CAMEL-14532: -- There some troubles with camel-restdsl-openapi, so you should be ok. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038995#comment-17038995 ] Colm O hEigeartaigh commented on CAMEL-14532: - I am literally about to merge it - is there still time? > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038994#comment-17038994 ] Andrea Cosentino commented on CAMEL-14532: -- The release cut for 3.1.0 is under work, so I don't think this will go in 3.1.0 > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Fix Version/s: 3.1.0 > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Description: There is an issue with this library that can cause endless recursion. A PR has been submitted upstream, however we can work around it in Camel until (if) it is applied. (was: There is an issue with this library that can cause endless recursion. The snakeyaml project will not fix it and so the Camel team has decided to deprecate this module and remove it from 3.1 onwards.) > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Summary: Fix issues with camel-snakeyaml (was: Deprecate camel-snakeyaml ) > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. > The snakeyaml project will not fix it and so the Camel team has decided to > deprecate this module and remove it from 3.1 onwards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14532) Deprecate camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CAMEL-14532: --- Assignee: Colm O hEigeartaigh > Deprecate camel-snakeyaml > -- > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. > The snakeyaml project will not fix it and so the Camel team has decided to > deprecate this module and remove it from 3.1 onwards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14579) Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038963#comment-17038963
]
Claus Ibsen commented on CAMEL-14579:
-
Okay the cacheSize(-1) has been fixed on master branch. You are welcome to try
this again with a new fresh build.
> Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
>
>
> Key: CAMEL-14579
> URL: https://issues.apache.org/jira/browse/CAMEL-14579
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.0.1
>Reporter: Pascal Schumacher
>Priority: Minor
> Attachments: CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG,
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG
>
>
> In Camel 3.0.1 there seems to be a memory leak when you use camel-mail to
> send mails with a recipient list (see attached screenshot
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG).
> Code to reproduce:
> {code:java}
> public class SendMailDynamicToMemoryLeakTest extends CamelTestSupport {
> @Override
> protected RouteBuilder createRouteBuilder() {
> return new RouteBuilder() {
> public void configure() {
> from("scheduler:start?delay=1")
> .setBody(constant("Hello"))
> .setHeader("smtpFrom", method(UUID.class, "randomUUID"))
>
> .recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
> //
> .toD("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}");
> }
> };
> }
> @Test
> public void test() throws Exception {
> Thread.sleep(100_000_000L);
> }
> }
> {code}
> {code:xml}
>
> com.bitmechanic
> dumbster
> 1.9.0.2
>
> {code}
> {code:java}
> public class TestMailServer {
> public static void main(String[] args) throws Exception {
> ServerOptions serverOptions = new ServerOptions();
> serverOptions.port = 1234;
> SmtpServerFactory.startServer(serverOptions);
> }
> }
> {code}
> To make reproduction easier I pushed everything to
> https://github.com/PascalSchumacher/CamelSendMailMemoryLeak
> Run the TestMailServer class, then run SendMailDynamicToMemoryLeakTest.
> Using Camel 3.1.0-SNAPSHOT to run the test shows the same behavior.
> Using Camel 2.24.2 there is no memory leak.
> ---
> The original code is using toD (see commented out code in the test case
> above) instead of a recipient list. For dynamic to there seems to be a slower
> memory leak in Camel 3.0.1 (not completely sure, a lot of objects get garbage
> collected, but overall object count seems to slowly increase.)
> Using Camel 2.24.2 there is no memory leak.
> Using Camel 3.1.0-SNAPSHOT with dynamic to there seems to be a memory leak,
> see the attached screenshot CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG.
> I am not sure if the recipientList/toD behavior is limited to camel-mail or
> if it would occur for other components too. I could not replicate the
> behavior with camel-http, but this component uses optimized dynamic to and
> this may prevent the occurrence of a memory leak.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14586) camel-core - Disable cache on some EIPs seems to not be working correlction
[ https://issues.apache.org/jira/browse/CAMEL-14586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14586. - Resolution: Fixed > cam%l-core - Disable cache on some EIPs seems to not be working correlction > --- > > Key: CAMEL-14586 > URL: https://issues.apache.org/jira/browse/CAMEL-14586 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.1.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14579) Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038918#comment-17038918
]
Claus Ibsen commented on CAMEL-14579:
-
And there may also be a bug with the disable cache with -1 - created another
ticket about that
> Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
>
>
> Key: CAMEL-14579
> URL: https://issues.apache.org/jira/browse/CAMEL-14579
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.0.1
>Reporter: Pascal Schumacher
>Priority: Minor
> Attachments: CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG,
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG
>
>
> In Camel 3.0.1 there seems to be a memory leak when you use camel-mail to
> send mails with a recipient list (see attached screenshot
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG).
> Code to reproduce:
> {code:java}
> public class SendMailDynamicToMemoryLeakTest extends CamelTestSupport {
> @Override
> protected RouteBuilder createRouteBuilder() {
> return new RouteBuilder() {
> public void configure() {
> from("scheduler:start?delay=1")
> .setBody(constant("Hello"))
> .setHeader("smtpFrom", method(UUID.class, "randomUUID"))
>
> .recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
> //
> .toD("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}");
> }
> };
> }
> @Test
> public void test() throws Exception {
> Thread.sleep(100_000_000L);
> }
> }
> {code}
> {code:xml}
>
> com.bitmechanic
> dumbster
> 1.9.0.2
>
> {code}
> {code:java}
> public class TestMailServer {
> public static void main(String[] args) throws Exception {
> ServerOptions serverOptions = new ServerOptions();
> serverOptions.port = 1234;
> SmtpServerFactory.startServer(serverOptions);
> }
> }
> {code}
> To make reproduction easier I pushed everything to
> https://github.com/PascalSchumacher/CamelSendMailMemoryLeak
> Run the TestMailServer class, then run SendMailDynamicToMemoryLeakTest.
> Using Camel 3.1.0-SNAPSHOT to run the test shows the same behavior.
> Using Camel 2.24.2 there is no memory leak.
> ---
> The original code is using toD (see commented out code in the test case
> above) instead of a recipient list. For dynamic to there seems to be a slower
> memory leak in Camel 3.0.1 (not completely sure, a lot of objects get garbage
> collected, but overall object count seems to slowly increase.)
> Using Camel 2.24.2 there is no memory leak.
> Using Camel 3.1.0-SNAPSHOT with dynamic to there seems to be a memory leak,
> see the attached screenshot CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG.
> I am not sure if the recipientList/toD behavior is limited to camel-mail or
> if it would occur for other components too. I could not replicate the
> behavior with camel-http, but this component uses optimized dynamic to and
> this may prevent the occurrence of a memory leak.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14586) camel-core - Disable cache on some EIPs seems to not be working correlction
Claus Ibsen created CAMEL-14586: --- Summary: camel-core - Disable cache on some EIPs seems to not be working correlction Key: CAMEL-14586 URL: https://issues.apache.org/jira/browse/CAMEL-14586 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.1.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.1.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14579) Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038910#comment-17038910
]
Claus Ibsen commented on CAMEL-14579:
-
Okay we can likely make camel-mail dynamic when you have headers with mail.xx
for java mail properties, and then we would have to create a prototype scoped
java mail sender if its not using the default values (as it needs to create a
new mail session).
> Camel-mail: MemoryLeak when sending mails using recipient list or dynamic to
>
>
> Key: CAMEL-14579
> URL: https://issues.apache.org/jira/browse/CAMEL-14579
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.0.1
>Reporter: Pascal Schumacher
>Priority: Minor
> Attachments: CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG,
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG
>
>
> In Camel 3.0.1 there seems to be a memory leak when you use camel-mail to
> send mails with a recipient list (see attached screenshot
> CamelMail_RecipientList_MemoryLeak_3.0.1.PNG).
> Code to reproduce:
> {code:java}
> public class SendMailDynamicToMemoryLeakTest extends CamelTestSupport {
> @Override
> protected RouteBuilder createRouteBuilder() {
> return new RouteBuilder() {
> public void configure() {
> from("scheduler:start?delay=1")
> .setBody(constant("Hello"))
> .setHeader("smtpFrom", method(UUID.class, "randomUUID"))
>
> .recipientList(simple("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}")).cacheSize(-1).end();
> //
> .toD("smtp://localhost:1234?to=t...@test.com=${header.smtpFrom}");
> }
> };
> }
> @Test
> public void test() throws Exception {
> Thread.sleep(100_000_000L);
> }
> }
> {code}
> {code:xml}
>
> com.bitmechanic
> dumbster
> 1.9.0.2
>
> {code}
> {code:java}
> public class TestMailServer {
> public static void main(String[] args) throws Exception {
> ServerOptions serverOptions = new ServerOptions();
> serverOptions.port = 1234;
> SmtpServerFactory.startServer(serverOptions);
> }
> }
> {code}
> To make reproduction easier I pushed everything to
> https://github.com/PascalSchumacher/CamelSendMailMemoryLeak
> Run the TestMailServer class, then run SendMailDynamicToMemoryLeakTest.
> Using Camel 3.1.0-SNAPSHOT to run the test shows the same behavior.
> Using Camel 2.24.2 there is no memory leak.
> ---
> The original code is using toD (see commented out code in the test case
> above) instead of a recipient list. For dynamic to there seems to be a slower
> memory leak in Camel 3.0.1 (not completely sure, a lot of objects get garbage
> collected, but overall object count seems to slowly increase.)
> Using Camel 2.24.2 there is no memory leak.
> Using Camel 3.1.0-SNAPSHOT with dynamic to there seems to be a memory leak,
> see the attached screenshot CamelMail_DyamicTo_MemoryLeak-3.1.0-SNAPSHOT.PNG.
> I am not sure if the recipientList/toD behavior is limited to camel-mail or
> if it would occur for other components too. I could not replicate the
> behavior with camel-http, but this component uses optimized dynamic to and
> this may prevent the occurrence of a memory leak.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-14585) camel-spring-boot - The BOM includes a wrong target artifactId
[
https://issues.apache.org/jira/browse/CAMEL-14585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-14585.
-
Fix Version/s: (was: 3.2.0)
3.1.0
Assignee: Claus Ibsen
Resolution: Fixed
> camel-spring-boot - The BOM includes a wrong target artifactId
> --
>
> Key: CAMEL-14585
> URL: https://issues.apache.org/jira/browse/CAMEL-14585
> Project: Camel
> Issue Type: Task
>Affects Versions: 3.1.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.1.0
>
>
> --- a/tooling/camel-spring-boot-dependencies/pom.xml
> +++ b/tooling/camel-spring-boot-dependencies/pom.xml
> @@ -1861,6 +1861,11 @@
> camel-zookeeper-starter
> ${project.version}
>
> +
> +org.apache.camel.springboot
> +target
> +${project.version}
> +
>
> org.apache.camel.tests
> org.apache.camel.tests.mock-javamail_1.7
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
