Hello David, you have raised this as a question but it is not clear what your question is. JBoss AS 7.1.3 is now quite an old release, our most recent release is WildFLy 8.1.0.CR1 which amongst other things contains a replacement web server, I would suggest you try upgrading and see if your issue is still present.
I try on JBoss EAP 6.1.0 Alpha and I have the same problem.
I could try on this Wildfly release as a test and I will give you a feedback.
My question is : do you have any idea on what this comportment can be? Any parameter on http connector? Other?
1 of 1 people found this helpful
There is not a specific setting I am aware of others may have some suggestions.
Personally if I was to investigate a set up that experiences a 30 second delay as you describe I would probably start with some network traces and take a few thread dumps of the server during the pause and probably one before and one one after to see if a point of contention can be identified.
As this is multiple tabs within a web browser there are two areas I would consider: -
- All the tabs are going to be sharing the same underlying HTTP session.
- The web browser is more than likely maintaining one or more keep alive connections to the server so it could be the sharing of these across 6 tabs causing the issue.
I found the problem...Nothing about JBoss (how could I have doubted about it )
It's all about RichFaces Push, Firefox / Chrome and the parameter "max persistent connections per server" (by default a value of 6)
FYI, RichFaces Push uses Atmosphere (version depends on RichFaces version...) and Atmosphere uses a "keep alive" request (so a persistent request...) and its duration is 30 seconds by default...
Useful links :
To change this parameter on Firefox : URL : about:config and find the parameter "network.http.max-persistent-connections-per-server".
Thank you for your time and your quick answer.