[
https://issues.jboss.org/browse/RF-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793529#comment-12793529
]
nathan dennis commented on RF-13109:
------------------------------------
apache 2.2.15-28
Mod JK 1.3
centos 6.4 final
kernel 2.6.32-358.11.1.el6.x86_64
java version "1.7.0_25"
OpenJDK Runtime Environment (rhel-2.3.10.3.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
<VirtualHost 10.2.8.2:80>
ServerAdmin "[email protected]"
ServerName a4jpushflood.localhost
ErrorLog /var/log/httpd/forms_errmr_log
JkMount /* ajp13w
DocumentRoot "/"
<Directory "/home/nbd/public_html">
Options +Indexes +FollowSymLinks
Order allow,deny
Allow from all
AllowOverride All
</Directory>
<Location /usage>
Order allow,deny
Allow from all
</Location>
</VirtualHost>
worker.list=wlb,jkstatus,ajp13w
#
#
# Defining a worker named ajp13w and of type ajp13
# Note that the name and the type do not have to match.
#
worker.ajp13w.type=ajp13
worker.ajp13w.host=10.2.8.2
#
# Defining a load balancer
#
worker.wlb.type=lb
worker.wlb.balance_workers=ajp13w
#
# Define status worker
#
worker.jkstatus.type=status
> a4j:push transaction flood
> ---------------------------
>
> Key: RF-13109
> URL: https://issues.jboss.org/browse/RF-13109
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1
> Environment: CHROME,Jboss 7.1.1.Final, Jboss 7.1.3.Final, CentoOS6.X,
> Windows 7
> Reporter: nathan dennis
> Labels: a4j:push, richfaces
> Attachments: a4jPushFlood.tar.gz
>
>
> long poll doesnt refresh at the 30 second mark. After 5 minutes, Chrome goes
> into meltdown, sending a transaction back to the server approx. ever 8 ms
> causing DOS and browser lock after about 3 seconds.
> Firefox on the other hand returns a cancelled transaction, exits abnormally,
> and goes back to behaving as expected with the appearance that it is working
> correctly.
> This took me forever to find out why this was happening as I couldn't
> replicate it with the showcase code... or the test project i built
> specifically for figuring this out. In the end I was removing one component
> at a time until it started working.
> The cause of the issue is found in the jboss-web.xml file. For years, I have
> ran apache in front of my jboss installations. I would specify root context
> to / and map the domain straight to it using a virtual host in the jboss
> server config file (regardless of the version). AJP in front and away you go.
> a4j:push will crash if this context is mapped to / instead of /foo.
> I'm going to attempt to attach the sample project to recreate this with. Map
> the alias from jboss-web.xml to a virtual server in your standalone.xml file
> and start it up. navigate to the consumer link at the top of the app. turn on
> your developer tools and wait for the chaos. at the five minute mark you are
> going to see death and destruction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
