Spring-Boot-JPA | Starter application in Spring Boot using JPA | Object-Relational Mapping library

It happens because when you want to query the Team, say, team 'A', it also carries a list of Players who are in team 'A', which themselves carry the Team they are in(team 'A'), which also carries a list of Players... You get it, it infinitely cycles through this relationship with no end. To avoid a StackOverflow error, you need to annotate the side of @OneToMany with @JsonIgnore if you are using Jackson, or @JsonbTransient if you use plain jsonb.

I found a solution usable from here. It doesn't use integrator but add all the event listeners one by one. Below is my code:

Spring offers two solutions for such kind of requirements, you can use Query natively in your repository, and send bind list to it like this

If problem doesn't solve even after including properties as in application.properties, Then problem will be solved when including testOnBorrow,validationQuery in application-context.xml located in src/main/resources

I have found out the solution. This can be resolved in pom.xml by modifying like that:

You should be aware of this very important footnote in the reference documentation of Docker Compose:

depends_on does not wait for db and redis to be “ready” before starting web - only until they have been started. If you need to wait for a service to be ready, see Controlling startup order for more on this problem and strategies for solving it.

In your case, your Spring boot container starts right after your MySQL container is being started. There's no guarantee though that MySQL will be able to take connections when Spring boot is setting up its connection pool.

This means that your Spring boot connection will fail to startup, because MySQL isn't ready yet. This results in your application container to be killed.

The solution to this problem is mentioned within the documentation I quoted. Namely, you have to use some kind of polling mechanism to see if you can connect to your database or not.

If you don't want to use tools like wait-for-it or wait-for, you could write a simple Shell script that does something like this:

Auditing is based on the JPA Lifecycle events. Only the methods directly manipulating instances (persist, merge and remove) trigger such events.

The execution of queries, modifying or otherwise, does not trigger any events and therefore, won't cause auditing to happen.

See the JPA Specification section 3.5.2 Lifecycle Methods for details.

Unidirectional or bi-directional, it all depends on your requirements. For example :- A and B are two entities : 1>A has one-one unidirectional relationship with B, This is a scenario where you do not need/want to load A when you are loading B. 2>If you want to load A when you are loading B , then you will require One-One bi- directional mapping.

Here's an example about how to use QueryDSL:

Include the following dependencies in your pom.xml file: