Open andrewazores opened 4 days ago
Looks similar: https://github.com/quarkusio/quarkus/issues/38913
According to this, the "multiple threads" message may just be a side effect of how the actual operation timeout is reported.
After this error, trying to create another recording with the same name fails:
2024-06-27 17:20:43,812 WARN [io.cry.ExceptionMappers] (executor-thread-1856) io.cryostat.util.EntityExistsException: Recording with name continue already exists. Try again with a different name
2024-06-27 17:20:43,812 INFO [io.qua.htt.access-log] (executor-thread-1856) 10.22.8.104 - - [27/Jun/2024:17:20:43 +0000] "POST /api/v3/targets/1/recordings HTTP/1.1" 409 76
and upon further investigation, the original request actually did result in a new recording being created on the target. Re-visiting the active recordings table results in Cryostat re-querying the target and finding that the recording does exist. However, since this is re-discovered after the fact, Cryostat thinks this recording was created externally and it has no labels associated with it.
Current Behavior
When attempting to create a new recording on a target application, Cryostat responded with an HTTP 504 Gateway Timeout response and the recording was not created. The Cryostat pod logs show an odd stack trace.
Expected Behavior
The recording should be successfully created on the target.
Steps To Reproduce
No response
Environment
No response
Anything else?