-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Hystrix 1.5.5 and Jackson Error on Metrics-Event-Stream #1331
Comments
There is a configuration property for the max concurrent connections, the default is 5. |
@mattflix yeah, as I said, the problem isn't that, the exception is masking it... The problem seems to be that the jackson version inside jboss as is older that the version used by metrics-stream... but the error shown is the number of connections, which is unrelated to the root cause... |
FWIW: version 1.5.3 works |
Hystrix 1.5.4 broke out the serialization of metrics into its own module (hystrix-serialization). That module depends on 2.7.5 Jackson libraries. In your application, do you have the hystrix-serialization jar? What versions of Jackson do you have there? |
@mattrjacobs yes, it was working until I updated it. It's a dependency hell... just so you have a slight idea: I'll try to bump all, for now, the report that remains is the misleading error message 👍 |
I know that feeling :) I suspect that the mismatched Jackson is the problem. Please let me know if that resolves things. |
@mattrjacobs yeah, I'll try to do that... |
I got the same problem in 1.5.5 and rectified it by excluding Jackson. |
I was able to get this working when using an older jackson dep by adding hystrix like this: <dependency>
<groupId>com.netflix.hystrix</groupId>
<artifactId>hystrix-metrics-event-stream</artifactId>
<version>1.5.5</version>
<exclusions>
<exclusion>
<groupId>com.fasterxml.jackson.dataformat</groupId>
<artifactId>jackson-dataformat-cbor</artifactId>
</exclusion>
</exclusions>
</dependency> |
This looks resolved. Please re-open if there's more to discuss |
Hi, I'm using 1.5.8 of hystrix-metrics-event-stream. First I had the same verifyError like the original poster, I added the exclusion like @pablote suggested then, but now I get the following ClassNotFound:
Now I'm not sure how to work around this, since there is obviously a Jackson on classpath already, but this is obviously not compatible to the one hystrix is using. Any hints? |
Do you have the hystrix-serialization jar on your classpath? |
Yes. Parts of the application I'm trying to use with Hystrix is depending on Jackson 2.2.1, but at this early time there was obviously no CBORParser, thats why excluding jackson-dataformat-cbor means class CBORParser is not there at all. I guess I can only solve this dilemma by using a very early version of Hystrix (say 1.4.26 or the like). What do you think, would that make sense? Edit: Fixed suggested Hystrix Version. |
So I think the problematic path for your use-case is that Otherwise, pinning Hystrix back would work as well |
I think a better design of this set of functionality is to be modular for serialization. If you need JSON serialization, then there should be a set of methods with a dependency on jackson-json. If you need CBOR serialization, then there should be a set of methods with a dependency on jackson-cbor. In this PR, I've deprecated (and hollowed out) the byte[] implementations of serializations/deserializations. They can come back in a different module when I reintroduce the ReactiveSocket impls of streams (#1325). Thoughts? |
Thank you so much Matt, looks good so far. Is there a timeline already when 1.5.9 will be available from Maven Central? |
It usually takes a couple of hours from the time I press the button, but it's out of my hands. Can you re-try? |
Hi Matt, I just tested the new release 1.5.9 from Maven Central and voila: It works like a charm now! No class loader errors at runtime. My effective dependency tree looks like this now (the omitted and newer Jackson version does obviously not affect the functionality of the JSON serialization that is needed by Hystrix). Thank you so much for your quick reaction and that nice release! |
Great- putting all the serialization options in the same jar was a mistake by me. I'll figure out a better way to do it once we have pieces that need the CBOR serialization. |
Last version of hystrix-metrics-event-stream (1.5.5) running on a JBoss AS 7 app server, when accessing the metric stream, give me this error:
Error log
And the error I got is
MaxConcurrentConnections reached: 5
.Any tips on how to fix that?
Thanks
The text was updated successfully, but these errors were encountered: