Re: [VOTE] Release Apache Camel 2.12.5
+1 On Thu, Oct 23, 2014 at 10:24 PM, Matteo Cusmai cusmaimat...@gmail.com wrote: +1 On 23 Oct 2014 19:42, Jean-Baptiste Onofré j...@nanthrax.net wrote: +1 (non binding) Regards JB Sent from my Samsung Galaxy smartphone. Original message From: seij...@gmail.com Date:23/10/2014 18:30 (GMT+01:00) To: d...@camel.apache.org Cc: priv...@camel.apache.org, d...@camel.apache.org, users@camel.apache.org Subject: Re: [VOTE] Release Apache Camel 2.12.5 +1 Johan Edstrom jedst...@savoirtech.com Phone (Cell) : +1 303 999 7535 On Thu, Oct 23, 2014 at 9:09 AM, akarpe akarpe_2...@yahoo.com wrote: +1 On Oct 23, 2014, at 12:14 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1017 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1017/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling
Do you have a use case that we could use to reproduce the issue ? On Thu, Oct 23, 2014 at 10:08 PM, BlackTie jts...@hotmail.com wrote: I tried configuring the JMX agent with registerAlways=true and that didn't make a difference. Still thinking about the transacted routes not being registered at the processor level in JMX, I removed the transacted method from the route builder for one of the routes that didn't have the detailed processor statistics and redeployed. Hawtio now shows processor statistics for that particular route. Something regarding or in conjunction with the transactions is stopping the processors from being registered by the agent. Can you think of any reason why transacting the routes would cause this JMX issue? Some information regarding our transaction config: * using Spring's JmsTransactionManager * using Spring's CachingConnectionFactory with the transaction manager * using Camel's SpringTransactionPolicy beans with the transaction manager * using ActiveMQ 5.10.0 * ActiveMQ Camel component's JMS config has transacted=true -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5757959.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
[CANCEL][VOTE] Release Apache Camel 2.12.5
-1 As I wrote earlier, this VOTE is cancelt because the Nexus repository doesn't contain the binary nor the source distributions. A new release candidate is in progress and will be available for test later today. Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member On Thu, Oct 23, 2014 at 7:14 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1017 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1017/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian
Re: [VOTE] Release Apache Camel 2.12.5
+1
On Fri, Oct 24, 2014 at 8:07 AM, Charles Moulliard ch0...@gmail.com wrote:
+1
On Thu, Oct 23, 2014 at 10:24 PM, Matteo Cusmai cusmaimat...@gmail.com
wrote:
+1
On 23 Oct 2014 19:42, Jean-Baptiste Onofré j...@nanthrax.net wrote:
+1 (non binding)
Regards
JB
Sent from my Samsung Galaxy smartphone.
Original message
From: seij...@gmail.com
Date:23/10/2014 18:30 (GMT+01:00)
To: d...@camel.apache.org
Cc: priv...@camel.apache.org, d...@camel.apache.org,
users@camel.apache.org
Subject: Re: [VOTE] Release Apache Camel 2.12.5
+1
Johan Edstrom
jedst...@savoirtech.com
Phone (Cell) : +1 303 999 7535
On Thu, Oct 23, 2014 at 9:09 AM, akarpe akarpe_2...@yahoo.com wrote:
+1
On Oct 23, 2014, at 12:14 AM, Christian Müller
christian.muel...@gmail.com wrote:
This is a vote to release Apache Camel 2.12.5, a patch release
coming
with
about 74 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166
Staging repo:
https://repository.apache.org/content/repositories/orgapachecamel-1017
Tarballs:
https://repository.apache.org/content/repositories/orgapachecamel-1017/org/apache/camel/apache-camel/2.12.5/
Tag:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58
Please test this release candidate and cast your vote.
[ ] +1 Release the binary as Apache Camel 2.12.3
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks,
Christian
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Re: [VOTE] Release Apache Camel 2.12.5
+1 On 24 October 2014 13:11, Alexandros Koufoudakis akoufouda...@gmail.com wrote: +1 On Fri, Oct 24, 2014 at 8:07 AM, Charles Moulliard ch0...@gmail.com wrote: +1 On Thu, Oct 23, 2014 at 10:24 PM, Matteo Cusmai cusmaimat...@gmail.com wrote: +1 On 23 Oct 2014 19:42, Jean-Baptiste Onofré j...@nanthrax.net wrote: +1 (non binding) Regards JB Sent from my Samsung Galaxy smartphone. Original message From: seij...@gmail.com Date:23/10/2014 18:30 (GMT+01:00) To: d...@camel.apache.org Cc: priv...@camel.apache.org, d...@camel.apache.org, users@camel.apache.org Subject: Re: [VOTE] Release Apache Camel 2.12.5 +1 Johan Edstrom jedst...@savoirtech.com Phone (Cell) : +1 303 999 7535 On Thu, Oct 23, 2014 at 9:09 AM, akarpe akarpe_2...@yahoo.com wrote: +1 On Oct 23, 2014, at 12:14 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1017 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1017/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io -- Jinesh M.K / Technical Lead Mobile:9400466629/ Office: 04762804530 Center for Cyber Security Amrita Vishwa Vidyapeetham, Kerala,India
Re: REST marshal gson with custom Exclustion Strategy
I am going to answer this one myself. As it is you cannot use content from the Exchange message to manipulate the Gson marshalling. At least not using the built in GsonDataFormat. You need to roll your own dataformat and use that. I guess that is fair enough :) -- View this message in context: http://camel.465427.n5.nabble.com/REST-marshal-gson-with-custom-Exclustion-Strategy-tp5757941p5757980.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: disableTimeToLive property ignored
I think that you have to remove the requestTimeout=5s. I think you can't mix requestTimeout with disableTimeToLive to true to(ExchangePattern.InOut, activemq:queue:ValidationInQueue?replyTo=PaymentsOutQueuereplyToType=ExclusivedisableTimeToLive=true) Regards -- View this message in context: http://camel.465427.n5.nabble.com/disableTimeToLive-property-ignored-tp5757977p5757987.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Web service SOAP fault handling
Here's how we generate a SOAP Fault:
public void process(Exchange exchange) throws Exception
{
// Setup the SOAP fault
SoapFault fault = buildFault(exchange);
fault.setFaultCode(Soap11.getInstance().getSender());
//B2BException_Exception fault = buildFault(exchange);
exchange.getOut().setHeaders(exchange.getIn().getHeaders());
exchange.getOut().setBody(fault);
exchange.getOut().setFault(true);
}
Cheers
@a_bouchama
--
View this message in context:
http://camel.465427.n5.nabble.com/Web-service-SOAP-fault-handling-tp5757883p5757988.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: disableTimeToLive property ignored
I can do that regarding to the camel docs. http://camel.apache.org/jms.html, section About time to live: /So the two options requestTimeout and disableTimeToLive gives you fine grained control when doing request/reply. / -- View this message in context: http://camel.465427.n5.nabble.com/disableTimeToLive-property-ignored-tp5757977p5757989.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: calling a REST Service POST method with parameters from another REST Service
Guys, This has been resolved following the below link. http://camel.465427.n5.nabble.com/HTTP-Post-component-parameters-td4937377.html Hope helps others as well, Thanks, Sayed -- View this message in context: http://camel.465427.n5.nabble.com/calling-a-REST-Service-POST-method-with-parameters-from-another-REST-Service-tp5757939p5757991.html Sent from the Camel - Users mailing list archive at Nabble.com.
[VOTE] Release Apache Camel 2.12.5 - second try
This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1020 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1020/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian
Re: [VOTE] Release Apache Camel 2.12.5 - second try
+1 Jeff On Oct 24, 2014, at 9:17 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1020 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1020/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian
Re: [VOTE] Release Apache Camel 2.12.5 - second try
+1 On Oct 24, 2014, at 10:17 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1020 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1020/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian
Re: [VOTE] Release Apache Camel 2.12.5 - second try
+1 Johan Edstrom jedst...@savoirtech.com Phone (Cell) : +1 303 999 7535 On Fri, Oct 24, 2014 at 9:24 AM, Jeff Genender jgenen...@apache.org wrote: +1 Jeff On Oct 24, 2014, at 9:17 AM, Christian Müller christian.muel...@gmail.com wrote: This is a vote to release Apache Camel 2.12.5, a patch release coming with about 74 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211version=12327166 Staging repo: https://repository.apache.org/content/repositories/orgapachecamel-1020 Tarballs: https://repository.apache.org/content/repositories/orgapachecamel-1020/org/apache/camel/apache-camel/2.12.5/ Tag: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=42850495b5a53878ceb1aec40f57b0b636e96e58 Please test this release candidate and cast your vote. [ ] +1 Release the binary as Apache Camel 2.12.3 [ ] -1 Veto the release (provide specific comments) Vote is open for at least 72 hours. Thanks, Christian
Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling
I don't have a small project that reproduces the issue, just the large app I'm performance-tuning now. I'm willing to try anything you recommend to figure out exactly what's wrong. I have a feeling that if I created a smaller project to mock this problem, I wouldn't be able to reproduce it. :) The interesting thing to note is that all the routes work as expected, the transactional error handler works to retry errors according to the policies we have set. The only indication that something isn't right with these transacted routes is that no statistics get recorded for the processors of those routes in JMX. Charles Moulliard-2 wrote Do you have a use case that we could use to reproduce the issue ? -- View this message in context: http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tp5757634p5758000.html Sent from the Camel - Users mailing list archive at Nabble.com.
read only file source has updated files with the same name
I have a readonly source for a file consumer so I'm using noop true which gets me idempotent in memory store. However sometimes they will redrop an update with the same name. Please direct me to how to modify the idempotent store to account for filename and timestamp. Or is there a better way? String fileUri = file: + srcPath+?startingDirectoryMustExist=true + readLock=changed + readLockCheckInterval=5000 + readLockMarkerFile=false + filter=#hoursFileFilter + delay= + delay + include=+include + noop=true; thanks, Rachel -- View this message in context: http://camel.465427.n5.nabble.com/read-only-file-source-has-updated-files-with-the-same-name-tp5758001.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel JMS message topic handling
As there is only 1 thread where a JMS Consumer is active (to avoid duplicate msg processing), isn't it normal that messages get lost in this scenario ? When that thread is busy processing a message (DefaultJmsMessageListenerContainer(AbstractPollingMessageListenerContainer).doReceiveAndExecute), any message that comes while this JMSConsumer is active will be lost, as this thread will close the message consumer when it's done. Having multiple active consumers would not help and would even make matters worse , as you would need to deal with duplicate messages. In what use-case would a basic (non-virtual) activeMQ topic combined with a single JMS consumer make sense ? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5758004.html Sent from the Camel - Users mailing list archive at Nabble.com.
Change property in unit test
Hello All, I have a unit test and I want to change a camel property. I am only a single version of the configuration file to test against so I would like to change the property in code. For example, I thought I could do something like this: context.getProperties().put(myProperty, false); However, that didn't do it. I see that I can resolve a property like this: context.resolvePropertyPlaceholders(property); However it doesn't look like I can change its value. Is there a way to dynamically change a property in a Camel Context unit test? Thanks, Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/Change-property-in-unit-test-tp5758017.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel JMS message topic handling
I’m not sure how it all works internally but consumers on topics do not lose incoming messages while it is busy processing one message. That would break the rule of JMS guaranteed message delivery. I’ve had a number of projects using a topic with only one consumer on it. Normally the topic is chosen because we need to broadcast the message out and currently there’s only one interested subscriber but potentially we could add more in the future. Perfectly valid use case. On 25 Oct 2014, at 7:32 am, ddewaele ddewa...@gmail.com wrote: As there is only 1 thread where a JMS Consumer is active (to avoid duplicate msg processing), isn't it normal that messages get lost in this scenario ? When that thread is busy processing a message (DefaultJmsMessageListenerContainer(AbstractPollingMessageListenerContainer).doReceiveAndExecute), any message that comes while this JMSConsumer is active will be lost, as this thread will close the message consumer when it's done. Having multiple active consumers would not help and would even make matters worse , as you would need to deal with duplicate messages. In what use-case would a basic (non-virtual) activeMQ topic combined with a single JMS consumer make sense ? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JMS-message-topic-handling-tp5757853p5758004.html Sent from the Camel - Users mailing list archive at Nabble.com.
