Why does JPA batch update rollback transaction on single record failure?

We're using the following to aggregate messages containing objects bound for JPA/Hibernate endpoint. The problem we have is managing failures; if a single record fails, the entire batch rolls back, and it's difficult to identify which record actually failed. Would be nice if BatchUpdateException w

Re: Combining TimeoutAwareAggregationStrategy and AbstractListAggregationStrategy

Thank you for the reply and the suggestion, although I was hoping for ideas about a Java implementation. I generally use the Java DSL, since I don't prefer XML. However, I ended up using FlexibleAggregationStrategy which is pretty cool. On Sat, Jul 2, 2016 at 8:40 PM, raffi wrote: > Try this;

Help with Topology

Hi, I am using a Trident topology to process files, transform them from CSV, EDI, XML to a general JSON format. I have a working prototype, but wanted to make sure I am implementing this correctly. Here is the flow 1. Read message from kafka, this message is meta data of the file location on S3

Re: Default ThreadPool Role in camel 2.16.1

On Sun, Jul 3, 2016 at 12:35 PM, Debraj Manna wrote: > Thanks for the pointers. > > If I have a route of the form > > from("direct:setStatusToReadyToShip").to("bean:orderHelper?method=setStatusToReadyToShip") > > Then the route from from(...).to(...) will be effected by > defaultThreadProfile? >

Re: Default ThreadPool Role in camel 2.16.1

Thanks for the pointers. If I have a route of the form from("direct:setStatusToReadyToShip").to("bean:orderHelper?method=setStatusToReadyToShip") Then the route from from(...).to(...) will be effected by defaultThreadProfile? On Jul 3, 2016 3:39 PM, "Claus Ibsen" wrote: > Hi > > > No Jetty ha

Re: Default ThreadPool Role in camel 2.16.1

Hi No Jetty has its own thread pooling, and you need to configure it using options on the jetty component http://camel.apache.org/jetty The thread pools in Camel is when you configure an explicit thread pool on a component that is of ExecutorService type. And also for all the EIPs that has threa

Default ThreadPool Role in camel 2.16.1

Can some please explain me how does threadPool works in camel? Let's say I have a default threadPool defined in camelContext:- Also let's say I have some routes defined as below:- from("jetty:http://localhost:/orchestratorservice";).process(processor); from("direct:setStatusToReadyToShip"