-
Bug
-
Resolution: Done
-
Critical
-
JWS 3.0.2 GA
-
None
-
Release Notes
-
-
-
-
-
-
This is verified and is a part of JBoss Core Services
-
This is the configuration that is breaking when hammered with many (~1000) concurrent requests:
LoadModule security2_module ${MODULE_HOME}/modules/mod_security2-jws3.so <IfModule security2_module> SecRuleEngine On SecCollectionTimeout 15 SecDataDir /dev/shm/modsec SecDebugLog /jws-3.0/httpd/logs/modsec-debug-GLOBAL-initcol.log SecDebugLogLevel 9 SecRule REQUEST_COOKIES:SESSIONID !^$ phase:1,id:110,nolog,pass,setsid:%{REQUEST_COOKIES.SESSIONID} SecAction phase:1,id:111,nolog,pass,setvar:SESSION.my_counter=+1 SecAction phase:1,id:112,nolog,pass,initcol:global=counter SecAction phase:1,id:113,nolog,pass,setvar:global.counter=+1 </IfModule>
The global "counter" and session "my_counter" should be equal. They should also be equal to the number of requests received by httpd in the 15 SecCollectionTimeout window.
- is cloned by
-
JBCS-156 It appears that the ModSecurity module sometimes fails to increment an integer in persistent storage when many concurrent transactions are sent to the Apache web server.
- Closed