-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFLY-13695] Upgrade wildfly-http-client to 1.0.23.Final #13422
Conversation
@fl4via I just started another run but so far the security manager CI job has failed twice with what looks at a glance like the same failure pattern. |
It's failing again so there must be some issue. |
@fl4via any update? |
FYI the secmgr tests passed without issues in the downstream PR |
@bstansberry @spyrkob I don't know why we're seeing this kind of error. I remember when we're working on wildfly-http-client fix that I was running some tests with security enabled, but everything seemed fine on the tests I ran and I don't recall the details now. I'll investigate the failing tests in my machine to find out what's going on. |
It looks like trying to remove transaction recovery files fails with secmgr. There's following stack trace in the logs:
Adding a doPrivileged block in wildfly-transaction-client like: wildfly/wildfly-transaction-client@1.1...spyrkob:WEJBHTTP-47-fix seems to fix the problem. |
@fl4via The failing test is in the multinode test suite. I see interesting stuff in the server.log for the server that acts as the 'client' https://gist.github.com/bstansberry/12abd38e6e8f19e8591805be4d940785 This logging is associated with RemoteCallClientInterceptorTestCase, the test the runs just before the 1st test that fails. The log chunk shows the deploy/undeploy of the archive used by that test, followed by a server reload, which is done by that test's ServerSetup teardown method. You can see the interesting logging in the middle of the reload. Also, in case it's useful, is that in the past the fact that CI uses -Dipv6 has resulted in it finding problems that devs didn't see themselves. Which is why CI uses -Dipv6. ;) |
Closing this one as WF is up to 1.1.2.Final. |
Jira: https://issues.redhat.com/browse/WFLY-13695
20.x PR (in case one is needed): #13423
Bug
Bug