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
[XNIO-317] Introduce API to clean ThreadLocal caches from ByteBufferSlicePool #176
Conversation
Build 57 outcome was FAILURE using a merge of 011c06b Failed tests
|
Hi @dmlloyd, can this be merged and released as well, please? |
Did we have a discussion about this? Normally I don't introduce new or change existing APIs in a minor branch. |
We did last year and the change ended up in 3.7 instead of 3.6 |
Build 62 outcome was FAILURE using a merge of 011c06b Failed tests
|
Build 80 outcome was FAILURE using a merge of 011c06b Failed tests
|
@fl4via @dmlloyd this is the same change as is merged in 3.x (#142). This seems to be blocking undertow-io/undertow#604. Can this be merged, please? |
As I said, we don't normally merge new APIs into old branches. Can we upgrade to a 3.7 release instead? |
We did some pre-testing with 3.7 and didn't really see any issues. @fl4via, was there anything in particular you were worried about? |
@mackaypeter the only concern about upgrading to XNIO 3.7.2.Final is that it requires jboss-remoting 5.0.12.Final to prevent a deadlock (REM3-336) |
@mackaypeter btw, I advise the upgrade to XNIO 3.7.2.Final and jboss remoting because of several issues that had been fixed. I'm tagging jboss-remoting today |
@fl4via thank you. I just want to mention that EAP 7.2.x is already on remoting 5.0.12 (https://github.com/jbossas/wildfly-core-eap/blob/6.0.x/pom.xml#L178) |
Closing this because the API doest not apply to old branch |
Issue: https://issues.jboss.org/browse/XNIO-317