cxf rs deadlock waiting for response

Hi There seems to be a problem doing a POST to a rest service that that returns http 202 with an empty body resulting in a inflight exchange that never completes (deadlock). btw the service response content-length header is set to 0 The lock is in -> at

Re: Camel zero routes started upon startup of context

One issue with this is that it also seems to mess with mdc looking in Karaf.. On Wed, Nov 2, 2016 at 10:54 PM, Souciance Eqdam Rashti < souciance.eqdam.ras...@gmail.com> wrote: > Gmail is not the best formatter but here it is..you can probably put it in > notepad++ for better highlighting.. > >

Re: netty4(-http) producer workerGroup and producerPool

Hi, I just checked the code of camel-netty4, the workerGroup can be share between the consumers and producers if the option is specified otherwise camel creates a new workerGroup per consumer or producer. The wiki doc is updated, I will commit a quick fix to the camel netty component. --

Re: cxf rs deadlock waiting for response

I debugged a bit to get closer. The root problem is in org.apache.cxf.jaxrs.client.AbstractClient as the threaddump shows the block in line 564 gets activated if (ex == null && !exchange.isOneWay()) { synchronized (exchange) { while

Re: Question on multicast to pipelines

HI, I created a jira (CAMEL-10442) for this in case it’s a bug. Thanks for your help. Best, Edoado > On 1 Nov 2016, at 19:30, Brad Johnson wrote: > > Edoardo, > > I missed the second set of logging statements, sorry. I thought you'd said > they were

MongoDB / findById and ObjectId (issue in 2.18)

Hi All, When using Camel MongoDB component with "operation=findById" and [_id] field is happened to be a standard ObjectId(), it doesn't work anymore in v.2.18 (worked 2.17.3 and before). Basically, to test you'd need to send org.bson.types.ObjectId in the message body but it never finds a

MongoDB component returning header "CamelMongoDbRecordsAffected" (2.18)

I wonder if returning headers, like "CamelMongoDbRecordsAffected" (MongoDbConstants.RECORDS_AFFECTED) will be re-introduced again in the future release of the component or it's gone for good. It's still documented as available feature and bringing it back is often just a couple of lines of code

Re: MongoDB / findById and ObjectId (issue in 2.18)

You're welcome to fill a JIRA for this if you think this is a bug. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, November 3, 2016

Re: MongoDB component returning header "CamelMongoDbRecordsAffected" (2.18)

You're welcome to raise a JIRA for this as a feature request. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, November 3, 2016 11:57 AM,

Re: Camel zero routes started upon startup of context

The blueprint looks OK to me - at least nothing jumps out at me. One question though - you have a lot more beans defined than are referenced - what are they for? Are they Camel routes? Or just supporting beans that the other routes use? I see in the log snippet that some Camel routes are

Re: cxf rs deadlock waiting for response

Hi You are right, it is a new code which was added to avoid some synchronization issues in case of the async client invocations. FYI, the existing CXF RS oneway tests still work with this code but only because the client does set a oneway CXF exchange status before the invocation, in case

Possible to use nested properties with both spring and camel property placeholders?

Hi, I have a Camel project that uses Spring XML, with various settings in a separate settings.properties file. And these settings are used both in plain Spring XML (like arguments to java beans) and in Camel specific configuration (like endpoint URI). Here is the part of my camel-context.xml

Re: cxf rs deadlock waiting for response

Thanks Sergey :-) I think the link should be https://issues.apache.org/jira/browse/CXF-7123 Cheers /Preben -- View this message in context: http://camel.465427.n5.nabble.com/cxf-rs-deadlock-waiting-for-response-tp5789687p5789708.html Sent from the Camel - Users mailing list archive at

Re: MongoDB component returning header "CamelMongoDbRecordsAffected" (2.18)

CAMEL-10444 -- View this message in context: http://camel.465427.n5.nabble.com/MongoDB-component-returning-header-CamelMongoDbRecordsAffected-2-18-tp5789686p5789706.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: MongoDB / findById and ObjectId (issue in 2.18)

CAMEL-10443 -- View this message in context: http://camel.465427.n5.nabble.com/MongoDB-findById-and-ObjectId-issue-in-2-18-tp5789685p5789703.html Sent from the Camel - Users mailing list archive at Nabble.com.

Evaluating Learning and Performance of Developers in Open Source Software Projects.

Hi, We, ManiTeja Chodapaneedi and Samhith Manda, two master students in Software Engineering at BTH are carrying out a Masters thesis on identifying developer performance in Open Source Projects and also identifying different challenges they face during their early stages in the project. Hence,

Re: cxf rs deadlock waiting for response

Oops :-), sorry. CXF-7123 has now been fixed Cheers, Sergey On 03/11/16 13:36, Preben.Asmussen wrote: Thanks Sergey :-) I think the link should be https://issues.apache.org/jira/browse/CXF-7123 Cheers /Preben -- View this message in context:

