Weblogic Apache plugin and session stickiness -
If two web servers are configured between a load balancer and a weblogic cluster, then will the two Apache server maintain the session viscosity ?
For example, to forward load balancers first Apache's first request and 1th Apache forward forward for 1 WL managed example. Regardless of the other requests of the same user, the load load is forwarded to the second Apache by the Balancer, the second Apache will be able to forward it to the 1 WLM angle instance, which was based on the first request rather than the second WL management, which There is no information about session information at all.
What should be the behavior of the Weblogic Apache plugin? I do not want to enable session replication on the wl server cluster.
section of Apache HTTP server plug-in: "
In one request, the session information stored in a cookie or in POST data, or a reference in the encoded session session in a URL is a specific server example in which the session was originally installed (called the primary server) and an additional The context of the server where the original session is repeated (called secondary server). Request a cookie attempt to connect to the primary server. If that attempt fails, the request is sent to the secondary server. If both primary and secondary servers fail, the session is lost and attempts to make plug-in attempts to create a new connection from another server in the dynamic cluster list. See.
Note: If the post data is larger than 64K, the plug-in will not parse POST data to get the session ID. Therefore, if you store session IDs in POST data, then the plug-in can not route the request to the correct primary or secondary server, resulting in potential loss of session data.
Image 3 - 1 connection failure
In other words, yes , Both Apache servers will be able to forward the incoming request "True" WebLogic example contains all the necessary information for that as session ID Note that there is no real need to confirm it with the test, but this is very much Will be easy
Update: Replying to the following comments from OP
I think this document is only good for an Apache server. I have two more load balancers in the 50:50 way to carry forward the requests of both servers. I did this test and the weblogic plugin does not maintain viscosity.
I understand that you are using two Apache fonts and I am not sure that this document applies only to the configuration of an Apache server as explained, session ID There is a reference to the primary server (and also the secondary server), so both Apache should be able to deal with it. At least this is my understanding. Actually, I have worked with the same configuration in the past but I can not remember if things were working like I think they want or if the load balancer is able to handle stickiness. Was configured (i.e. forward for a given Apache server). Now I have a little doubt ...
Your plug-in configuration (after separating the Apache server)? Can you also confirm that when only one Apache server is up (and test it with both the Apache if there is a difference in their configuration, which should not be the case)?
Comments
Post a Comment