tisaksen wrote:
That was it! Thank you so much!
Can you create a JIRA here - JBoss Issue Tracker and explain the issue and point to this thread? The workaround you did was fine but it's still a workaround. The proper fix can be done in WildFly itself.
I sure will. Thanks.
For your information jaikiran
After implementing the fix in my constructor I have added some more code in the handlerRequest method and I got stuck in the same situation as in the constructor.
To fix it I had to apply the same fix as in the constructor but I suppose I could simply skip Thread.currentThread().setContextClassLoader(oldCL); but I don't know if it would cause any other problems.
I'm not sure if/how this finding will affect your fix https://issues.jboss.org/browse/WFLY-9773