Bug 1316960

Summary: (6.4.z) max-active-sessions in jboss-web.xml is not working
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Michael Cada <mcada>
Component: WebAssignee: Enrique Gonzalez Martinez <egonzale>
Status: CLOSED CURRENTRELEASE QA Contact: Radim Hatlapatka <rhatlapa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.7CC: bbaranow, bmaxwell, egonzale, jtruhlar, ppalaga, rmaucher
Target Milestone: CR1   
Target Release: EAP 6.4.12   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: eap6412-proposed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:13:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1375585    
Attachments:
Description Flags
Simple web app for session counting none

Description Michael Cada 2016-03-11 14:29:49 UTC 
Created attachment 1135257 [details]
Simple web app for session counting

Description of problem:

If you set

<jboss-web>
  <max-active-sessions>3</max-active-sessions>
</jboss-web>

in jboss-web.xml, property MAX_ACTIVE_SESSIONS is not set on 3.

But if you start EAP with
  ./standalone -Dorg.apache.catalina.session.StandardManager.MAX_ACTIVE_SESSIONS=3
it works.

You can use attached application for session counting, deploy it and from jboss-cli use:
      /deployment=something.war/subsystem=web:read-resource(include-runtime=true)
to see active-sessions.

URL for something.war session counter is http://localhost:8080/something/SessionAccessCounter

Expected result:
If you set max-active-sessions in jboss-web.xml it should set property MAX_ACTIVE_SESSIONS and all sessions over this number should be rejected.
Comment 1 Enrique Gonzalez Martinez 2016-03-16 11:50:51 UTC 
PR against 6.4.z 
https://github.com/jbossas/jboss-eap/pull/2733
no upstream required.
Comment 2 Mike McCune 2016-03-28 22:33:16 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 3 Michael Cada 2016-11-11 09:03:30 UTC 
Verified with EAP 6.4.12.CP.CR1
Comment 4 Petr Penicka 2017-01-17 13:13:33 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 5 Petr Penicka 2017-01-17 13:15:49 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.