AsyncExecutor | Prototype for roblin rtc sdk | Augmented Reality library

I have been struggling with implementing a multi-threaded approach to the application I am working on.

The part I want to run in parallel threads was originally constructed with a for loop going about a list.

I have fragment which contain recyclerview. if progaurd was not enabled everything works fine. if i enable the progaurd then data coming from API is not setting. if i put breakpoint it's not reaching the constructor but fragment is setting,recyclerview showing null data.

I have added progaurd rules also please check

I spent all day trying to figure out how to solve this issue.

The purpose is to insert several sequence of strings into a single column of a table.

I have a method like this:

I'm trying to write RetryAdvice for Kafka handler; and fall back to saving to MongoDB as RecoveryCallback.

I have been trying to add benchmarking using the Criterion crate to my actix_web application. I have been struggling to get it to work because the AsyncExecutor trait is not implemented for tokio 0.2.x. I tried implementing the trait for the actix_rt runtime but ran into issues there as well, code below

UPD: Marked answer solved the problem see it's comments for small fixes.

First of all forgive me for butchered code. This problem drives me crazy, I tried a lot of stuff in order to determine the source of the problem, but failed.

I have a Spring Boot web app, which has the FMonitor service. It works while the app is running and notifies me, when a file with ".done" extension appears in certain folder. When I run the app it works flawlessly (at least it seems like that).

I decided to practice with tests and threw three simple ones. They work with success when I run them one at a time. However, when I run the whole class of tests, only first one passes, other two fail.

My tests check the System.out and compare it with desired output. And here is the strangest thing to me. Thats what happens.

First test passes, output of the FMonitor is exactly like in assertEquals. Found test1 Found test2 Found test3

Second test fails. Output is oddly doubled for some reason: Found test1 Found test1 Found test3 Found test3

And then third one fails. Output is triple now: Found test Found test Found test

My guess is that I do something entirely wrong with threads, so fm.monitor() somehow catches all of events and something like that. I'm very confused. I tried a lot of things with how to implement threading here, I'm not good with it, but it still works same. Also I thought that @Async annotation for monitor() could mess up something, but removing it didn't change anything. Help, please.

BunchOfTests

I am trying configure Spring Boot Security to allow anonymous user reach all URLs except one. By default user and generated security password by Spring. I need just one page for maintanance application I already tried a lot tips and tutorials.

1 2 3 4

And others.

But Spring still required authetification for all pages.
My current security config

I have the following application (the same application with Gradle + Spring Boot is here https://www.dropbox.com/s/vizr5joyhixmdca/demo.zip?dl=0):

Writer.java contains some code that is run asynchronously with the help of @Async annotation. One method returns void and another returns Future. Both variants are allowed as per documentation.

I am using Spring Integration and Scatter Gather handler (https://docs.spring.io/spring-integration/docs/5.3.0.M1/reference/html/scatter-gather.html) in order to send 3 parallel requests (using ExecutorChannels) to external REST APIs and aggregate their response into one single message.

Everything works fine until exception is thrown within Aggregator's aggregatePayloads method (AggregatingMessageHandler). In this scenario error message is successfully delivered to Messaging Gateway which initiated the flow ( caller ). However, ScatterGatherHandler thread remains in hanging state waiting for gatherer reply (I believe) which never arrives due to the exception within it. I.e each sequential call leaves one additional thread in "stuck" state and eventually Thread Pool runs out of available working threads.

My current Scatter Gather configuration: