max-threads | Python module for running tasks

I am running a Spring Boot application that acts as a backend for a frontend Javascript application. The frontend is served to the client as a static resource and the backend serves API requests coming from it. The application is initially designed to run on-premise but should be built in a way that allows easy porting to a cloud-native solution.

I expect the backend to do some heavy lifting ETL work which will be heavy on the memory and CPU side. At the same time, it won't need to scale to serve many concurrent requests - it only really needs to serve requests that kick-off and manage the jobs, which will be invoked by a single user who's interfacing with it.

What are some parameters that I could tweak to fine-tune for this type of deployment?

Current thinking:

• Reduce server.tomcat.max-threads to a single digit to minimize the footprint of the request thread pool as I am not expected to handle more than one-two concurrently
• Do the same for the database connection pool
• Fine-tune Xms and Xmx when launching the JAR

I would appreciate any other insights about how to make sure that the Java application takes up as big a footprint on the system as it can as well as Spring Boot specific parameters that I could tweak. Thank you.

I'm dealing with the Tomcat configuration on springboot.

Let's supposse i have the following configuration:

I have an endpoint using CompletableFuture for async processing and I have configured embedded tomcat to have only one thread as below:

currently I am testing my Spring Boot app, which is a rest service with a circuit breaker pattern. Now I called my service with 20 threads at the same time and get the following log entry:

I'm trying to create a simple JMS ActiveMQ connection in WildFly 19, using IntelliJ. I've followed setup guidelines, but I'm hitting a connection error.

I'm running Wildfly as a local server, in standalone mode. I've updated the Startup Script environment variables in IntelliJ, to point to standalone-full.xml (apparently I need to use standalone-full.xml, in order to use JMS?)

I have a Spring RESTful service using a Tomcat web servlet that processes 2 different types of data and therefore has 2 rest controllers for each type of data. Controller #1 has the potential to perform an intensive task using lots of memory so I would like to allow up to, for instance, 10 connections on this controller. But if all 10 connections are processing on controller #1 I would also like controller #2 to have its own thread pool so it can continue processing while controller #1 is full.

The proper way to configure Tomcat is set its properties in the application.yml as described here in the spring docs. To set the total number of max connection one would use:

I wanted to test parallel requests in my controller. I know that by default Spring can handle 200 parallel requests and we can change it by modifying this property server.tomcat.max-threads

I played a little bit with that value and found interesting thing: When I set it to 3 when I start app I see 3 threads are being created: http-nio-8080-exec-1,2,3 When I set it to 5 I see 5 threads like that. And it continues up to 10 and stops at 10. When I set it to 15 there are still 10 threads of name http-nio-8080-exec. Could someone explain why it never exceeds 10?

If i will make controller like this

I'm working on a POC for a Galleon feature-pack providing the Camunda BPM subsystem.

My current progress can be found here: https://github.com/marcus-nl/camunda-galleon-pack

This article and the linked example/template have been very helpful thus far, but unfortunately I'm stuck at a point which these don't quite cover: customizing the standalone.xml configuration.

The required additions to standalone.xml are as follows: standalone.xml. So basically there are 4 additions:

1. The Camunda BPM extension and subsystem. This was no problem.
2. The H2 driver and Camunda datasource. The wildfly-datasources-galleon-pack was very helpful for this.
3. A job-executor configuration.
4. A process-engine configuration.

I can not figure out how to achieve 3 and 4. Starting with 3, the CLI command to simply add the job-executor (without a nested job-acquisitions element) is as follows:

Here is my fundamental understanding of the CPU and threads(naive!). The processor can run one thread per core.
System information on my laptop reads as show below
Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s) **Can run 8 threads in parallel **
In order to validate my understanding i create a Spring Boot(embedded tomcat) to handle each request