[jira] [Commented] (CAMEL-9143) Producers that implement the ServicePoolAware interface cause memory leak due to JMX references

[ https://issues.apache.org/jira/browse/CAMEL-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791806#comment-14791806 ] Bob Browning commented on CAMEL-9143: - Yes in the TC as the intent was to simulate RemoteFileXxx it

[jira] [Updated] (CAMEL-9143) Producers that implement the ServicePoolAware interface cause memory leak due to JMX references

[ https://issues.apache.org/jira/browse/CAMEL-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-9143: Description: h4. Description Producer instances that implement the ServicePoolAware interface will

[jira] [Updated] (CAMEL-9143) Producers that implement the ServicePoolAware interface cause memory leak due to JMX references

[ https://issues.apache.org/jira/browse/CAMEL-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-9143: Affects Version/s: (was: 2.14.3) > Producers that implement the ServicePoolAware interface

[jira] [Created] (CAMEL-9143) Producers that implement the ServicePoolAware interface cause memory leak due to JMX references

Bob Browning created CAMEL-9143: --- Summary: Producers that implement the ServicePoolAware interface cause memory leak due to JMX references Key: CAMEL-9143 URL: https://issues.apache.org/jira/browse/CAMEL-9143

[jira] [Created] (CAMEL-9013) Camel HTTP no longer supporting chunked transfer encoding with Tomcat

Bob Browning created CAMEL-9013: --- Summary: Camel HTTP no longer supporting chunked transfer encoding with Tomcat Key: CAMEL-9013 URL: https://issues.apache.org/jira/browse/CAMEL-9013 Project: Camel

[jira] [Created] (CAMEL-8088) FTP can wait indefinitely when connection timeout occurs during connect

Bob Browning created CAMEL-8088: --- Summary: FTP can wait indefinitely when connection timeout occurs during connect Key: CAMEL-8088 URL: https://issues.apache.org/jira/browse/CAMEL-8088 Project: Camel

[jira] [Updated] (CAMEL-8088) FTP can wait indefinitely when connection timeout occurs during connect

[ https://issues.apache.org/jira/browse/CAMEL-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-8088: Description: In our production system we have seen cases where the FTP thread is waiting for a

[jira] [Updated] (CAMEL-7644) Scala camel DSL creates numerous DefaultCamelContext instances

[ https://issues.apache.org/jira/browse/CAMEL-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7644: Description: Since the camel DSL is invoked prior to `.addRoutesToCamelContext(CamelContext)`

[jira] [Updated] (CAMEL-7644) Scala camel DSL creates numerous DefaultCamelContext instances

[ https://issues.apache.org/jira/browse/CAMEL-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7644: Description: Since the camel DSL is invoked prior to `.addRoutesToCamelContext(CamelContext)`

[jira] [Created] (CAMEL-7644) Scala camel DSL creates numerous DefaultCamelContext instances

Bob Browning created CAMEL-7644: --- Summary: Scala camel DSL creates numerous DefaultCamelContext instances Key: CAMEL-7644 URL: https://issues.apache.org/jira/browse/CAMEL-7644 Project: Camel

[jira] [Created] (CAMEL-7500) Concurrent modification of exchange during retry leads to futher processing of failed messages

Bob Browning created CAMEL-7500: --- Summary: Concurrent modification of exchange during retry leads to futher processing of failed messages Key: CAMEL-7500 URL: https://issues.apache.org/jira/browse/CAMEL-7500

[jira] [Updated] (CAMEL-7500) Concurrent modification of exchange during retry leads to futher processing of failed messages

[ https://issues.apache.org/jira/browse/CAMEL-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7500: Attachment: NettyRedeliveryTest.java Concurrent modification of exchange during retry leads to

[jira] [Updated] (CAMEL-7500) Concurrent modification of exchange during retry after netty TCP failure leads to futher processing of failed messages

[ https://issues.apache.org/jira/browse/CAMEL-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7500: Summary: Concurrent modification of exchange during retry after netty TCP failure leads to futher

[jira] [Updated] (CAMEL-7500) Concurrent modification of exchange during retry after netty TCP failure leads to futher processing of failed messages

[ https://issues.apache.org/jira/browse/CAMEL-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7500: Attachment: NettyRedeliveryTest.java Concurrent modification of exchange during retry after netty

[jira] [Updated] (CAMEL-7500) Concurrent modification of exchange during retry after netty TCP failure leads to futher processing of failed messages

[ https://issues.apache.org/jira/browse/CAMEL-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7500: Attachment: (was: NettyRedeliveryTest.java) Concurrent modification of exchange during retry

[jira] [Created] (CAMEL-7276) camel-quartz - use of management name to provide default scheduler name breaks context isolation

Bob Browning created CAMEL-7276: --- Summary: camel-quartz - use of management name to provide default scheduler name breaks context isolation Key: CAMEL-7276 URL: https://issues.apache.org/jira/browse/CAMEL-7276

[jira] [Updated] (CAMEL-7276) camel-quartz - use of management name to provide default scheduler name breaks context isolation

[ https://issues.apache.org/jira/browse/CAMEL-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bob Browning updated CAMEL-7276: Description: When using the camel-quartz component in an unmanged context with multiple camel