dmvk commented on pull request #18733: URL: https://github.com/apache/flink/pull/18733#issuecomment-1042994014
> However, since the AWS SDK jar is loaded by parent classloader I assume the Netty threads would be spawned via AWS SDK threads also loaded from parent classloader, thus attaching parent context classloader. But this is just a guess. My intuition would be that this will use the user classloader as the threads are spawned from the user code. Maybe we could solve that by overriding the thread factory from the ELG and setting the context manually (not sure if thats doable)? -- 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]
