hikari | A Discord API wrapper for Python and asyncio built on good intentions | REST library

It seems the issue lies in the fact with how you try to access your DB in gitlab.

When you add the mysql service

It turns out that context was recreated almost with every test class because I was extensively using @MockBean annotation in my tests. Since it affects Spring context, each @MockBean/No MockBean combination in different test classes counts as a different context, i.e.:

• Test class 1: bean MyService is a MockBean, MyOtherService is not
• Test class 2: bean MyService is a MockBean, MyOtherService is also a MockBean
• Test class 3: none of these two beans is a MockBean

In such case, a new Spring context will created for each class because the bean configuration is different, resulting in an increasing number of connections to the datasource.

To (partially) solve this, I looked for patterns in the beans combinations of my test classes and created a new class I called TestMockBeans.

Its sole purpose is to declare as many MockBeans and/or SpyBeans as possible to re-use in similar test configurations. I extend corresponding test classes with TestMockBeans, and then, because they share this similar setup, Spring identifies their contexts as similar and does not recreate a new one for every test class.

As you can guess, not all of my tests throughout the Spring boot app share the same need for Mockbeans (or absence of Mockbeans) so it's only a partial solution, but I hope it will help someone experiencing the same issue to mitigate it.

According to the Hibernate Documentation when you have a UniDirectional relation in your entity schema and you have only the side of @OneToMany , you can't use the annotation @JoinColumn.

According to the Doc

When using a unidirectional @OneToMany association, Hibernate resorts to using a link table between the two joining entities.

You must remove the @JoinColumn so that hibernate follows the default process of creating a intermediate join table and then it will be able to proceed.

Found my answer in this thread https://developer.jboss.org/thread/241453. It is a log4j/jboss configuration issue. The fix is to either exclude jboss logging subsystem from jboss deployment configuration or get rid of the console appender. Thanks to Ralph Goers from Log4J team for guiding me towards the jboss thread.

I have closed the issue that I raised to https://issues.apache.org/jira/browse/LOG4J2-3274. The code snippet that I shared in this question was from log4j-1.2 compatibility adapter which doesn't has any impact in my code because I am already using the latest api version.

Your CurrencyExchange_Logic class has two constructors: the required args constructor, which has parameters corresponding to the 3 final fields, and the all args constructor, with parameters corresponding to those 3 fields as well as start and end.

When you only have one constructor defined, Spring knows how to implicitly choose it for injection. However, when you have more than one, you have to tell it which one you want it to use, using the @Autowired or @Inject annotation.

I would guess you want Spring to use the required args constructor, as I doubt Spring has any way of knowing how to resolve the start or end fields. This can be done in lombok (@RequiredArgsConstructor(onConstructor_ = @Autowired)), or by just explicitly writing the constructor yourself and annotating it. Note you could also get rid of the all args constructor, if you don't need it, and Spring's implicit constructor injection should "just work."

Ok, this was a local error. What actually caused the issue was that our code was written as:

Your application should listen on a non-privileged port (> 1024).

The created container is unable to use a privileged port. The bootBuildImage task creates and runs images utilizing buildpacks (for runtime paketobuildpacks/run:tiny-cnb), the application in the container doesn't run as root. Therefore you can not listen on a port below 1024.

Spring boot uses paketo-buildpacks, which have some security-hardenings in them

The stack images are run as a dedicated non-root user when building and running applications.

see paketo documentation

Mistake in Hibernate Relational Mapping @ManyToMany. You join base table but not join with child table. If you want to put all Cascade Type don't put CascadeType.DETACH, CascadeType.MERGE, CascadeType.PERSIST, CascadeType.REFRESH just put CascadeType.ALL

Here down is modified code:

Article

Could you please update Snowflake account URL and try: nw99383.eu-west-2.aws.snowflakecomputing.com/