Testing CDI Route

Hello camel experts, I'm using camel inside of wildfly swarm application and having trouble to create a working test with CamelCdiRunner. I've followed the example from camel documentation but the test I've created fails with the error: java.lang.NullPointerException at

Re: Testing CDI Route

Hi Oli, CamelCdiRunner bootstraps a Weld SE container so that you can easily test your Camel CDI code with a bare minimal CDI container. If you want to test your Camel CDI code with WildFly Swarm, you may need to rely on Arquillian or what WildFly Swarm provides as testing framework. You may

Best way to build a wait/retry loop with Camel?

Hi Camel users TLDR: - how to implement wait/retry loop? - messages "wait" in a queue - each message should be reprocessed only once per interval (let's say per day) - after reprocessing a message either returns to the waiting queue or continues (goes out of loop) - after [maxRetry] attempts it

Re: Testing CDI Route

Hi Antonin, in other words, CamelCdiRunner would do the job? Why it doesn't work for me? The test class: @RunWith(CamelCdiRunner.class) @Beans(classes = Route.class) public class RouteTest { void advice( @Observes CamelContextStartingEvent event, @Uri("mock:test")

Re: Testing CDI Route

Hi Oli, Indeed, your test class should work. However, it seems the WildFly Swarm plugin generates some other classes, like org.wildfly.swarm.cdi.StageConfigBean, that are deployed as bean classes and that seems to require some execution context. The CamelCdiRunner starts a Weld SE container

Enrich headers of message

Hi there, I will start off by describing what I am willing to accomplish. I need to process a file line by line, pluck out a field from each file record, make two rest api calls, the first one to get a json web token, the second one use the token from the first api call in the header and return

AW: Enrich headers of message

Yes. A Message contains properties and IN and OUT parts consisting each of header values and the body. Jan > -Ursprüngliche Nachricht- > Von: lsantos [mailto:leandro.bu...@globo.com] > Gesendet: Donnerstag, 3. November 2016 18:09 > An: users@camel.apache.org > Betreff: Enrich headers of

Re: Best way to build a wait/retry loop with Camel?

On number 3, you might add a timestamp in millis in addition to the max retries. When you pull the object off the queue do a quick addition of the timestamp on the object (or header) and the number of millis in a day. The current time in millis should exceed that number or a day has not passed

Re: Best way to build a wait/retry loop with Camel?

PS putting the timestamp in millis in place would also let you fire up the route on a regular basis, every 5 minutes, hour, 8 hours or day. It wouldn't matter. In all cases the first thing it does is add the number of millis in a day to the timestamp and ensuring that the current time in millis

Re: Enrich headers of message

I think all you are wanting to do is save the file record (body) to your own header called, say, filebody, then you can restore filebody header to the exchange body at the end for the out. In the meantime you can do the enrich with the setBody to some data from header.filebody In summary, your

Re: Best way to build a wait/retry loop with Camel?

Just be careful of using the Active MQ delay since unless you clean this header up, it propagates to every subsequent queue. Quite difficult to debug! -- View this message in context: http://camel.465427.n5.nabble.com/Best-way-to-build-a-wait-retry-loop-with-Camel-tp5789712p5789722.html Sent

Re: Best way to build a wait/retry loop with Camel?

Owain, That's why my preference would be to use the chron job he mentioned and just check my own timestamp in millis in a header or even putting the items in a map and putting that on the queue. The map would have number of retries, timestamp, and the actual data model he's working with. That

Split, aggregate, then wait for completionTimeout before continuing

Hello, I have a simple use case where I'd like to do the following: * split a message and process each part * aggregate parts into groups of size N for group-processing (w/timeout to ensure no parts are lost) * continue route ONLY after all aggregated parts have completed The simplified route

Re: Possible to use nested properties with both spring and camel property placeholders?

It looks like you are using the Spring and Camel Properties component together. Camel support the {{}} syntax out of box , so you just need to find a way to let the spring bean too support :)   -- Willem Jiang Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese)