Oracle Web Cache not load balancing WebLogic JVM's

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?

Re: Oracle Web Cache not load balancing WebLogic JVM\'s

Did you ever make any progress on this?

Re: Oracle Web Cache not load balancing WebLogic JVM\'s

We finally scrapped Oracle Web Cache, and implemented our own home-grown rudimentary mechanism to distribute PC's to each of our different JVM's. Nothing fancy, but it works for us.

By the way, we also tried to use a Barracuda load balancer, but without any luck there, either.

Re: Oracle Web Cache not load balancing WebLogic JVM\'s

Hi Don,

Are your users usign their local IE to access your E1 infrstructrure or IE published via Citrix. Do you have any rule defined( like source address affinity etc) that could prefer one server over others..

Re: Oracle Web Cache not load balancing WebLogic JVM\'s

Jaise,

Yes, our users use their local IE to access E1. We have a script that runs when a user logs into our network, which changes their JDE icon to a specific JVM, based upon the alphabetic name of their machine name. Like I said, nothing fancy, but it works well enough for us.