Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Problem Vaadin 8.0.x / Eclipse / Jetty and @Push

Gerhard Hofstaetter
5 years ago Mar 27, 2017 5:58pm

HI,
we have some problems starting a Vaadin application with @Push in Eclipse with an embedded Jetty.

The application startup in Eclipse is fine, but as soon as we start a browser session we immediately receive a "Session expired"
it does not work with Vaadin 8.0.3 or 8.0.4 and Jetty 9.4.x - no matter if we use the compatibility packages or the "core" Vaadin 8 packages
it does work with Vaadin 8.0.2 (or earlier versions) and Jetty 9.4.x
and it does work with Vaadin 8.0.3 or 8.0.4 and Jetty 9.3.x
(and of course it does work in a Tomcat environment)

is this somehow related with this two issues ?
Problem with Atmosphere -> Session Expired
https://github.com/vaadin/framework/issues/8134
https://github.com/Atmosphere/atmosphere/issues/2241

and what can we do ?

Regards
Gerhard
 

Patrick Höhle
5 years ago Mar 27, 2017 6:04pm
Andreas Decker
5 years ago Mar 28, 2017 11:57am
Patrick Höhle
5 years ago Mar 28, 2017 1:07pm

i had that issue with @PUSH and without @push ... but when reading your posting, i think it is not the same issue as mine was.

Gerhard Hofstaetter
5 years ago Mar 30, 2017 11:10am

any comments from Vaadin concerning this problem ?

since the problem occurs when switching from Vaadin 7.x/Vaadin 8.0.2 to Vaadin 8.0.3/Vaadin 8.0.4 perhaps it has something to do with the changes in these releases ....
we are still faced with this problem

Regards
Gerhard 

Gerhard Hofstaetter
5 years ago Apr 02, 2017 11:08am
George Soler
4 years ago Apr 17, 2017 8:02pm

I run the same problem enabling @Push with jetty 9.4.3 atmosphere-runtime-2.4.5.vaadin2.jar  and vaadin 8.0.5
Substituting atmosphere-runtime-2.4.5.vaadin2.jar with atmosphere-runtime-2.2.7.vaadin1.jar eliminates the session expired message and shows the UI correctly, BUT there are incompatibility problems and push will not work:
java.lang.NoClassDefFoundError: org/atmosphere/cpr/AtmosphereRequestImpl

Is this only a jetty issue? Can Vaadin revert back to the earlier atmosphere and resolve the compatibility isses?

In the meantime, I cannot upgrade to Vaadin 8.0.5

Andreas Decker
4 years ago Apr 18, 2017 6:06am
Andreas Decker
4 years ago Apr 19, 2017 7:01am
Kari Mattsson
4 years ago Apr 19, 2017 7:23pm
Andreas Decker
4 years ago Apr 21, 2017 7:09am
Roland Binder
4 years ago Apr 21, 2017 7:25am
Kari Mattsson
4 years ago Apr 21, 2017 7:29pm

Apparently Atmosphere must be updated to be compatible with Jetty 9.4.x, so this not purely Vaadin issue.
Maybe you want to push this issue:
https://github.com/Atmosphere/atmosphere/issues/2241
 

Andreas Decker
4 years ago May 04, 2017 8:01am
Gerhard Hofstaetter
4 years ago May 29, 2017 4:44am
Alexander Cherepanov
4 years ago Jul 21, 2017 10:58am
George Soler
4 years ago Jul 21, 2017 5:31pm
Alexander Cherepanov
4 years ago Oct 04, 2017 10:03am
Alexander Cherepanov
4 years ago Oct 04, 2017 11:12am
Alexander Cherepanov
4 years ago Oct 05, 2017 7:31am
Alexander Cherepanov
4 years ago Oct 05, 2017 10:18am
Alexander Cherepanov
4 years ago Oct 05, 2017 11:17am
Alexander Cherepanov
4 years ago Oct 06, 2017 6:08am
Alexander Cherepanov
4 years ago Oct 06, 2017 6:10am