Errors using the PrimeFaces socket component

[dparasam]

I am seeing the following errors when using the socket component.

Code: Select all

[2017-06-27T14:35:24.597-0500] [glassfish 4.1] [WARN] [] [org.jboss.weld.Context] [tid: _ThreadID=31 _ThreadName=http-listener-1(4)] [timeMillis: 1498592124597] [levelValue: 900] [[
  WELD-000225: Bean store leak was detected during org.jboss.weld.context.http.HttpRequestContextImpl association: com.sun.enterprise.web.pwc.connector.coyote.PwcCoyoteRequest@9d6b095]]

[2017-06-27T14:35:24.597-0500] [glassfish 4.1] [WARN] [] [org.jboss.weld.Context] [tid: _ThreadID=31 _ThreadName=http-listener-1(4)] [timeMillis: 1498592124597] [levelValue: 900] [[
  WELD-000225: Bean store leak was detected during org.jboss.weld.context.http.HttpSessionContextImpl association: com.sun.enterprise.web.pwc.connector.coyote.PwcCoyoteRequest@9d6b095]]

[2017-06-27T14:35:24.597-0500] [glassfish 4.1] [WARN] [] [org.jboss.weld.Servlet] [tid: _ThreadID=31 _ThreadName=http-listener-1(4)] [timeMillis: 1498592124597] [levelValue: 900] [[
  WELD-000715: HttpContextLifecycle guard not set. The Servlet container is not fully compliant.]]

The markup in the JSF page looks like:

Code: Select all

    <prime:socket channel="/myChannel">
        <prime:ajax event="message" update="@all"/>
    </prime:socket>

I have confirmed that adding the socket component like above is causing the errors. The push mechanism seems to work though, i.e. the components do get updated when the channel gets a message.

We have also (occasionally) noticed

java.io.IOException: java.lang.OutOfMemoryError: Java heap space

errors and wondering if above errors are related.

I was initially using Glassfish 4.1 (having Grizzly Framework 2.3.15 and Weld 2.2.2), and Atmosphere runtime 2.4.9 where I got these errors. I later upgraded to the latest Glassfish 4.1.2 (having Grizzly Framework 2.3.23 and Weld 2.2.13), and Atmosphere runtime 2.4.12 but go the same results.

How do I fix these errors?