Bug 865369 - [HTTP Connectors Load Balancing Guide]: Session replication doesn't works with Tomcat
[HTTP Connectors Load Balancing Guide]: Session replication doesn't works wit...
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: doc-HTTP-Connectors-Guide (Show other bugs)
2.0.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Misha H. Ali
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-11 05:50 EDT by Jan Stefl
Modified: 2012-11-08 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-08 17:10:49 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Stefl 2012-10-11 05:50:30 EDT
http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Web_Server/2/html/HTTP_Connectors_Load_Balancing_Guide/Apache_HTTP_Overview.html

Following text (all about session replication) is valid for EAP and not for EWS. Should be removed.

{remove}
HTTP session replication is used to replicate the state associated with web client sessions to other nodes in a cluster. If one node becomes unavailable, another node in the cluster takes the load of the disabled node. Two distinct functions must be performed:

Session state replication
Load-balancing HTTP Requests

Sessions state replication is handled by JBoss at the application level.
Load balancing, however, requires an external load balancer. A cost effective way of managing load-balancing is to set up a software load balancer using Apache httpd and mod_jk.
{remove}
Comment 1 Misha H. Ali 2012-10-11 18:23:30 EDT
The overview no longer contains these paragraphs. This bug will be set to ON_QA when the results appear on the stage.
Comment 2 Misha H. Ali 2012-11-08 17:10:49 EST
This bug is set to CLOSED CURRENT RELEASE to indicate that this fix is now released and available at access.redhat.com.

Note You need to log in before you can comment on or make changes to this bug.