demo-application | Demo application using TERASOLUNA Server Framework for Java | HTTP library

Your application is listening on port 8080. In your Service file you need to use the targetPort as 8080.

ok so i checked InertiaJS's sample CRM project and looked at the generated app.blade.php file, and @routes was replaced with generate(); ?>. I replaced @routes with that and the route() function's working now. would still appreciate if there's a better way to do it.

Look at your port information :
The port 9100 of the container is published on the port 7000 on the host.
But look at your log application : it is deployed on 8080 (and not on 9100).
What you want is publishing the container port 8080 on the 7000 port of the host such as :

Your if syntax is slightly off. The command has to be on the same (logical) line as the if. Also the else and the command after it has to be on the same (logical) line. Use parentheses to start a code-block (the start of a command block is syntactically treated as a valid command):

term queries are not analyzed see the official doc which clearly mention this

Returns documents that contain an exact term in a provided field.

Which clearly means that index time you are using some custom analyzer which is removing - and joining the tokens ie for demo-application-child3 your custom analyzer would be generating demoapplicationchild3 token, which you can easily confirm using the Analyze api.

If you want to get result either change term query to match query or use the .keyword suffix with your field if mappping is generated dynamically or create another field which is of type keyword which uses no-op analyzer.

From my experience performance problems with JDKs are related mostly to one of the following:

• JIT Compilation
• VM configuration (heap sizes)
• GC algorithm
• Changes in the JVM/JDK which break known good running applications
• (Oh, and I forgot to mention class loading...)

If you just use the default JVM configuration since OpenJDK11, maybe you should set some of the more prominent options to fixed values, like GC, Heap size, etc.

Maybe some graphical analyse tool could help track your issue down. Like Retrace, AppDynamics or FlightRecorder and the like. These give more overview on the overall state of heap, GC cycles, RAM, threads, CPU load and so on at a given time than log files could provide.

Do I understand correctly that your application writes about 30710 lines to the log within the first second of running (under OpenJDK11)? Why is it "only" writing about 7k lines under OpenJDK14 in the first second? This seems like a huge difference for an application that is just started on different JVMs to me... Are you sure there are not for example high amounts of Exception stacktraces dumped into the log?

The other numbers are even higher sometimes, so maybe the slowdowns are related to exception logging? Or even swapping, if RAM gets low?

Actually I am thinking, if an application does not write anything into the log, this is a sign of smooth running without problems (unless it is frozen entirely in this time). What is happening from seconds 12-22 (in the OpenJDK14 case here) is what would concern me more... the logged lines go through the roof... why?

And afterwards the logging goes down to all time low values of about 1-2k lines... what is the reason for that?? (Well, maybe it is the GC kicking in at second 22 and does a tabula rasa which resolves some things...?)

Another thing may be your statement about "single CPU" machines. Does this imply "single core" also (Idk, maybe your software is tailored on legacy hardware or something)?

And the "single CPU" VMs are running on those machines? But I assume, I am wrong about these assumptions, since almost all CPUs are multicore nowadays... but I would investigate on a multithreading issue (deadlock) problem maybe.