Prime Push not working after migrating to 6.2

[Error]

I have an app that uses Primefaces. It was on version 6.0 and everything was working fine.

Now I'm trying to update the Primefaces version to 6.2 and my websockets (prime push) stop working. I updated the Atmosphere dependency to version 2.4.6 as the manual says. However I keep getting this message:

Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent). - wasClean: true

And then my messages are not delivered; Is anyone else with this problem?
I'm using JSF 2.2 with Wildfly 10.

[stephan.wenders]

Yes, I am having the same problem.
Any help is appreciated.

Otherwise I will try to migrate to JSF 2.3 and test the new websocket feature.

[tandraschko]

I would migrate, we removed Push completely for 6.3.

[stephan.wenders]

Yes your right, but the problem is that we have to do a lot of work for this.

There will be the necessity to switch to wildfly 12 or 13 to have jsf 2.3 support,
better to wildfly 13 to have full jee8 support.

The local primefaces problem results in a lot of testing for our production environment.

Please do not get me wrong, primefaces rocks, but it takes al lot of time and it would be nice
to have a solution for the local problem.

Perhaps an additional information, the browsers console output will give a hint.

Code: Select all

Websocket closed, reason: Connection was closed abnormally (that is, with no close frame being sent). - wasClean: false
socket.js.xhtml:1:40274
Websocket failed on first connection attempt. Downgrading to long-polling and resending
socket.js.xhtml:1:40274
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713589
[HTTP/1.1 404 Not Found 1ms]
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713593
[HTTP/1.1 404 Not Found 1ms]
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713627
[HTTP/1.1 404 Not Found 0ms]
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713639
[HTTP/1.1 404 Not Found 1ms]
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713654
[HTTP/1.1 404 Not Found 0ms]
XHRGET
http://pc601.hkm.de:8080/primepush/valuesProduced?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.3.3-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&X-atmo-protocol=true&_=1529491713673
[HTTP/1.1 404 Not Found 1ms]

[tandraschko]

Sorry, i'm not good in atmosphere but it was always hard to get it running on different containers. Therefore i never used it. Also atmosphere (especially the fallbacks) isn't required anymore since all current browsers support websockets.
You can also use OmniFaces, the websocket component should be very similar to the JSF23 websocket.

[FkJ]

Sorry, i'm not good in atmosphere but it was always hard to get it running on different containers. Therefore i never used it. Also atmosphere (especially the fallbacks) isn't required anymore since all current browsers support websockets.
You can also use OmniFaces, the websocket component should be very similar to the JSF23 websocket.

Same problem with 6.2.5. I noticed that the context path of the application is missing on the generated web socket urls, generating these 404 errors on the console.

Could please take a look? Maybe it is something simple.

Thanks

[Melloware]

Try and look in the 6.2 changelog for anything that might have affected computing of a path?

You will probably have to debug this one maybe by comparing PF 6.1 to PF 6.2 source code for what changed and reporting it. But since its 6.2 you might have to have a PRO support account to get it fixed or patch the branch yourself.

[jfarcand]

@tandraschko I would appreciate if you stop spreading all over the place (github, here) TOTALLY false information about Atmosphere. I have hundreds of happy customers using Atmosphere + PF so please stop your false statement. Just take a look at your internal JIRA and you will see that you have customers that use Atmosphere in production.

PF + Atmosphere integration may have some regressions with 6.1 or 6.2, but was working perfectly fine before that.

[tandraschko]

@JF
sorry, i don't want to blame you or atmosphere, i just wanted to share my expierence as (probably bad) atmosphere user, not as PF dev.

I tried PF Push 2-3 years ago and i sadly needed to switch to plain atmosphere, which worked in my environment. Not sure what was the exact problem... was long time ago.
Today, I (as user) would use plain websockets with a small wrapper like OmniFaces/JSF23, as the fallback doesn't matter for me anymore and the programming model seems similar (between atmosphere and the JSR) and i probably only use basic features.

Removing Push was wheter influenced by me nor decided by me.
If just the path is wrong, it should be easily possible the overwrite the Socket/PushRenderer in the applications.
Also, the sourcecode of PF Push is still there (in the 6.2 tag), someone could easily extract it to an own module!

[Melloware]

@jfarcand. I think a "PrimeFaces-Atmosphere" library supported and run by the Atmosphere team might be the better place for the code that got removed in PF 6.3. There do seem to be advantages of PrimeFaces Push but PrimeTek no longer wanted to support it and our open source team (@tandraschko, myself, @Rapster) etc don't know enough about it to really make quality bug fixes.

And when out team did report Atmosphere defects it seems no one takes any action on them for example here are the two I reported...

https://github.com/Atmosphere/atmosphere/issues/2289

https://github.com/Atmosphere/atmospher ... issues/226

I know yours is a community based project but it's hard for PF to support a library when defects being reported are not being actioned.