-
Notifications
You must be signed in to change notification settings - Fork 580
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
util-jvm: Support for HP NonStop Hotspot JVM #272
Comments
@pvasterd, is this something you'd like to contribute? We don't run that VM so there is no way for us to test it. |
Hi @bryce-anderson, I did contribute this in this #273. That PR was not merged, but my commit 0970951 got in and is now part of 20.4.0. Since my commit got in I closed #273 myself. Also, this was tested on HP NonStop JVM and works as expected (no metrics, but properly dealing with unsupported operations for the HotSpot JVM). |
Okay, sounds like it's already done. Thanks! |
Twitter/util does not work on HP Nonstop Hotspot JVM as some native metrics functions are not implemented
This issue is cloned from twitter/finagle#833, but as issue and fix is in twitter/util, moving the issue to twitter/util as well.
Expected behavior
Even if certain native functions are not supported by the underlying JVM - that are not essential for the base functionality- it should continue to initialize (and logging some warnings that certain information may not be available).
Actual behavior
javax.naming.OperationNotSupportedException while Finagle is initializing:
Steps to reproduce the behavior
I am afraid you need a HP non-stop machine to reproduce this, but if you have this, simply create a Finagle Http.Client.
HP NONSTOP info:
The text was updated successfully, but these errors were encountered: