[jira] [Commented] (CAMEL-8629) Update AWS SDK from version 1.9.17 to version 1.9.30
[ https://issues.apache.org/jira/browse/CAMEL-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493649#comment-14493649 ] Andrea Cosentino commented on CAMEL-8629: - In the last days I've opened a ticket for this on ServiceMix JIRA: https://issues.apache.org/jira/browse/SM-2496 and they resolved it yesterday. Update AWS SDK from version 1.9.17 to version 1.9.30 Key: CAMEL-8629 URL: https://issues.apache.org/jira/browse/CAMEL-8629 Project: Camel Issue Type: Task Components: camel-aws Reporter: Andrea Cosentino Assignee: Claus Ibsen Priority: Minor Fix For: 2.16.0 After the latest update from old version of SDK to 1.9.17, I've opened a ticket into Servicemix JIRA to ask for a bundle release of latest AWS SDK version, 1.9.30. The ticket has been resolved. We need to update the dependency from 1.9.17 to 1.9.30. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8626) Leaking exchangesInFlightKeys in ManagedRoute
[
https://issues.apache.org/jira/browse/CAMEL-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-8626:
---
Attachment: camel-core-2.15.2-SNAPSHOT.jar
attached fixed camel-core JAR
Leaking exchangesInFlightKeys in ManagedRoute
-
Key: CAMEL-8626
URL: https://issues.apache.org/jira/browse/CAMEL-8626
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.1
Environment: Java 8 u 40 64 bit, Linux
Reporter: Mateusz Nowakowski
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.15.2, 2.16.0
Attachments: camel-core-2.15.2-SNAPSHOT.jar
Having a camel context with a single route:
{code}
onException(Throwable.class)
.handled(true)
.process(handleException()); // essentially doing
exchange.setException(someConvertedException);
from(direct:generalFlow)
.routingSlip(property(GeneralFlowRoute.class.getName()));
{code}
started from Spring:
{code}
camelContext id=flows xmlns=http://camel.apache.org/schema/spring;
template id=template defaultEndpoint=direct:generalFlow/
routeBuilder ref=generalFlow/
/camelContext
bean id=generalFlow class=com.blabla.GeneralFlowRoute/
{code}
During performance test both exchangesInFlightKeys and
exchangesInFlightStartTimestamps are accumulating over time.
But if the test is run in one thread with debug - nothing is accumulated.
Issue found after migration from 2.14.1 to 2.15.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8627) Update Infinispan version from 6.0.2.Final to 7.1.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493641#comment-14493641 ] ASF GitHub Bot commented on CAMEL-8627: --- Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/484 Update Infinispan version from 6.0.2.Final to 7.1.1.Final - Key: CAMEL-8627 URL: https://issues.apache.org/jira/browse/CAMEL-8627 Project: Camel Issue Type: Task Components: camel-infinispan Reporter: Andrea Cosentino Priority: Minor Fix For: 2.16.0 We need to update Infinispan from version 6.0.2.Final to the latest stable version 7.1.1.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8626) Leaking exchangesInFlightKeys in ManagedRoute
[
https://issues.apache.org/jira/browse/CAMEL-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-8626:
--
Assignee: Claus Ibsen
Leaking exchangesInFlightKeys in ManagedRoute
-
Key: CAMEL-8626
URL: https://issues.apache.org/jira/browse/CAMEL-8626
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.1
Environment: Java 8 u 40 64 bit, Linux
Reporter: Mateusz Nowakowski
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.15.2, 2.16.0
Having a camel context with a single route:
{code}
onException(Throwable.class)
.handled(true)
.process(handleException()); // essentially doing
exchange.setException(someConvertedException);
from(direct:generalFlow)
.routingSlip(property(GeneralFlowRoute.class.getName()));
{code}
started from Spring:
{code}
camelContext id=flows xmlns=http://camel.apache.org/schema/spring;
template id=template defaultEndpoint=direct:generalFlow/
routeBuilder ref=generalFlow/
/camelContext
bean id=generalFlow class=com.blabla.GeneralFlowRoute/
{code}
During performance test both exchangesInFlightKeys and
exchangesInFlightStartTimestamps are accumulating over time.
But if the test is run in one thread with debug - nothing is accumulated.
Issue found after migration from 2.14.1 to 2.15.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8626) Leaking exchangesInFlightKeys in ManagedRoute
[
https://issues.apache.org/jira/browse/CAMEL-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493644#comment-14493644
]
Claus Ibsen commented on CAMEL-8626:
Thanks for reporting, its when an exchange had failed the leak happens. Not for
succesfull exchanges.
Leaking exchangesInFlightKeys in ManagedRoute
-
Key: CAMEL-8626
URL: https://issues.apache.org/jira/browse/CAMEL-8626
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.1
Environment: Java 8 u 40 64 bit, Linux
Reporter: Mateusz Nowakowski
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.15.2, 2.16.0
Having a camel context with a single route:
{code}
onException(Throwable.class)
.handled(true)
.process(handleException()); // essentially doing
exchange.setException(someConvertedException);
from(direct:generalFlow)
.routingSlip(property(GeneralFlowRoute.class.getName()));
{code}
started from Spring:
{code}
camelContext id=flows xmlns=http://camel.apache.org/schema/spring;
template id=template defaultEndpoint=direct:generalFlow/
routeBuilder ref=generalFlow/
/camelContext
bean id=generalFlow class=com.blabla.GeneralFlowRoute/
{code}
During performance test both exchangesInFlightKeys and
exchangesInFlightStartTimestamps are accumulating over time.
But if the test is run in one thread with debug - nothing is accumulated.
Issue found after migration from 2.14.1 to 2.15.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8626) Leaking exchangesInFlightKeys in ManagedRoute
[
https://issues.apache.org/jira/browse/CAMEL-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493694#comment-14493694
]
Claus Ibsen commented on CAMEL-8626:
I have build a JAR with the fix, you are welcome to give a test.
You can also build from source yourself
http://camel.apache.org/building.html
Leaking exchangesInFlightKeys in ManagedRoute
-
Key: CAMEL-8626
URL: https://issues.apache.org/jira/browse/CAMEL-8626
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.1
Environment: Java 8 u 40 64 bit, Linux
Reporter: Mateusz Nowakowski
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.15.2, 2.16.0
Attachments: camel-core-2.15.2-SNAPSHOT.jar
Having a camel context with a single route:
{code}
onException(Throwable.class)
.handled(true)
.process(handleException()); // essentially doing
exchange.setException(someConvertedException);
from(direct:generalFlow)
.routingSlip(property(GeneralFlowRoute.class.getName()));
{code}
started from Spring:
{code}
camelContext id=flows xmlns=http://camel.apache.org/schema/spring;
template id=template defaultEndpoint=direct:generalFlow/
routeBuilder ref=generalFlow/
/camelContext
bean id=generalFlow class=com.blabla.GeneralFlowRoute/
{code}
During performance test both exchangesInFlightKeys and
exchangesInFlightStartTimestamps are accumulating over time.
But if the test is run in one thread with debug - nothing is accumulated.
Issue found after migration from 2.14.1 to 2.15.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8627) Update Infinispan version from 6.0.2.Final to 7.1.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493637#comment-14493637 ] Andrea Cosentino commented on CAMEL-8627: - First of all: sorry for this. I close the PR and work on this. Update Infinispan version from 6.0.2.Final to 7.1.1.Final - Key: CAMEL-8627 URL: https://issues.apache.org/jira/browse/CAMEL-8627 Project: Camel Issue Type: Task Components: camel-infinispan Reporter: Andrea Cosentino Priority: Minor Fix For: 2.16.0 We need to update Infinispan from version 6.0.2.Final to the latest stable version 7.1.1.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8631) Allow use of Spring 4 in Karaf environment
Martin Lichtin created CAMEL-8631: - Summary: Allow use of Spring 4 in Karaf environment Key: CAMEL-8631 URL: https://issues.apache.org/jira/browse/CAMEL-8631 Project: Camel Issue Type: Improvement Affects Versions: 2.15.1 Environment: Karaf 3.0.3 Reporter: Martin Lichtin It's currently not possible to use Camel with Spring version 4. When first installing Spring 4: feature:install -v spring/4.1.2.RELEASE_1 and then installing Camel: feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.15.1/xml/features feature:install camel The Camel feature file will actually install Spring 3 and not use the version 4 that is already installed. One can verify this with bundle:requirements camel-spring to see that it resolved the 'spring' packages with 3.2.11.RELEASE and not version 4. E.g.: osgi.wiring.package; ((osgi.wiring.package=org.springframework.beans)(version=3.2.0)(!(version=5.0.0))) resolved by: osgi.wiring.package; org.springframework.beans 3.2.11.RELEASE from org.apache.servicemix.bundles.spring-beans [83] I believe the Camel features file needs to be modified to support Spring 4. It currently has range restrictions that exclude version 4. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8632) httpBindingRef httpBinding for the servlet component documentation
Richard Groote created CAMEL-8632: - Summary: httpBindingRef httpBinding for the servlet component documentation Key: CAMEL-8632 URL: https://issues.apache.org/jira/browse/CAMEL-8632 Project: Camel Issue Type: Improvement Components: camel-servlet Reporter: Richard Groote Priority: Minor In the documentation of apache camel servlet (http://camel.apache.org/servlet.html) the option for the HttpBindingRef is missing. HttpBinding is not supported on the servlet. It would be nice if this works the same as for the HTTP component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8633) Servlet Multipart
[ https://issues.apache.org/jira/browse/CAMEL-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Groote updated CAMEL-8633: -- Attachment: ServletHttpBinding.java Servlet Multipart Key: CAMEL-8633 URL: https://issues.apache.org/jira/browse/CAMEL-8633 Project: Camel Issue Type: Improvement Components: camel-http, camel-servlet Affects Versions: 2.12.4 Reporter: Richard Groote Attachments: ServletHttpBinding.java The servlet component cannot handle attachments from a multipart request. In our situation a REST multipart call is made and the attachments must be handled. I created a extension on the DefaultHttpBinding and added functionality for multipart parsing. May be this functionality can be added to apache camel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8626) Leaking exchangesInFlightKeys in ManagedRoute
[
https://issues.apache.org/jira/browse/CAMEL-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493828#comment-14493828
]
Mateusz Nowakowski commented on CAMEL-8626:
---
Thanks for a fast fix.
WIll run a test again and will have report tomorrow after 6 AM CDT.
Leaking exchangesInFlightKeys in ManagedRoute
-
Key: CAMEL-8626
URL: https://issues.apache.org/jira/browse/CAMEL-8626
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.15.1
Environment: Java 8 u 40 64 bit, Linux
Reporter: Mateusz Nowakowski
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.15.2, 2.16.0
Attachments: camel-core-2.15.2-SNAPSHOT.jar
Having a camel context with a single route:
{code}
onException(Throwable.class)
.handled(true)
.process(handleException()); // essentially doing
exchange.setException(someConvertedException);
from(direct:generalFlow)
.routingSlip(property(GeneralFlowRoute.class.getName()));
{code}
started from Spring:
{code}
camelContext id=flows xmlns=http://camel.apache.org/schema/spring;
template id=template defaultEndpoint=direct:generalFlow/
routeBuilder ref=generalFlow/
/camelContext
bean id=generalFlow class=com.blabla.GeneralFlowRoute/
{code}
During performance test both exchangesInFlightKeys and
exchangesInFlightStartTimestamps are accumulating over time.
But if the test is run in one thread with debug - nothing is accumulated.
Issue found after migration from 2.14.1 to 2.15.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8628) camel-dozer component fails when multiple expressions are used in a mapping
[
https://issues.apache.org/jira/browse/CAMEL-8628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494031#comment-14494031
]
ASF GitHub Bot commented on CAMEL-8628:
---
Github user kcbabo closed the pull request at:
https://github.com/apache/camel/pull/485
camel-dozer component fails when multiple expressions are used in a mapping
---
Key: CAMEL-8628
URL: https://issues.apache.org/jira/browse/CAMEL-8628
Project: Camel
Issue Type: Bug
Components: camel-dozer
Affects Versions: 2.15.1
Reporter: Keith Babo
Assignee: Claus Ibsen
Fix For: 2.15.2, 2.16.0
The reference to the current exchange is cleared on each invocation of
ExpressionMapper in the done() method. If a mapping file contains multiple
expression mappings, the first expression clears out the exchange reference
and subsequent expression mappings fail with:
{noformat}
java.lang.IllegalStateException: Current exchange has not been set for
ExpressionMapper
{noformat}
Fix is to not clear the reference in ExpressionMapper.done(). We should do
this in DozerProducer after all mappings in the mapping file have completed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CAMEL-8635) XStream no longer supports dynamic CL updates
[ https://issues.apache.org/jira/browse/CAMEL-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8635. Resolution: Fixed Fix Version/s: 2.16.0 XStream no longer supports dynamic CL updates - Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Improvement Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Assignee: Willem Jiang Fix For: 2.15.2, 2.16.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8635) XStream no longer supports dynamic CL updates
[ https://issues.apache.org/jira/browse/CAMEL-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494182#comment-14494182 ] Willem Jiang commented on CAMEL-8635: - Merged the patch into camel-2.15.x and camel master branches with thanks to Thomas. XStream no longer supports dynamic CL updates - Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Improvement Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Assignee: Willem Jiang Fix For: 2.15.2, 2.16.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8634) Wire tap - Should emit event notification about sending to tapped endpoint
[ https://issues.apache.org/jira/browse/CAMEL-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8634. Resolution: Fixed Wire tap - Should emit event notification about sending to tapped endpoint -- Key: CAMEL-8634 URL: https://issues.apache.org/jira/browse/CAMEL-8634 Project: Camel Issue Type: Improvement Components: camel-core, eip Affects Versions: 2.15.1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.2, 2.16.0 See nabble http://camel.465427.n5.nabble.com/Wiretap-not-firing-events-tp5765760.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8635) XStream does no longer support dynamic CL updates
Thomas Diesler created CAMEL-8635: - Summary: XStream does no longer support dynamic CL updates Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Bug Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Fix For: 2.15.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8635) XStream no longer supports dynamic CL updates
[ https://issues.apache.org/jira/browse/CAMEL-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494175#comment-14494175 ] Claus Ibsen commented on CAMEL-8635: Thomas do be aware that the correct procedure would be PR against master branch that are then cherry picked to older branches such as 2.15.x. However your PR is targeted against 2.15.x. So its the opposite. XStream no longer supports dynamic CL updates - Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Improvement Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Assignee: Willem Jiang Fix For: 2.15.2, 2.16.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8054) Use SharedEntityManager to reduce connections
[ https://issues.apache.org/jira/browse/CAMEL-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8054. Resolution: Fixed Thanks for the patch. Use SharedEntityManager to reduce connections - Key: CAMEL-8054 URL: https://issues.apache.org/jira/browse/CAMEL-8054 Project: Camel Issue Type: New Feature Components: camel-jpa Affects Versions: 2.13.2 Reporter: Chris Watts Assignee: Claus Ibsen Fix For: 2.16.0 Attachments: CAMEL-8054-sharedEntityManager-2.13.patch, CAMEL-8054-sharedEntityManager-2.14.patch, camel-sharedEntityManager.patch When using JpaTransactionManager it Binds a JPA EntityManager from the specified factory to the thread. Meaning that on top of the EntityManager created for each JpaConsumer, each time it creates a new EntityManager. New property: *sharedEntityManager* - whether to use spring's SharedEntityManager for the consumer/producer. Sets joinTransaction=false Also added as a property to the JpaComponent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8635) XStream no longer supports dynamic CL updates
[ https://issues.apache.org/jira/browse/CAMEL-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494167#comment-14494167 ] ASF GitHub Bot commented on CAMEL-8635: --- GitHub user tdiesler opened a pull request: https://github.com/apache/camel/pull/487 [CAMEL-8635] XStream no longer supports dynamic CL updates You can merge this pull request into a Git repository by running: $ git pull https://github.com/tdiesler/camel camel-8635 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/487.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #487 commit 5e3c9d9bb1cd59f2dc31730b170588bcedf0ffe5 Author: Thomas Diesler thomas.dies...@jboss.com Date: 2015-04-14T14:35:46Z [CAMEL-8635] XStream no longer supports dynamic CL updates XStream no longer supports dynamic CL updates - Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Bug Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Fix For: 2.15.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8054) Use SharedEntityManager to reduce connections
[ https://issues.apache.org/jira/browse/CAMEL-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8054: -- Assignee: Claus Ibsen Use SharedEntityManager to reduce connections - Key: CAMEL-8054 URL: https://issues.apache.org/jira/browse/CAMEL-8054 Project: Camel Issue Type: New Feature Components: camel-jpa Affects Versions: 2.13.2 Reporter: Chris Watts Assignee: Claus Ibsen Fix For: 2.16.0 Attachments: CAMEL-8054-sharedEntityManager-2.13.patch, CAMEL-8054-sharedEntityManager-2.14.patch, camel-sharedEntityManager.patch When using JpaTransactionManager it Binds a JPA EntityManager from the specified factory to the thread. Meaning that on top of the EntityManager created for each JpaConsumer, each time it creates a new EntityManager. New property: *sharedEntityManager* - whether to use spring's SharedEntityManager for the consumer/producer. Sets joinTransaction=false Also added as a property to the JpaComponent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8054) Use SharedEntityManager to reduce connections
[ https://issues.apache.org/jira/browse/CAMEL-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8054: --- Fix Version/s: 2.16.0 Use SharedEntityManager to reduce connections - Key: CAMEL-8054 URL: https://issues.apache.org/jira/browse/CAMEL-8054 Project: Camel Issue Type: New Feature Components: camel-jpa Affects Versions: 2.13.2 Reporter: Chris Watts Fix For: 2.16.0 Attachments: CAMEL-8054-sharedEntityManager-2.13.patch, CAMEL-8054-sharedEntityManager-2.14.patch, camel-sharedEntityManager.patch When using JpaTransactionManager it Binds a JPA EntityManager from the specified factory to the thread. Meaning that on top of the EntityManager created for each JpaConsumer, each time it creates a new EntityManager. New property: *sharedEntityManager* - whether to use spring's SharedEntityManager for the consumer/producer. Sets joinTransaction=false Also added as a property to the JpaComponent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8085) Add handling of offset in case of auto commit is disabled to prevent data loss
[ https://issues.apache.org/jira/browse/CAMEL-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14495179#comment-14495179 ] yogananth mahalingam commented on CAMEL-8085: - I am observing one issue with the implementation. For the last batch of messages that is getting processed, offset is not getting commited to ZK. Can you handle this scenario as well? Add handling of offset in case of auto commit is disabled to prevent data loss -- Key: CAMEL-8085 URL: https://issues.apache.org/jira/browse/CAMEL-8085 Project: Camel Issue Type: Improvement Components: camel-kafka Affects Versions: 2.14.0 Reporter: Ivan Vasyliev Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 In order to prevent data loss kafka client allows to manually handle consumer offset. According to this lady: http://ingest.tips/2014/10/12/kafka-high-level-consumer-frequently-missing-pieces/ Kafka consumer commitOffset is committing offset for each consumer and for all streams of this consumer. I've made changes in camel-kafka in order to support handling of offset in case of auto-commit option is disabled. https://github.com/apache/camel/pull/342 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8632) httpBindingRef httpBinding for the servlet component documentation
[ https://issues.apache.org/jira/browse/CAMEL-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-8632: --- Assignee: Willem Jiang httpBindingRef httpBinding for the servlet component documentation Key: CAMEL-8632 URL: https://issues.apache.org/jira/browse/CAMEL-8632 Project: Camel Issue Type: Improvement Components: camel-servlet Reporter: Richard Groote Assignee: Willem Jiang Priority: Minor In the documentation of apache camel servlet (http://camel.apache.org/servlet.html) the option for the HttpBindingRef is missing. HttpBinding is not supported on the servlet. It would be nice if this works the same as for the HTTP component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8635) XStream no longer supports dynamic CL updates
[ https://issues.apache.org/jira/browse/CAMEL-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-8635: -- Summary: XStream no longer supports dynamic CL updates (was: XStream does no longer support dynamic CL updates) XStream no longer supports dynamic CL updates - Key: CAMEL-8635 URL: https://issues.apache.org/jira/browse/CAMEL-8635 Project: Camel Issue Type: Bug Components: camel-xstream Affects Versions: 2.15.1 Reporter: Thomas Diesler Fix For: 2.15.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8054) Use SharedEntityManager to reduce connections
[ https://issues.apache.org/jira/browse/CAMEL-8054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494797#comment-14494797 ] ASF GitHub Bot commented on CAMEL-8054: --- Github user devgrok closed the pull request at: https://github.com/apache/camel/pull/417 Use SharedEntityManager to reduce connections - Key: CAMEL-8054 URL: https://issues.apache.org/jira/browse/CAMEL-8054 Project: Camel Issue Type: New Feature Components: camel-jpa Affects Versions: 2.13.2 Reporter: Chris Watts Assignee: Claus Ibsen Fix For: 2.16.0 Attachments: CAMEL-8054-sharedEntityManager-2.13.patch, CAMEL-8054-sharedEntityManager-2.14.patch, camel-sharedEntityManager.patch When using JpaTransactionManager it Binds a JPA EntityManager from the specified factory to the thread. Meaning that on top of the EntityManager created for each JpaConsumer, each time it creates a new EntityManager. New property: *sharedEntityManager* - whether to use spring's SharedEntityManager for the consumer/producer. Sets joinTransaction=false Also added as a property to the JpaComponent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8627) Update Infinispan version from 6.0.2.Final to 7.1.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494839#comment-14494839 ] Andrea Cosentino commented on CAMEL-8627: - PR submitted: https://github.com/apache/camel/pull/488 There were some things to change inside features.xml and some dependencies version to change. Infinispan 7.1.1.Final bundle now depends on jboss-marshalling-osgi bundle and no more from jboss-marshalling bundle. Update Infinispan version from 6.0.2.Final to 7.1.1.Final - Key: CAMEL-8627 URL: https://issues.apache.org/jira/browse/CAMEL-8627 Project: Camel Issue Type: Task Components: camel-infinispan Reporter: Andrea Cosentino Priority: Minor Fix For: 2.16.0 We need to update Infinispan from version 6.0.2.Final to the latest stable version 7.1.1.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8627) Update Infinispan version from 6.0.2.Final to 7.1.1.Final
[ https://issues.apache.org/jira/browse/CAMEL-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494829#comment-14494829 ] ASF GitHub Bot commented on CAMEL-8627: --- GitHub user oscerd opened a pull request: https://github.com/apache/camel/pull/488 CAMEL-8627 Update Infinispan version from 6.0.2.Final to 7.1.1.Final Hi everyone, This PR is related to: https://issues.apache.org/jira/browse/CAMEL-8627 Thanks. Bye, Andrea You can merge this pull request into a Git repository by running: $ git pull https://github.com/oscerd/camel update-infinispan-to-7.1.1.Final Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/488.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #488 commit 6d7491391b88943e2e134fa52b1242db3f4bdd89 Author: ancosen anco...@gmail.com Date: 2015-04-14T20:37:03Z Resolve CAMEL-8627 Update Infinispan version from 6.0.2.Final to 7.1.1.Final Update Infinispan version from 6.0.2.Final to 7.1.1.Final - Key: CAMEL-8627 URL: https://issues.apache.org/jira/browse/CAMEL-8627 Project: Camel Issue Type: Task Components: camel-infinispan Reporter: Andrea Cosentino Priority: Minor Fix For: 2.16.0 We need to update Infinispan from version 6.0.2.Final to the latest stable version 7.1.1.Final -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8629) Update AWS SDK from version 1.9.17 to version 1.9.30
[ https://issues.apache.org/jira/browse/CAMEL-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494051#comment-14494051 ] ASF GitHub Bot commented on CAMEL-8629: --- Github user oscerd closed the pull request at: https://github.com/apache/camel/pull/486 Update AWS SDK from version 1.9.17 to version 1.9.30 Key: CAMEL-8629 URL: https://issues.apache.org/jira/browse/CAMEL-8629 Project: Camel Issue Type: Task Components: camel-aws Reporter: Andrea Cosentino Assignee: Claus Ibsen Priority: Minor Fix For: 2.16.0 After the latest update from old version of SDK to 1.9.17, I've opened a ticket into Servicemix JIRA to ask for a bundle release of latest AWS SDK version, 1.9.30. The ticket has been resolved. We need to update the dependency from 1.9.17 to 1.9.30. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-6415) camel-twitter - Support for the User Stream Endpoint
[ https://issues.apache.org/jira/browse/CAMEL-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6415. Resolution: Fixed Fix Version/s: 2.16.0 Assignee: Claus Ibsen Thanks Alex for the patch. camel-twitter - Support for the User Stream Endpoint Key: CAMEL-6415 URL: https://issues.apache.org/jira/browse/CAMEL-6415 Project: Camel Issue Type: New Feature Components: camel-twitter Affects Versions: 2.11.0 Reporter: Jason Separovic Assignee: Claus Ibsen Fix For: 2.16.0 Attachments: camel-twitter-userstreaming-support.patch Tweets from protected accounts can only be received on the user and site stream endpoints. It would be good to see this functionality added to the camel-twitter component so that protected tweets can be received by camel. The Hosebird Client could be used: https://github.com/twitter/hbc If connecting to a userstream, use Twitter4jUserstreamClient. If making a sitestream connection, use Twitter4jSitestreamClient -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8634) Wire tap - Should emit event notification about sending to tapped endpoint
Claus Ibsen created CAMEL-8634: -- Summary: Wire tap - Should emit event notification about sending to tapped endpoint Key: CAMEL-8634 URL: https://issues.apache.org/jira/browse/CAMEL-8634 Project: Camel Issue Type: Improvement Components: camel-core, eip Affects Versions: 2.15.1 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.15.2, 2.16.0 See nabble http://camel.465427.n5.nabble.com/Wiretap-not-firing-events-tp5765760.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7563) Allow passing HazelcastInstance as a query parameter of a Hazelcast component endpoint.
[ https://issues.apache.org/jira/browse/CAMEL-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494060#comment-14494060 ] ASF GitHub Bot commented on CAMEL-7563: --- Github user alexlomov closed the pull request at: https://github.com/apache/camel/pull/211 Allow passing HazelcastInstance as a query parameter of a Hazelcast component endpoint. --- Key: CAMEL-7563 URL: https://issues.apache.org/jira/browse/CAMEL-7563 Project: Camel Issue Type: Improvement Components: camel-hazelcast Reporter: Alexander Lomov Assignee: Willem Jiang Priority: Minor Fix For: 2.14.0 It is impossible now to pass an existing HazelcastInstance to a HazelcastEndpoint as a bean from Registry. It complicates Hazelcast Endpoint usage in any DI environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
