gziphandler | Go middleware to gzip HTTP responses | HTTP library

This still doesn't show a cause. NoClassDeffFoundErrors are usually related to a clashing dependencies. You could have different versions of dl4j/nd4j on your classpath but I doubt it. Most of the time this is the side effect of a native dependency crash somehow.

Of note here:

I wouldn't recommend running the keras converter (or any model import process) in line. I would recommend converting the models separately. This is mainly for performance reasons

Whatever your problem is there are usually a few:

1. glibc version with hdf5. Keras import uses hdf5 underneath the covers which means c code.

2. Nd4j native dependency crash: this is also usually glibc related. We load nd4j in to memory to create and set native arrays (which means more java calling in to c++) that then can trigger a crash depending on what OS you're running on

3. Another hdf5 error: this could be an invalid model or some hdf5 version error.

In any case, we would need more information before we can help you. Whatever you're reporting here isn't enough. Could you mention your docker container OS and what version of dl4j/nd4j is bundled here?

Edit: I see it's oracle linux 7 which is effectively RHEL/Centos. If you're using docker I would recommend a newer image maybe.

Beyond that if it is an nd4j related crash (still not verifiable from your stack trace) if you are using the latest version you might be seeing a crash due to glibc version.

If so there was a recent update to the nd4j classifiers you can find here: https://repo1.maven.org/maven2/org/nd4j/nd4j-native/1.0.0-M1.1/

Older glibcs need to use linux-x86_64-compat as a migration path

Okay so interestingly this issue stopped occurring after I upgraded the instance type to m6g.large.elasticsearch due to high jvm pressure. However my development and staging single-node clusters (using a t3.small.elasticsearch instance) are still logging this exception.

I'm not 100% sure if upgrading your instance type is the key to solve this issue. For now I will accept my own answer. If I have new insights I'll let you know.

1. You should only gzip when it's requested by the client.

Accept-Encoding: gzip is never requested, but you gzip the response anyway.

So curl gives it back to you as-is.

2. Given the behavior of your browser, it sounds like double-compression. Maybe you have some HTTP reverse proxy in place which already handles compression to the browser, but doesn't compress backend traffic. So you may not need any gzipping at the backend at all - try curl --compressed to confirm this.

3. You should filter out Content-Length from the response. Content-Length is the final size of the compressed HTTP response, so the value changes during compression.

4. You should not blindly apply compression to all URI's. Some handlers perform gzipping already (e.g. prometheus /metrics), and some are pointless to compress (e.g. .png, .zip, .gz). At the very least strip Accept-Encoding: gzip from the request before passing it down the handler chain, to avoid double-gzipping.

5. Transparent gzipping in Go has been implemented before. A quick search reveals this gist (adjusted for point #4 above):

This is a serialization issue. As per the github repo that you shared there doesn't seem to be a endpoint associated with /gameusers path. But its being called in the health check callback. So the call is failing and its not able to deserialize error response into ArrayList. In GameUserRESTController.java you need to add the path as follows:

This part of source code https://github.com/trinodb/trino/blob/343/presto-main/src/main/java/io/prestosql/server/security/PasswordAuthenticatorManager.java#L62-L84 loads the config.

So search for -- Loading password authenticator -- in log that should give you more information regarding what could have gone wrong.

Check if file contents are loaded properly or not, sometime that is also the cause for the error.

Finally, the server starts normally if i use another kind of artifact, which is a modern one : "dropwizard-guicey" in version 5.2.0

Remark : the enpoint "/brands/name" does not work ! It is because of an Injection problem. (beware !)

Maybe this can help you, and it's due to version of swagger and how file upload API is defined:

Finally I found answer for this, actually previously there is no support for file upload, now they updated swagger-ui.js file. You need to replace your old one with new and also you have to define these properties under Parameters for particular parameter:

Dependency convergence errors are fixed by using entries in , not by using exclusions.

You do the following:

• You look into the list which transitive dependencies appear in more than one version.
• You pick the version you want (often the newest).
• You add an entry to the section of your POM in which specify this version.
• This entry will then override the different transitive dependencies.

This was a bug in GzipHandler related to flush of empty initial buffers (a flush before attempting to send any data).

Issue https://github.com/eclipse/jetty.project/issues/4835 has been closed.

The fix is present in Jetty 9.4.29.v20200521 (now available on https://eclipse.org/jetty/ and maven central)