snazy commented on issue #3685: URL: https://github.com/apache/polaris/issues/3685#issuecomment-3879497770
> I wonder if there is anything going on and this request is made on the event loop thread instead of a worker thread, as I would expect the same behaviour for both operations. I wouldn't worry much about the thread name that's been logged. I assume ([asked for confirmation](https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/Thread.20logged.20in.20HTTP.20access-log/with/573098838)) that this is just the thread that logs the message, which does not need to be the same thread that executed the [blocking request](https://quarkus.io/guides/rest#execution-model). The actual logging is basically just one of the last "actions" that run during the whole HTTP request processing. All REST API requests in Polaris are blocking requests, as the OpenAPI generation tool does not allow us to use a async/reactive programming model. The thread name in the access log would become even less meaningful for async/reactive requests. It's not the case that all "parts" (core HTTP "machinery", authZ, etc) involved in processing a single HTTP request run synchronously on a single thread, not even for blocking request. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
