[jira] [Updated] (CAMEL-7363) camel headers are not preserverd in camel-ahc component
[ https://issues.apache.org/jira/browse/CAMEL-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Siano updated CAMEL-7363: - Patch Info: Patch Available camel headers are not preserverd in camel-ahc component --- Key: CAMEL-7363 URL: https://issues.apache.org/jira/browse/CAMEL-7363 Project: Camel Issue Type: Bug Components: camel-ahc Affects Versions: 2.12.3, 2.13.0 Reporter: Stephan Siano Attachments: 0001-CAMEL-7363-camel-headers-are-not-preserverd-in-camel.patch The documentation of the camel-ahc component states: ... All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally Camel will add the HTTP response headers as well to the OUT message headers. However this is not true. Camel headers are not copied from the in to the out message. I have looked up other components doing http requests (http4 and cxf) and these components do copy the headers from the in to the out message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7363) camel headers are not preserverd in camel-ahc component
[ https://issues.apache.org/jira/browse/CAMEL-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Siano updated CAMEL-7363: - Attachment: 0001-CAMEL-7363-camel-headers-are-not-preserverd-in-camel.patch camel headers are not preserverd in camel-ahc component --- Key: CAMEL-7363 URL: https://issues.apache.org/jira/browse/CAMEL-7363 Project: Camel Issue Type: Bug Components: camel-ahc Affects Versions: 2.12.3, 2.13.0 Reporter: Stephan Siano Attachments: 0001-CAMEL-7363-camel-headers-are-not-preserverd-in-camel.patch The documentation of the camel-ahc component states: ... All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally Camel will add the HTTP response headers as well to the OUT message headers. However this is not true. Camel headers are not copied from the in to the out message. I have looked up other components doing http requests (http4 and cxf) and these components do copy the headers from the in to the out message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7363) camel headers are not preserverd in camel-ahc component
[ https://issues.apache.org/jira/browse/CAMEL-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968120#comment-13968120 ] Stephan Siano commented on CAMEL-7363: -- BTW: There was even a unit test for this, however it contained a bug: the test route just returned all the request headers in the HTTP response, so the headers were passed through via the server. camel headers are not preserverd in camel-ahc component --- Key: CAMEL-7363 URL: https://issues.apache.org/jira/browse/CAMEL-7363 Project: Camel Issue Type: Bug Components: camel-ahc Affects Versions: 2.12.3, 2.13.0 Reporter: Stephan Siano Attachments: 0001-CAMEL-7363-camel-headers-are-not-preserverd-in-camel.patch The documentation of the camel-ahc component states: ... All headers from the IN message will be copied to the OUT message, so headers are preserved during routing. Additionally Camel will add the HTTP response headers as well to the OUT message headers. However this is not true. Camel headers are not copied from the in to the out message. I have looked up other components doing http requests (http4 and cxf) and these components do copy the headers from the in to the out message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilgin Ibryam reassigned CAMEL-6999: Assignee: Henryk Konsek (was: Bilgin Ibryam) Assigning to Henryk as he already took good care of this issue. Component page is remaining still. Camel component for dropbox integration --- Key: CAMEL-6999 URL: https://issues.apache.org/jira/browse/CAMEL-6999 Project: Camel Issue Type: New Feature Affects Versions: 2.12.1 Reporter: Giovanni Marigi Assignee: Henryk Konsek Priority: Minor Labels: camel, dropbox Fix For: Future Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7360) Add HTTP Date header
[ https://issues.apache.org/jira/browse/CAMEL-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968172#comment-13968172 ] Willem Jiang commented on CAMEL-7360: - Applied the patch into camel master branche with thanks to Dai, I also added unit test to verify the change. Add HTTP Date header Key: CAMEL-7360 URL: https://issues.apache.org/jira/browse/CAMEL-7360 Project: Camel Issue Type: Improvement Components: camel-jetty Affects Versions: 2.13.0 Reporter: Dai Kuroda Assignee: Willem Jiang Priority: Minor Attachments: patchfile.txt http://camel.465427.n5.nabble.com/Patch-camel-jetty-tc5750112.html http://servicemix.396122.n5.nabble.com/HTTP-Date-headers-for-Jetty-endpoints-td5718803.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7360) Add HTTP Date header
[ https://issues.apache.org/jira/browse/CAMEL-7360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7360. - Resolution: Fixed Fix Version/s: 2.14.0 I just updated the wiki page for it. Add HTTP Date header Key: CAMEL-7360 URL: https://issues.apache.org/jira/browse/CAMEL-7360 Project: Camel Issue Type: Improvement Components: camel-jetty Affects Versions: 2.13.0 Reporter: Dai Kuroda Assignee: Willem Jiang Priority: Minor Fix For: 2.14.0 Attachments: patchfile.txt http://camel.465427.n5.nabble.com/Patch-camel-jetty-tc5750112.html http://servicemix.396122.n5.nabble.com/HTTP-Date-headers-for-Jetty-endpoints-td5718803.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7362) Add URI option support of maxTotalConnections and connectionsPerRoute
[ https://issues.apache.org/jira/browse/CAMEL-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7362. - Resolution: Fixed Applied the patch into camel master and updated the wiki page. Add URI option support of maxTotalConnections and connectionsPerRoute - Key: CAMEL-7362 URL: https://issues.apache.org/jira/browse/CAMEL-7362 Project: Camel Issue Type: New Feature Components: camel-http4 Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.14.0 We could support to set these parameters through the http4 endpoint uri if we don't specify the connection manager in the http component. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7364) JpaMessageIdRepository uses EntityManager non thread-safe
Denis created CAMEL-7364: Summary: JpaMessageIdRepository uses EntityManager non thread-safe Key: CAMEL-7364 URL: https://issues.apache.org/jira/browse/CAMEL-7364 Project: Camel Issue Type: Bug Components: camel-jpa Affects Versions: 2.12.3 Environment: tomcat 7.0.32, hibernate 4.1.4.Final, spring 3.1.4.RELEASE Reporter: Denis In our product we have found strange behavior of JpaMessageIdRepository when change version 2.9.2 to 2.12.3. The reason for this was that EntityManager assigned in the constructor org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository, but EntityManager not required to be thread safe. http://download.oracle.com/otn-pub/jcp/persistence-2.0-fr-oth-JSpec/persistence-2_0-final-spec.pdf page 286. I think need assign the EntityManager in each method separately. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7118) Hazelcast-based Recoverable Aggregation Repository
[ https://issues.apache.org/jira/browse/CAMEL-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968354#comment-13968354 ] ASF GitHub Bot commented on CAMEL-7118: --- Github user alexlomov closed the pull request at: https://github.com/apache/camel/pull/84 Hazelcast-based Recoverable Aggregation Repository -- Key: CAMEL-7118 URL: https://issues.apache.org/jira/browse/CAMEL-7118 Project: Camel Issue Type: New Feature Components: camel-hazelcast Environment: Any Reporter: Alexander Lomov Priority: Minor Labels: features Fix For: 2.13.1 This patch introduces HazelcastAggregationRepository class that implements RecoverableAggregationRepository and OptimisticLockingAggregationRepository. This class uses a Hazelcast distributed maps as a backing store for operational and persisted exchanges. This repository is aimed to support aggregation in an environment where multiple hosts run identical Camel routes which participate an aggregation process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7365) Camel versus Karaf versions
Martin Lichtin created CAMEL-7365: - Summary: Camel versus Karaf versions Key: CAMEL-7365 URL: https://issues.apache.org/jira/browse/CAMEL-7365 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Priority: Minor Can page http://camel.apache.org/karaf.html be brought up to date? For example, I'd like to upgrade to Karaf 3.0.1 and it's not clear which version (or version range) would be suitable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7358) Tracer - Should have options to allow streams or files
[ https://issues.apache.org/jira/browse/CAMEL-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7358: --- Assignee: Willem Jiang Tracer - Should have options to allow streams or files -- Key: CAMEL-7358 URL: https://issues.apache.org/jira/browse/CAMEL-7358 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Willem Jiang Priority: Minor Fix For: 2.14.0 So people can configure if the tracer should load the message body from streams or files, or not. Currently it will load the content into memory as a String. But we need options to turn this off by default for file / streams. And then people can turn these option on if they really want that See also http://camel.465427.n5.nabble.com/Java-heap-space-with-FILE-producer-and-larges-files-tp5749845.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7366) Error during commit: GenericFileOnCompletion
Arni Sumarlidason created CAMEL-7366:
Summary: Error during commit: GenericFileOnCompletion
Key: CAMEL-7366
URL: https://issues.apache.org/jira/browse/CAMEL-7366
Project: Camel
Issue Type: Bug
Affects Versions: 2.13.0
Environment: java 1.7.0_51
Reporter: Arni Sumarlidason
Files are lost when using a thread pool paradigm and the from(file://) source.
{code:title=Exception|borderStyle=solid}
[WARN ] [2014-04-14 11:00:28,812] [Camel (camel-1) thread #1 - seda://a]
[org.apache.camel.component.file.GenericFileOnCompletion]: Error during commit.
Exchange[66.json]. Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - Cannot
rename file: GenericFile[66.json] to: GenericFile[.camel/66.json]]
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
rename file: GenericFile[66.json] to: GenericFile[.camel/66.json]
at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:115)
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:88)
at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:124)
at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:80)
at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:54)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:100)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:228)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:613)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:581)
at
org.apache.camel.processor.CamelInternalProcessor$InternalCallback.done(CamelInternalProcessor.java:240)
at
org.apache.camel.processor.CamelInternalProcessor$InternalCallback.done(CamelInternalProcessor.java:251)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:429)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
at
org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:291)
at
org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:200)
at
org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:147)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{code}
Files that produced this message seemed to be deleted from disk.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968678#comment-13968678 ] Henryk Konsek commented on CAMEL-6999: -- Thanks Bilgin. I'll handle it. Camel component for dropbox integration --- Key: CAMEL-6999 URL: https://issues.apache.org/jira/browse/CAMEL-6999 Project: Camel Issue Type: New Feature Affects Versions: 2.12.1 Reporter: Giovanni Marigi Assignee: Henryk Konsek Priority: Minor Labels: camel, dropbox Fix For: Future Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-6999) Camel component for dropbox integration
[ https://issues.apache.org/jira/browse/CAMEL-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968681#comment-13968681 ] Henryk Konsek commented on CAMEL-6999: -- Giovanni, can you print, sign and fax the ICLA to the Apache? The procedure is described here (1). If you got any questions or problems, please let me know. (1) https://camel.apache.org/how-do-i-edit-the-website.html Camel component for dropbox integration --- Key: CAMEL-6999 URL: https://issues.apache.org/jira/browse/CAMEL-6999 Project: Camel Issue Type: New Feature Affects Versions: 2.12.1 Reporter: Giovanni Marigi Assignee: Henryk Konsek Priority: Minor Labels: camel, dropbox Fix For: Future Create a camel component (producers and consumers ) for dropbox integration -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7118) Hazelcast-based Recoverable Aggregation Repository
[ https://issues.apache.org/jira/browse/CAMEL-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13968842#comment-13968842 ] Alexander Lomov commented on CAMEL-7118: Updated pull request with a fix: https://github.com/apache/camel/pull/134 Hazelcast-based Recoverable Aggregation Repository -- Key: CAMEL-7118 URL: https://issues.apache.org/jira/browse/CAMEL-7118 Project: Camel Issue Type: New Feature Components: camel-hazelcast Environment: Any Reporter: Alexander Lomov Priority: Minor Labels: features Fix For: 2.13.1 This patch introduces HazelcastAggregationRepository class that implements RecoverableAggregationRepository and OptimisticLockingAggregationRepository. This class uses a Hazelcast distributed maps as a backing store for operational and persisted exchanges. This repository is aimed to support aggregation in an environment where multiple hosts run identical Camel routes which participate an aggregation process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7118) Hazelcast-based Recoverable Aggregation Repository
[ https://issues.apache.org/jira/browse/CAMEL-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7118: --- Assignee: Willem Jiang Hazelcast-based Recoverable Aggregation Repository -- Key: CAMEL-7118 URL: https://issues.apache.org/jira/browse/CAMEL-7118 Project: Camel Issue Type: New Feature Components: camel-hazelcast Environment: Any Reporter: Alexander Lomov Assignee: Willem Jiang Priority: Minor Labels: features Fix For: 2.13.1 This patch introduces HazelcastAggregationRepository class that implements RecoverableAggregationRepository and OptimisticLockingAggregationRepository. This class uses a Hazelcast distributed maps as a backing store for operational and persisted exchanges. This repository is aimed to support aggregation in an environment where multiple hosts run identical Camel routes which participate an aggregation process. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7324) DynamicRouter sends in-message to next destination
[ https://issues.apache.org/jira/browse/CAMEL-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7324. - Resolution: Fixed Fix Version/s: 2.14.0 2.13.1 2.12.4 Applied patch into master, camel-2.13.x and camel-2.12.x branches with thanks to Rene. DynamicRouter sends in-message to next destination -- Key: CAMEL-7324 URL: https://issues.apache.org/jira/browse/CAMEL-7324 Project: Camel Issue Type: Bug Components: camel-core Reporter: Rene Avontuur Assignee: Willem Jiang Fix For: 2.12.4, 2.13.1, 2.14.0 Attachments: AsyncEndpointDynamicRouterTest.java, DynamicRouterIntermediateResultIssueTest.java, patch7324-2.txt, patch7324.txt The DynamicRouter appears to send the in-message in stead of the out-message to the next destination, which is an unexpected behaviour. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CAMEL-7324) DynamicRouter sends in-message to next destination
[ https://issues.apache.org/jira/browse/CAMEL-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969173#comment-13969173 ] Willem Jiang edited comment on CAMEL-7324 at 4/15/14 3:17 AM: -- Applied patch into master, camel-2.13.x and camel-2.12.x branches with thanks to Rene. I also did some modification on the unit tests. was (Author: njiang): Applied patch into master, camel-2.13.x and camel-2.12.x branches with thanks to Rene. DynamicRouter sends in-message to next destination -- Key: CAMEL-7324 URL: https://issues.apache.org/jira/browse/CAMEL-7324 Project: Camel Issue Type: Bug Components: camel-core Reporter: Rene Avontuur Assignee: Willem Jiang Fix For: 2.12.4, 2.13.1, 2.14.0 Attachments: AsyncEndpointDynamicRouterTest.java, DynamicRouterIntermediateResultIssueTest.java, patch7324-2.txt, patch7324.txt The DynamicRouter appears to send the in-message in stead of the out-message to the next destination, which is an unexpected behaviour. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7335) Kafka : Expose kafka configuration properties to the camel component
[ https://issues.apache.org/jira/browse/CAMEL-7335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7335. - Resolution: Fixed Fix Version/s: 2.13.1 Kafka : Expose kafka configuration properties to the camel component Key: CAMEL-7335 URL: https://issues.apache.org/jira/browse/CAMEL-7335 Project: Camel Issue Type: Improvement Components: camel-kafka Affects Versions: 2.13.0 Reporter: Fabien Chaillou Assignee: Willem Jiang Labels: patch Fix For: 2.13.1, 2.14.0 Hello, Kafka provides a lot of property configurable for both consumer and producer (See http://kafka.apache.org/documentation.html#consumerconfigs and http://kafka.apache.org/documentation.html#producerconfigs). With this change, all this properties are exposed to the camel component. To do that, i splitted the configuration in its own class so that it is possible to create a separated configuration that can be reused. See the pull request on github : https://github.com/apache/camel/pull/126 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7350) JaxbDataFormat should not parse the Schema over and over again
[ https://issues.apache.org/jira/browse/CAMEL-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7350. - Resolution: Duplicate Fix Version/s: 2.14.0 2.13.1 2.12.4 JaxbDataFormat should not parse the Schema over and over again -- Key: CAMEL-7350 URL: https://issues.apache.org/jira/browse/CAMEL-7350 Project: Camel Issue Type: Improvement Components: camel-jaxb Affects Versions: 2.12.3, 2.13.0 Reporter: Sebastian Bösl Assignee: Willem Jiang Priority: Minor Labels: performance Fix For: 2.12.4, 2.13.1, 2.14.0 Attachments: AltJaxbDataFormat.zip Currently the createMarshaller and createUnmarshaller methods parse the javax.xml.validation.Schema from scratch, which is a severe overhead considering that a Schema instance is threadsafe and it is encuraged to re-use it as much as possible (see http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/validation/Schema.html) I extended the DataFormat and cached the parsed Schema and did a small benchmark that parsed an input document 64000 times: JaxbDataFormat: 3:18 AltJaxbDataFormat: 0:35 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7338) CxfClientCallback should not populate camel exchange OUT message if no response comes back to cxf producer and camel exchange pattern is InOnly
[
https://issues.apache.org/jira/browse/CAMEL-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-7338.
-
Resolution: Fixed
Fix Version/s: 2.14.0
2.13.1
2.12.4
Applied patch into camel master, camel-2.13.x and camel-2.12.x branches with
thanks to Joe.
CxfClientCallback should not populate camel exchange OUT message if no
response comes back to cxf producer and camel exchange pattern is InOnly
---
Key: CAMEL-7338
URL: https://issues.apache.org/jira/browse/CAMEL-7338
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.10.4
Reporter: Joe Luo
Assignee: Willem Jiang
Fix For: 2.12.4, 2.13.1, 2.14.0
Attachments: patch.txt
I have a following camel route:
{code}
String destination = cxf:http://localhost:9090/test?dataFormat=MESSAGE;;
from(jms:queue:dslSource)
.onException(java.net.ConnectException.class, Exception.class)
.maximumRedeliveries(3)
.maximumRedeliveryDelay(3000)
.retryAttemptedLogLevel(LoggingLevel.INFO)
.log(LoggingLevel.WARN, Failed to send message ${body})
.log(LoggingLevel.WARN, Sending message to the error queue:
${body}) // body is null here
.to(jms:queue:dslError)
.end()
.log(LoggingLevel.INFO, Sending message ...)
.setHeader(bridgeDestination, constant(destination))
.to(destination)
.log(LoggingLevel.INFO, received back: ${body})
.routeId(example-dsl);
{code}
If an exception is thrown, for instance, a ConnectionException due to
unavailability of the backend web service, the onException() route will be
executed. The first log endpoint:
{code}
.log(LoggingLevel.WARN, Failed to send message ${body})
{code}
prints out camel exchange IN message body without any problem. However, the
second log endpoint:
{code}
.log(LoggingLevel.WARN, Sending message to the error queue: ${body})
{code}
only prints out a null.
The reason is that when an exception is thrown, the
CxfClientCallback.handleException() is called:
{code}
public void handleException(MapString, Object ctx, Throwable ex) {
if (!boi.getOperationInfo().isOneWay()) {
// copy the InMessage header to OutMessage header
camelExchange.getOut().getHeaders().putAll(camelExchange.getIn().getHeaders());
binding.populateExchangeFromCxfResponse(camelExchange,
cxfExchange, ctx);
camelAsyncCallback.done(false);
}
...
{code}
and this line always populates camel exchange OUT message regardless whether
there is a CXF response back or not:
{code}
camelExchange.getOut().getHeaders().putAll(camelExchange.getIn().getHeaders());
{code}
Therefore, the second log endpoint within onException() block has it's camel
exchange IN message been overwritten and replaced with OUT message from
previous endpoint's although it is a message of NULL body.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CAMEL-7141) Custom HeaderFilterStrategy does not work when set it on either component or endpoint uri
[ https://issues.apache.org/jira/browse/CAMEL-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7141. - Resolution: Fixed Fix Version/s: (was: 2.12.3) (was: 2.13.0) 2.14.0 2.13.1 2.12.4 Custom HeaderFilterStrategy does not work when set it on either component or endpoint uri - Key: CAMEL-7141 URL: https://issues.apache.org/jira/browse/CAMEL-7141 Project: Camel Issue Type: Bug Components: camel-netty-http Affects Versions: 2.12.2 Reporter: Joe Luo Assignee: Willem Jiang Fix For: 2.12.4, 2.13.1, 2.14.0 Attachments: NettyHttpHeaderFilterBug.patch, revised_patch.txt Setting custom HeaderFilterStrategy on either NettyHttpComponent or NettyHttpEndpoint uri does not work. The only way to get it to work is to create a NettyHttpBinding bean and set the custom HeaderFilterStrategy as a property of the NettyHttpBinding bean and then set the custom NettyHttpBinding bean onto either NettyHttpComponent and NettyHttpEndpoint uri. The reason it does not work was that when applying the custom HeaderFilterStrategy, it is not set on NettyHttpBinding object as the NettyHttpBinding object always uses default HeaderFilterStrategy. I have attached the patch file. It might not be necessary to modify NettyHttpComponent class but I thought it'd be better to initialize configuration, nettyBinding and headerFilterStrategy in their getter method only when needed rather than in constructor of the NettyHttpComponent. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7366) Error during commit: GenericFileOnCompletion
[
https://issues.apache.org/jira/browse/CAMEL-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969179#comment-13969179
]
Willem Jiang commented on CAMEL-7366:
-
Hi Arni,
Can you submit a test case to help us for digging the issue?
Error during commit: GenericFileOnCompletion
Key: CAMEL-7366
URL: https://issues.apache.org/jira/browse/CAMEL-7366
Project: Camel
Issue Type: Bug
Affects Versions: 2.13.0
Environment: java 1.7.0_51
Reporter: Arni Sumarlidason
Labels: file, seda, threading
Files are lost when using a thread pool paradigm and the from(file://)
source.
{code:title=Exception|borderStyle=solid}
[WARN ] [2014-04-14 11:00:28,812] [Camel (camel-1) thread #1 - seda://a]
[org.apache.camel.component.file.GenericFileOnCompletion]: Error during
commit. Exchange[66.json]. Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - Cannot
rename file: GenericFile[66.json] to: GenericFile[.camel/66.json]]
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
rename file: GenericFile[66.json] to: GenericFile[.camel/66.json]
at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:115)
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:88)
at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:124)
at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:80)
at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:54)
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:100)
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:228)
at
org.apache.camel.util.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:613)
at
org.apache.camel.processor.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:581)
at
org.apache.camel.processor.CamelInternalProcessor$InternalCallback.done(CamelInternalProcessor.java:240)
at
org.apache.camel.processor.CamelInternalProcessor$InternalCallback.done(CamelInternalProcessor.java:251)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:429)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:191)
at
org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:291)
at
org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:200)
at
org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:147)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
{code}
Files that produced this message seemed to be deleted from disk.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CAMEL-7365) Camel versus Karaf versions
[ https://issues.apache.org/jira/browse/CAMEL-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7365: --- Assignee: Willem Jiang Camel versus Karaf versions --- Key: CAMEL-7365 URL: https://issues.apache.org/jira/browse/CAMEL-7365 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Assignee: Willem Jiang Priority: Minor Can page http://camel.apache.org/karaf.html be brought up to date? For example, I'd like to upgrade to Karaf 3.0.1 and it's not clear which version (or version range) would be suitable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7365) Camel versus Karaf versions
[ https://issues.apache.org/jira/browse/CAMEL-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13969197#comment-13969197 ] Willem Jiang commented on CAMEL-7365: - I just update the wiki page with last released Camel 2.13.0 which is using Karaf 2.3.3. Camel doesn't has the hard dependency on the specific Karaf version, the version just means we run the CI build with specific version of Karaf. Now we don't have plan to upgrade the Karaf version to 3.0.x, but you can try Camel 2.13.0 with the latest released Karaf 3.0.1. You just need to setup the camel feature version, then the Karaf can take care of it. Camel versus Karaf versions --- Key: CAMEL-7365 URL: https://issues.apache.org/jira/browse/CAMEL-7365 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Assignee: Willem Jiang Priority: Minor Can page http://camel.apache.org/karaf.html be brought up to date? For example, I'd like to upgrade to Karaf 3.0.1 and it's not clear which version (or version range) would be suitable. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7365) Camel versus Karaf versions
[ https://issues.apache.org/jira/browse/CAMEL-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-7365. - Resolution: Fixed Camel versus Karaf versions --- Key: CAMEL-7365 URL: https://issues.apache.org/jira/browse/CAMEL-7365 Project: Camel Issue Type: Improvement Components: documentation Reporter: Martin Lichtin Assignee: Willem Jiang Priority: Minor Can page http://camel.apache.org/karaf.html be brought up to date? For example, I'd like to upgrade to Karaf 3.0.1 and it's not clear which version (or version range) would be suitable. -- This message was sent by Atlassian JIRA (v6.2#6252)
