Skip to content
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

Rename AttributeKey persistent channel to allow coexisting with 0.7 #440

Closed
smaldini opened this issue Sep 23, 2018 · 0 comments
Closed
Labels
type/bug A general bug
Milestone

Comments

@smaldini
Copy link
Contributor

If not renamed, having both 0.7 and 0.8 in use in your application will result in:

    at io.netty.util.ConstantPool.createOrThrow(ConstantPool.java:113) ~[netty-common-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.ConstantPool.newInstance(ConstantPool.java:95) ~[netty-common-4.1.29.Final.jar:4.1.29.Final]
    at io.netty.util.AttributeKey.newInstance(AttributeKey.java:55) ~[netty-common-4.1.29.Final.jar:4.1.29.Final]
    at reactor.netty.ReactorNetty.<clinit>(ReactorNetty.java:614) ~[reactor-netty-0.8.0.RELEASE.jar:0.8.0.RELEASE]```
@smaldini smaldini added the type/bug A general bug label Sep 23, 2018
@smaldini smaldini added this to the 0.8.1.RELEASE milestone Sep 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant