[ https://issues.jboss.org/browse/RF-11156?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11156: --------------------------------- I assume the behavior which is Jura experiencing is caused by number of connections opened to server and server/browser connection is not closed right after aborting XHR long-polling request. The behavior is though not real world scenario and users can toggle the number of connections in application server configuration if needed. We can't generally change number of concurrent connections per session in Showcase example, so closing this issue as partially completed. Note that this affects only particular browsers and it is nothing we can do about. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira