Skip to main content

Pulling from some archival problems I’ve had in the past, I figured I should share them and their solutions here in case others are racking their brains on them.

A while back I upgraded an OAM 11gR2 (11.1.2.0) environment to OAM 11gR2PS2 (11.1.2.2) and everything stopped working. More specifically, when I would send a request for a protected URL to my reverse proxy, they would all timeout and dump with a 404.

One thing that I noticed was that when I would request http://something.com/app, I would be instantly bounced to httpS://something.com/app. This was our load balancer front-loading SSL to all the requests which has always been working. So first step was to disable that so all requests would be regular HTTP for testing purposes.

This seemed to work, except now when I’m presented with my login form, all the artifacts are missing (no images, styles gone, etc). Running a fiddler, you would see that all these requests ended with a 504 (timeout). WTF?

I would then bypass the load balancer all together via my local hosts files and everything worked fine.

Turns out that the upgrade to patch set 2 changed the header lengths of all the requests to 4112 bytes, which was over the 4096 default, causing packets to be dropped.

Made the change to the packet size, re-enabled SSL and all is well.