JBoss EAP 6.3 Vaadin Push Firefox Problems


I have two problems with using Vaadin push in combination with firefox. The following problems ar ONLY occurs with firefox.
Internet Explorer 9 and Chrome 36 works great. After Problem 2 occurs Vaadin push still works but the exception fills my jboss log.

Problem 1:
When I close Firefox the following exception throws:
08:12:48,171 SEVERE [vaadin org.atmosphere.container.JSR356Endpoint]
(http-d00212362wp.ads.provinzial.com/ : java.io.EOFException
at org.apache.catalina.core.StandardWrapperValve.async(StandardWrapperValve.java:555) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:350) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:171) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:247) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:121) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:228) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.coyote.http11.Http11NioProcessor.event(Http11NioProcessor.java:231) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Http11NioProtocol.java:818) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:935) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]

at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]

Problem 2:
When I refresh Friefox with shortcut F5 I get the following exception:
No UI was found based on data in the request, but a slower lookup based on the AtmosphereResource succeeded. See http://dev.vaadin.com/ticket/14251 for more details.

The ticket describes that the problem was fixed, so why I get this error?

JBoss EAP 6.2
Websocket enable by following guide:
Vaadin 7.2.6
PushMode auto
PreserveOnRefresh on
Firefox 31
Chrome 36
Internet Explorer 9
Windows 7 64bit

@WebServlet(value = “/*”, asyncSupported=true)
@VaadinServletConfiguration(closeIdleSessions = false, productionMode = false, heartbeatInterval = 100, ui = UIClass.class, widgetset = “XXX”)

Thanks for any help.

Hi Jan R,

sorry for posting on this thread, but I’ve a problem with JBoss EAP 6.3.0 and WebSockets, maybe you can help me…

I’ve enabled NIO2 connector on JBoss, as stated in the guide you linked above and added the tag true on my jboss-web.xml, but FF and Chrome keeps telling me that WebSockets are not enabled, and Atmosphere is failing back to Comet.

Have you done some other configurations for making WebSockets working with Atmosphere?

Thank You,

Hi Antlia,
my jboss-web.xml under MyVaadinProject/WebContent/WEB-INF


You have to replace the connector tag in the standalone.xml of jboss eap!
Than add the Annotation @Push to the UI Class of your Vaadin Project.
After that check if push is mention in your ivy.xml.
Then recompile your widgetset.

Suggestion of someone else to my topic?

Hi to all,

finally I got WebSocket working on EAP 6.3.0 and I confirm that, even with Vaadin 7.3.0 the problem related to the above-mentioned ticket is still there…the only way to get it out is using the workaround in the ticket, overriding the refresh method and manually checking if the push connection is still connected.

Hi, the log message is there just to remind that the fix for #14251 is just a workaround for the underlying issue. Everything should still work even if you get the message. You can get rid of the message by configuring java.util.logging to not log INFO level messages from PushHandler: