byte-buddy | Runtime code generation for the Java virtual machine | Video Game library

Not sure how much of an answer this will be, but the issue is now (seemingly) self-fixed... I'll describe what I've done and what happened in case it helps other users experiencing similar issues.

After unsuccessfully trying all the things described in the question, I had to restart the laptop (again) for an unrelated problem (Zoom wouldn't start up). Upon restart the laptop simply crashed and restarted again on its own. Then it did the same a second time. Upon the third automatic restart, I was no longer experiencing issues building my Java applications.

My guess is that the NVRAM got somehow corrupted and this was affecting the JVM's ability to accept incoming requests for attachment. On a MBP M1 one cannot reset the NVRAM as with Intel models (pressing Cmd + Opt + R + P), instead the NVRAM is supposed to self-heal when it detects something wrong. I suppose after crashing the MBP finally decided to repair the NVRAM and that's why the build starting working again.

UPDATE: I have now encountered this issue a few more times and every time the "solution" was to restart the laptop a few times until it crashed. After that the issue would disappear. This adds weight to the idea that there is some inherent instability with the combination of hardware and software specified in the question. I'll leave this as an "answered" question in case anybody else has the same issue.

UPDATE 2: This may be pure coincidence, but the issue seems to be exacerbated by the usage of an additional screen, particularly using an iPad via Sidecar.

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

You can create such a class. Have a look at the DSL and FieldAccessor for creating (overriding) methods that access fields.

On the other hand, it seems to me that you should rather look at MethodHandles which can access field values as fast as any Java byte code once generated. And I argue that resolving a method handle takes less resources then creating a class.

I just accessed your database with the following URL:

I've tried your example:

You need to take care of a few things here:

• You have already download the ChromeDriver and accessing it as:

Could you please try with the following:

It was an Intelli-J issue!

So, cleaning the Intelli-J dependency spaghetti up solved it!

1. File > Invalidate cache ... and restart. Helped a bit.
2. Closing the Intelli-J project. Then removed manually the ".idea" folder and any *.iml file.

Yes, I did option 1 previously. Especially doing action 2 solved it within a minute.

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."