So a few minutes after the app has been deployed I get an overload in the available request threads and apache stops serving my app.
The image bellow shows some of those requests as viewed in the /server-status monitoring page:
The total requests currently being processed number keeps increasing (it never gets smaller), and once it achieves the maximum (250) apache stops working....Server uptime: 3 hours 22 minutes 24 seconds
Total accesses: 2511 - Total Traffic: 29.4 MB
.207 requests/sec - 2537 B/second - 12.0 kB/request
124 requests currently being processed, 126 idle workers
I'm using Primefaces 3.5.14 with Atmosphere 1.0.8. My web server is JBoss 7.1.1.
This is my servlet config in web.xml
Code: Select all
<servlet>
<servlet-name>Push Servlet</servlet-name>
<servlet-class>org.primefaces.push.PushServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
<init-param>
<param-name>org.atmosphere.websocket.maxTextMessageSize</param-name>
<param-value>0</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useWebSocket</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.cpr.sessionSupport</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useNative</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.resumeOnBroadcast</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.cpr.broadcasterCacheClass</param-name>
<param-value>org.atmosphere.cache.HeaderBroadcasterCache</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.cpr.broadcastFilterClasses</param-name>
<param-value>org.atmosphere.client.TrackMessageSizeFilter</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useBlocking</param-name>
<param-value>true</param-value>
</init-param>
</servlet>