Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 8.1.12 with JDK11

Of note, the MappedLoginService was removed as part of commit

As a result of working issue

Read the commit details, perhaps there's something in there that might help you.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Thu, Sep 5, 2019 at 12:44 PM Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
If you are doing this work, use Jetty 9.4.20.v20190813, not 9.4.18. (and stay current)
1) we are using  org.eclipse.jetty.server.AsyncContinuation. 

Starting in Servlet 3.0 (Jetty 8.1.x) you should have transitioned to using the standard async techniques.

Look at javax.servlet.AsyncContext and switch to using it.
The methods names should seem familiar.

While the continuation classes are still present in Jetty 9.4.x they are deprecated and fully removed in Jetty 10.0.x

2) We are using AbstractHttpConnection.   specifically AbstractHttpConnection.getCurrentConnection() method.
4) we are using connector.getConnection() method. 

Accessing the Connection is a strong anti-pattern.
Why are you doing this?

3) We are using which is not present in Jetty 9.4.18.

The entire security layer was refactored in Jetty 9.x
What specific feature of MappedLoginService were you using?
Based on your answer we can point you to the correct code.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Thu, Sep 5, 2019 at 11:30 AM anand patel <anandpatel9998@xxxxxxxxx> wrote:

Hi Team,

Currently we are using Jetty 8.1.12 with JDK8. We are migrating to JDK11. As per this documentation, Jetty 9.4.12 onward it is fully compatible with JDK11. (Also as per this, they encourage old jetty users to upgrade to latest version as soon as possible). Because of dependency on some classes which are absent in Jetty 9.4.x, we can’t move from 8.1.12 straight forwardly. 

I wanted to know if anyone has faced any issue with Jetty 8.1.12 and JDK11 or not. And if yes, do you have list of known compatibility issues and any guidance for the same?

Also, while migrating to Jetty 9.4.18. I am facing following issues:

1) we are using  org.eclipse.jetty.server.AsyncContinuation. Which is not present in Jetty 9.4.18
2) We are using AbstractHttpConnection.   specifically AbstractHttpConnection.getCurrentConnection() method. Which is not present in Jetty 9.4.18.
3) We are using which is not present in Jetty 9.4.18.
4) we are using connector.getConnection() method. which is not present in Connector class in Jetty 9.4.18.


jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top