Load Balanced GAD Hourglass on Login

Hello Everyone,
I have been scratching my head on this one for over a day now. I have just installed GAD and Apache in a Load Balaced configuration across 2 servers and get the endless hourglass uppon logging on via the Apache URL. I get logged in with no problems when I log in directly to the GAD instance via the URL with port number. Here is my setup…

GAD Server A has Apache and 3 GAD Instances
GAD Server B has Apache and 3 GAD Instances
Each Apache is configured with compression, caching, and loadbalancing across all 6 GAD instances.
I have tried turning compression and caching off and I have tried reducing the load balance to each respective servers GAD instances. I experience the same problem on both Apache servers. I can hit the URL and get the login screen of one GAD. I can also login properly. But when the next frame opens, I get then endless hourglass. If I hit the F5 key the page does come up. I have cleared my browsers temp, cookies, etc…
I am stumpped here. The Apache logs indicate that I might be getting a 403 error. From what I can tell, the initial request to log in happens on one instance of GAD and the susiquent pages are attempting to come from another GAD. I have verified that Sticky Sessions is True in Apache. Has anyone had this happen to them?
I appreciate any assistance.
Thanks,
Perry

In case anyone is interested… Patient Heal Thy Self…
The most certain way to clear this is to delete the .JAVA and .CLASS files from the work/catalina/… folders. Then perform a “Check JSP Files” in the GAD Admin page. This will force the rebuild of these files. You might not need to delete the files but I wanted to make 100% certain they got created from scratch.

Thanks,
Perry