tty-server | Server side for tty-share

Thanks all.

I was using an older Kafka version.

I upgraded Kafka in the cluster from kafka_2.12-1.1.0 to the latest stable version kafka_2.12-2.7.0. I also upgraded zookeeper from zookeeper-3.4.6 to apache-zookeeper-3.6.2-bin version.

In addition in the run file I added the following:

Having the same class name in multiple locations on your classpath is a bad idea.

This is the most common form of unstable operation on Java there is!

The classloaders in Java have no guarantee of load order behavior if the same class is present in multiple locations within the classloader.

In one run you might accidentally load the classes in the order you intend, and have it run properly, then at a future date you run the same program and the load order is different, now you are running with a different class version and you have unexpected behavior.

The only way to fix this is to clean up your classloader and ensure that you only have 1 version of the class you intend to use.

This is what Jetty is telling you.

As for this specific one, javax.websocket-api and javax.websocket-client-api, you want to exclude javax.websocket-client-api at the gradle level, as all of the websocket client classes are also present in the javax.websocket-api.

The javax.websocket-client-api jar is only intended for projects that only use the javax.websocket Client, without a javax.websocket Server.

Following the suggestion of joakim-erdfelt I have modified my gradle.build and this prevent the problem:

Jetty 11 is based on Jakarta Servlet 5.0, which is part of Jakarta EE 9.

Jakarta EE 9 underwent the "big bang" change (their name, not mine) to namespace and packaging, there is no longer a javax.servlet.* it is now jakarta.servlet.*.

There is literally nothing in Jetty 11 that looks for javax.servlet.*.

Some quick history ...

• Oracle owned Java EE.
• Oracle produced Java EE 7.
• Oracle decided it didn't want to create/manage EE anymore.
• Oracle gave all of EE to the Eclipse Foundation.
• Oracle did not grant the Eclipse Foundation the right to use "java" or "javax" in this new EE reality.
• Eclipse Foundation renamed it to "Jakarta EE" for legal reasons.
• Eclipse Foundation releases "Jakarta EE 8" which is essentially just "Java EE 7" renamed for legal reasons (no package namespace change yet)
• Eclipse Foundation renamed all packaging from javax. to jakarta. for legal reasons.
• Eclipse Foundation releases "Jakarta EE 9" which is essentially just "Jakarta EE 8" but with a namespace change (this is the "big bang" mentioned above)

(be aware, I skimmed over a lot of other things that happened between these steps)

javax.servlet.* is dead, long live jakarta.servlet.*.

Jetty maintains the following versions (currently)

• Jetty 9.4.x - Servlet 3.1 / Java EE 7 (javax.servlet)
• Jetty 10.x - Servlet 4.0 / Jakarta EE 8 (javax.servlet)
• Jetty 11.x - Servlet 5.0 / Jakarta EE 9 (jakarta.servlet)

There will never be a backward compatibility feature to allow both javax.servlet and jakarta.servlet to coexist in a release of Jetty. (we've tried this, the complexity of the Servlet spec makes this untenable for the HttpSession, RequestDispatcher, Dynamic servlet/filter registrations, etc)

The best we can hope for (and there are several projects started to do this, all alpha quality ATM) is some kind of tooling that updates your jars and/or source for the new packaging in an automated fashion to then be run on a Jakarta based server.

This was caused by a bug in the SDK triggered by a change in the service behavior. (transfer encoding chunked)

The bug has been fixed and is available in release 1.0.8 of of the core library

It seems like the jetty-server was cleaned up a bit and these Connectors are not used anymore. Maybe you can have a look at the following post to find a way on how to migrate your code to the new way of work: https://www.eclipse.org/lists/jetty-dev/msg01952.html

Just changing the version string isn't sufficient.

You'll also need ...

• ALPNServerConnectionFactory - for processing the TLS layer (known as ALPN) that selects the HTTP/2 protocol
• HTTP2ServerConnectionFactory - for using HTTP/2 protocol

As seen in the embedded / Http2Server.java example

The key is that you will chain the connection types together, ALPN to HTTP2 to HTTPS.

You will have to add apache-jsp so that your server will support jsps. If your web app uses jstl, you should also add apache-jstl.

This error was due to different cxf jar versions being used This was solved by matching all the cxf versions in the pom.xml. of current project and all the projects being imported.

You should not use 0.0.0.0 but the hostname as defined through the dockerfile. So at the zoo1 config server1 should be zoo1, at the zoo2 server2 should be zoo2 and at the zoo3 server should be zoo3.