[jira] [Updated] (CAMEL-5348) Uptime reported by Camel can be incorrect for values 1 day.
[ https://issues.apache.org/jira/browse/CAMEL-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-5348: --- Fix Version/s: 2.10.0 2.9.3 Uptime reported by Camel can be incorrect for values 1 day. - Key: CAMEL-5348 URL: https://issues.apache.org/jira/browse/CAMEL-5348 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.9.2 Reporter: Mark Waller Assignee: Willem Jiang Priority: Minor Fix For: 2.9.3, 2.10.0 Similar to issue KARAF-760 the context.getUptime() reports invalid durations - such as '19 days 54 hours'. Problem is in org/apache/camel/util/TimeUtils.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5338) Exchange.copy() should make a deep copy, if the referenced objects (body, headers, properties) implements java.lang.Cloneable
[ https://issues.apache.org/jira/browse/CAMEL-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292283#comment-13292283 ] Claus Ibsen commented on CAMEL-5338: If you read the effective java book (by Joshua Bloch), there is an item about clone. He basically says its broken and you should use it with care if you go down that road. The idea in Camel 2.x was to make end users deal with this, by the onPrepare callbacks. And besides the clone, you may need to do other work as well. What we could do in your line of idea, is to offer a pluggable SPI, where people can plugin a custom implementation that does the deep cloning. Mind that deep cloning is hard to do generic, as you would need to traverse list/maps, etc. and create new copies of them, and clone the values, and put them into the list, and so forth. With the pluggable SPI, it can be in line with the other functionality we have for that, documented at http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html Exchange.copy() should make a deep copy, if the referenced objects (body, headers, properties) implements java.lang.Cloneable - Key: CAMEL-5338 URL: https://issues.apache.org/jira/browse/CAMEL-5338 Project: Camel Issue Type: Improvement Affects Versions: 2.9.2 Reporter: Christian Müller Fix For: 3.0.0 We run into an issue where an exchange with a custom pojo as payload was sent to an multicast and changed in two different sub-routes at the same time (connected by using the direct protocol). The reason is that the Exchange.copy() method only creates shallow copies of the body (it's the same for the exchange properties and message headers). I think it's a good improvement to check whether the object implements java.lang.Cloneable and in this case create a deep copy of the object. [1] https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/DefaultExchange.java [2] https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/MessageSupport.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5309) Replies with Incorrect CorrelationIDs Received After Reinstantiating a Route with ActiveMQ Endpoint and Exclusive Reply Queue
[
https://issues.apache.org/jira/browse/CAMEL-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292288#comment-13292288
]
Vladimir Tsvetkov commented on CAMEL-5309:
--
I'm still reproducing the issue with 2.9-SNAPSHOT.
I expect 5 replies, but instead I receive 2 and 3 are with incorrect
correlation IDs:
{code}
2012-06-09 12:51:56,231 [Camel (camel-1) thread #13 -
PersistentQueueReplyManager[completionsQueue]-1] WARN
org.apache.camel.component.jms.reply.PersistentQueueReplyManager - Reply
received for unknown correlationID
[ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-507]. The
message will be ignored: ActiveMQTextMessage {commandId = 5, responseRequired =
true, messageId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:2:1:1:1,
originalDestination = null, originalTransactionId = null, producerId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:2:1:1,
destination = queue://completionsQueue, transactionId = null, expiration = 0,
timestamp = 1339235516008, arrival = 0, brokerInTime = 1339235516008,
brokerOutTime = 1339235516011, correlationId =
ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-507, replyTo =
queue://completionsQueue, persistent = true, type = null, priority = 4, groupID
= null, groupSequence = 0, targetConsumerId = null, compressed = false, userID
= null, content = null, marshalledProperties =
org.apache.activemq.util.ByteSequence@300eff0c, dataStructure = null,
redeliveryCounter = 0, size = 1248, properties =
{breadcrumbId=ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-500,
CamelJmsDeliveryMode=2, taskType=processIndexTask}, readOnlyProperties = true,
readOnlyBody = true, droppable = false, text =
{fiscalYear:2011,indexCompression:ZIP,...quarter:3}}
2012-06-09 13:06:29,605 [Camel (camel-1) thread #33 - Threads] INFO
PROCESS_INDICES_STATE.RESPONSE - Exchange[ExchangePattern:InOut,
BodyType:String,
Body:{fiscalYear:2011,indexCompression:ZIP,indexType:COMPANY,quarter:4}]
2012-06-09 13:16:48,811 [Camel (camel-1) thread #13 -
PersistentQueueReplyManager[completionsQueue]-1] WARN
org.apache.camel.component.jms.reply.PersistentQueueReplyManager - Reply
received for unknown correlationID
[ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-506]. The
message will be ignored: ActiveMQTextMessage {commandId = 5, responseRequired =
true, messageId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:4:1:1:1,
originalDestination = null, originalTransactionId = null, producerId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:4:1:1,
destination = queue://completionsQueue, transactionId = null, expiration = 0,
timestamp = 1339237008806, arrival = 0, brokerInTime = 1339237008806,
brokerOutTime = 1339237008809, correlationId =
ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-506, replyTo =
queue://completionsQueue, persistent = true, type = null, priority = 4, groupID
= null, groupSequence = 0, targetConsumerId = null, compressed = false, userID
= null, content = null, marshalledProperties =
org.apache.activemq.util.ByteSequence@482163cd, dataStructure = null,
redeliveryCounter = 0, size = 1248, properties =
{breadcrumbId=ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-500,
CamelJmsDeliveryMode=2, taskType=processIndexTask}, readOnlyProperties = true,
readOnlyBody = true, droppable = false, text =
{fiscalYear:2011,indexCompression:ZIP,...quarter:2}}
2012-06-09 13:27:39,280 [Camel (camel-1) thread #34 - Threads] INFO
PROCESS_INDICES_STATE.RESPONSE - Exchange[ExchangePattern:InOut,
BodyType:String,
Body:{fiscalYear:2012,indexCompression:ZIP,indexType:COMPANY,quarter:1}]
2012-06-09 13:28:15,364 [Camel (camel-1) thread #13 -
PersistentQueueReplyManager[completionsQueue]-1] WARN
org.apache.camel.component.jms.reply.PersistentQueueReplyManager - Reply
received for unknown correlationID
[ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-508]. The
message will be ignored: ActiveMQTextMessage {commandId = 5, responseRequired =
true, messageId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:6:1:1:1,
originalDestination = null, originalTransactionId = null, producerId =
ID:Vladimir-Tsvetkovs-MacBook-Pro.local-57252-1339232410422-1:6:1:1,
destination = queue://completionsQueue, transactionId = null, expiration = 0,
timestamp = 1339237695326, arrival = 0, brokerInTime = 1339237695327,
brokerOutTime = 1339237695328, correlationId =
ID-Vladimir-Tsvetkovs-MacBook-Pro-local-57270-1339232420004-0-508, replyTo =
queue://completionsQueue, persistent = true, type = null, priority = 4, groupID
= null, groupSequence = 0, targetConsumerId = null, compressed = false, userID
= null, content = null, marshalledProperties =
org.apache.activemq.util.ByteSequence@bd53277, dataStructure = null,
redeliveryCounter
[jira] [Commented] (CAMEL-5325) camel-cxf-transport build failed using system encoding
[ https://issues.apache.org/jira/browse/CAMEL-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292292#comment-13292292 ] Liu Jianhong commented on CAMEL-5325: - Ok,already filled , the Jira address is https://issues.apache.org/jira/browse/CXF-4369 camel-cxf-transport build failed using system encoding -- Key: CAMEL-5325 URL: https://issues.apache.org/jira/browse/CAMEL-5325 Project: Camel Issue Type: Task Components: build system, camel-cxf, camel-jmx, camel-soap Environment: Windows 7 with chinese language camel 2.10-SNAPSHOT Reporter: Liu Jianhong Assignee: Willem Jiang Priority: Minor Fix For: 2.10.0 Attachments: pom.xml This bug is fixed as https://issues.apache.org/jira/browse/CXF-2450;, by adding forkalways/fork additionalJvmArgs-Duser.language=en/additionalJvmArgs to cxf-codegen-plugin's configuration section. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5349) camel-test - Make it easy to provider override properties from unit tests
Claus Ibsen created CAMEL-5349: -- Summary: camel-test - Make it easy to provider override properties from unit tests Key: CAMEL-5349 URL: https://issues.apache.org/jira/browse/CAMEL-5349 Project: Camel Issue Type: New Feature Components: camel-blueprint, camel-test Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.10.0 When unit testing you may use properties from osgi config admin, or external resources and whatnot. We should make it easier to provide a java.util.Properties from the unit test source code. See nabble http://camel.465427.n5.nabble.com/Overwrite-blueprint-properties-in-camel-blueprint-tests-tp5710948.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5349) camel-test - Make it easy to provider override properties from unit tests
[ https://issues.apache.org/jira/browse/CAMEL-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-5349. Resolution: Fixed Updated docs. See the using property placeholder docs for details. camel-test - Make it easy to provider override properties from unit tests - Key: CAMEL-5349 URL: https://issues.apache.org/jira/browse/CAMEL-5349 Project: Camel Issue Type: New Feature Components: camel-blueprint, camel-test Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.10.0 When unit testing you may use properties from osgi config admin, or external resources and whatnot. We should make it easier to provide a java.util.Properties from the unit test source code. See nabble http://camel.465427.n5.nabble.com/Overwrite-blueprint-properties-in-camel-blueprint-tests-tp5710948.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4855) Add wiki page for camel-mina2 component
[ https://issues.apache.org/jira/browse/CAMEL-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292337#comment-13292337 ] Claus Ibsen commented on CAMEL-4855: lets keep camel-mina2 in progress, so we have time to make those improvements we want, before putting out docs and whatnot. So pushing this for Camel 2.11 Add wiki page for camel-mina2 component --- Key: CAMEL-4855 URL: https://issues.apache.org/jira/browse/CAMEL-4855 Project: Camel Issue Type: Sub-task Components: camel-mina2 Reporter: Chad Beaulac Fix For: 2.11 Checkout the instructions here: http://camel.apache.org/add-new-component-guide.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5346) camel-solr feature missing the bundle for http4 client
[ https://issues.apache.org/jira/browse/CAMEL-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-5346. Resolution: Fixed camel-solr feature missing the bundle for http4 client -- Key: CAMEL-5346 URL: https://issues.apache.org/jira/browse/CAMEL-5346 Project: Camel Issue Type: Bug Components: karaf Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.10.0 Just found the solr bundle is the dependencies of http4 client by running the validation on the apache-camel feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5345) Removed the unused jaxws bundles from camel-hdfs
[ https://issues.apache.org/jira/browse/CAMEL-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-5345. Resolution: Fixed Removed the unused jaxws bundles from camel-hdfs Key: CAMEL-5345 URL: https://issues.apache.org/jira/browse/CAMEL-5345 Project: Camel Issue Type: Task Components: karaf Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.10.0 When upgrade the hadoop-core to 1.0, the code just use the jaxrs interface for management and doesn't need the jaxws api any more. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5311) Spring Batch component
[ https://issues.apache.org/jira/browse/CAMEL-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-5311. Resolution: Fixed Initial docs added. Fell free to improve in the future. Spring Batch component -- Key: CAMEL-5311 URL: https://issues.apache.org/jira/browse/CAMEL-5311 Project: Camel Issue Type: New Feature Affects Versions: 2.10.0 Reporter: Henryk Konsek Assignee: Henryk Konsek Fix For: 2.10.0 Attachments: camel-spring-batch-patch-2.txt, spring-batch.patch I'm attaching completed Spring Batch Component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5225) camel-netty can't distinguish between Sharable and Unsharable codecs
[
https://issues.apache.org/jira/browse/CAMEL-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292466#comment-13292466
]
edge wang commented on CAMEL-5225:
--
Would you please adopt my revised UnsharableCodecsConflictsTest.java and run
the test? I only saw the code somewhat reverted to version 2.9.1, but didn't
solve the problem I reported. The problem exists as long as you use code like
this(DefaultServerPipelineFactory.java):
ListChannelUpstreamHandler decoders =
consumer.getConfiguration().getDecoders();
for (int x = 0; x decoders.size(); x++) {
channelPipeline.addLast(decoder- + x, decoders.get(x));
}
this configuration model causes the decoders(created and cached in
consumer.getConfiguration().getDecoders()) to be shared among pinelines and
then lead to conflicts on stateful codecs.
camel-netty can't distinguish between Sharable and Unsharable codecs
Key: CAMEL-5225
URL: https://issues.apache.org/jira/browse/CAMEL-5225
Project: Camel
Issue Type: Bug
Components: camel-netty
Affects Versions: 2.9.2
Environment: ALL
Reporter: edge wang
Assignee: Claus Ibsen
Labels: netty
Fix For: 2.9.3, 2.10.0
Attachments: DefaultServerPipelineFactory.java.patch,
UnsharableCodecsConflictsTest.java, UnsharableCodecsConflictsTest.java
Camel-netty uses general configuration model for referenced encoders/decoders
for channel pipelines, see DefaultServerPipelineFactory. That is, create
encoder/decoder objects at configuration parsing time and store them in a
list, then use them when a pipeline is established. However, this will make
encoder/decoder objects shared among different pipelines, that may cause data
conflicts, when the encoder/decoder is not Sharable(has object status/not
annotated as @Sharable), e.g. a LengthFieldBasedFrameDecoder.
Although we can avoid the problem by totally writing a new
serverpipelinefactory for our apps, several problem still remains, please see
detailed description and testcase for this bug at:
http://camel.465427.n5.nabble.com/camel-netty-bug-and-the-need-of-best-practice-for-creating-referenced-parameter-object-on-looking-up-td5627926.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
