Thanks Karen! We will. I will have my teammate do it since he is actually
working on the issue and has the details
On Fri, Mar 11, 2022 at 10:32 AM Karen Lease
wrote:
> Hi Mark,
> This looks like a bug to me. During startup the AggregateProcessor first
> queries the exchange IDs in the table and
Hi Mark,
This looks like a bug to me. During startup the AggregateProcessor first
queries the exchange IDs in the table and then tries to read them using
the IDs. So if the exchange completes between these 2 queries, the
second select will return null.
The AggregateProcessor should check for a
FYI we tried using ClusterJDBCAggregationRepository, but we can’t use
because it requires instance_id.
Also, our organization does not have support for StatefulSet so we can't
use that.
On Thu, Mar 10, 2022 at 5:14 PM Mark Nuttall wrote:
> Sorry Claus, I should have included that. I was jumping
Sorry Claus, I should have included that. I was jumping back and forth on
multiple things :(
Camel 3.12.0 (using Java DSL)
Spring Boot 2.5.5
Java 11
Thank you!
On Thu, Mar 10, 2022 at 1:32 PM Claus Ibsen wrote:
> Hi
>
> What version of Camel do you use?
>
> On Thu, Mar 10, 2022 at 5:54 PM Mark
Hi
What version of Camel do you use?
On Thu, Mar 10, 2022 at 5:54 PM Mark Nuttall wrote:
>
> Has anyone successfully gotten JDBC Aggregation to work with K8s
> (Kubernetes)? We are struggling to make it work and maybe we are just
> missing something.
>
> Each instance (pod) gets a list of aggr
