example-spring | An example on how to integrate JobRunr with Spring | Model View Controller library

It's not possible to run the ignitevisorcmd from the same pod in the Kubernetes that runs the ignite service node, because the TcpDiscoveryKubernetesIpFinder can't be used with different discovery ports (From the javadocs: Make sure that all Ignite pods occupy a similar discovery port, otherwise they will not be able to discover each other using this IP finder.). The discovery port is already used by the ignite server, so the visor can only be run as a separate pod.

Also the library ignite-kubernetes should be installed in order to use ignite visor:

Uh oh, as mentioned in the comments, take care with the Level DB stuff since it is deprecated. Only use it if you have tested it thoroughly! In our tests, it was running quite nice. But when the level DB was, for whatever reason, corrupted, the data was lost. We were never able to restore a Level DB. Not very nice for production.

And don't even think about NFS based solutions. NFS is really not suited for this, we had a lot of issues in our tests. We often managed it for example to have multiple masters or no masters at all. So we gave it up.

In the end we are using a plain single broker because the complexity of solving issues in master/slave or replication setups can be quite high. And we had almost never any unplanned downtimes despite our "single point of failure".

However, a bunch of people told me that a network of brokers works quite well to have a redundant setup. At least one of them was talking about a really big environment.

Well, this is not really an answer to your question, isn't it?

You can put Camel routes beside the broker XML configuration and these routes then run inside the ActiveMQ process. See here for an example.

If you want to build a SpringBoot app to run the Broker, you simply need to make the Camel context available in Spring and it should be picked up.

In your project you have added

Whenever you face such type of error, while running Spring Boot + JPA CRUD Example, Just check once that you have defined ID field using AUTO_INCREMENT option or not. I was having such type of Error because I did not require ID field. BUT Spring Boot Hibernate checks for Unique A_I ID field.

If you don't require ID field, then use and Your problem will be solved.

You need to set id and description to route context, not to rest context.

For example this definition:

Your example is referencing boot 1.5.X which uses Jedis, by default lettuce is used in Boot 2.0 if you want to use Jedis you need to manually add the dependency. Additionally you can see that Jedis isn't on your classpath and lettuce is.

To integrate a database and use it transactional, your JmsTransactionManager is not suitable. You would need a DataSourceTransactionManager instead.

I don't see any routes that send or consume to/from JMS. If you don't use JMS at all, you don't need the JmsTransactionManager.

I'm not sure if it's the best option, but for me this problem was solved when I remove the jar dependency tomcat-embed-jasper. I've just inserted the code below in my pom.xml:

Instead of using @Consumed you can use a custom deleteHandler which you can configure on the JPA endpoint.

• https://github.com/apache/camel/blob/master/components/camel-jpa/src/main/java/org/apache/camel/component/jpa/DeleteHandler.java

• https://github.com/apache/camel/blob/master/components/camel-jpa/src/main/docs/jpa-component.adoc