Status: Closed (View Workflow)
Affects Version/s: 4.5.0.Alpha3
Fix Version/s: 4.5.0.Beta2
JBoss AS 7.4.0.Final-redhat-12 (EAP 6.3)
Java(TM) SE Runtime Environment 1.7.0_25-b15 @ Linux
Chrome 36.0.1985.143 @ Linux x86_64
Same with latest FF, but Chrome has better verification tools in this case.
Sprint:4.5.0.Beta2 - Sprint 1
Steps to Reproduce:
Start EAP 6.3 Deploy Metamer/Showcase Whichever you prefer, both have similar push examples. In Chrome open dev tools Switch to 'Network' Use pre-defined filter 'WebSockets' Go to page with push Link to page in Metamer Link to page in Showcase As you enter the page in dev tools there should be a request but there is none If you clear the filter (to see all network activity) you can notice that new requests are constantly created - which is the old method without WebSockets
- Start EAP 6.3
- Deploy Metamer/Showcase
- Whichever you prefer, both have similar push examples.
- In Chrome open dev tools
- Switch to 'Network'
- Use pre-defined filter 'WebSockets'
- Go to page with push
- As you enter the page in dev tools there should be a request but there is none
- If you clear the filter (to see all network activity) you can notice that new requests are constantly created - which is the old method without WebSockets
When using push, connection should be established via WebSockets.
This does not happen and the old method is used. I also tried a workaround which was needed in earlier versions of EAP - manually enabling websockets.
I used EAP 6.3 and Metamer/Showcase. Please see steps to reproduce.
As for verification of WebSockets usage, Chrome dev tools can detect connection establishment as described here.