DSauve
Legendary Poster
Oracle Web Cache not load balancing WebLogic JVM\'s
We're getting ready to upgrade our TR to 9.1.0.2, and as part of this have changed from OAS to WLS. For our 9.1.0.2 setup, we have two web servers that we use Windows NLB on, which is working fine, and points to port 80. Port 80 on each of the servers is being serviced by Oracle Web Cache, which is set up in load balancing mode to farm its requests out to one of two WLS JVM's on that same server.
The problem we run into is that the Oracle Web Cache seems to develop a preference for one of the JVM's on each server, and once it makes a connection to one of the JVM's, it routs all requests to that JVM. This basically leaves one JVM on each server sitting there doing nothing, and give us only half the JVM's to service all our users.
I have had an SR open with Oracle support on this issue since March, and have escalated it, but with no resolution.
Does anyone have any ideas on why Web Cache would be working this way?
We're getting ready to upgrade our TR to 9.1.0.2, and as part of this have changed from OAS to WLS. For our 9.1.0.2 setup, we have two web servers that we use Windows NLB on, which is working fine, and points to port 80. Port 80 on each of the servers is being serviced by Oracle Web Cache, which is set up in load balancing mode to farm its requests out to one of two WLS JVM's on that same server.
The problem we run into is that the Oracle Web Cache seems to develop a preference for one of the JVM's on each server, and once it makes a connection to one of the JVM's, it routs all requests to that JVM. This basically leaves one JVM on each server sitting there doing nothing, and give us only half the JVM's to service all our users.
I have had an SR open with Oracle support on this issue since March, and have escalated it, but with no resolution.
Does anyone have any ideas on why Web Cache would be working this way?