Topic: Issues Migrating WL Proxies from IPlanet 6.1 to Ap 2.4

[jamuller]

I am working on a project to migrate all our IPlanet 6.1 SP19 webserver proxies (formerly Sun One) to Apache 2.4, since IPlanet 6.1 does not support TLS 1.2 and IPlanet 7.0 is being EOL. Our backend application servers are Weblogic 9.2 / Weblogic 12c. The IPlanet proxies have performed FLAWLESSLY for over 10 years, despite the product being no longer supported and the WL Plug-in not officially supported with Weblogic 12c.

However now that we are trying to use a more supported configuration (self-compiled Apache 2.4.18 running Weblogic Server Plugin 12.1.3) we are constantly seeing these errors, which results in performance degradation for our applications, and in some cases I think maybe even lost data.


[Tue Jun 14 09:27:36.239682 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> Write to the client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM

[Tue Jun 14 09:27:36.239747 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> **
*****Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of BaseProxy.cpp, referer: https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM

[Tue Jun 14 09:27:36.239952 2016] [weblogic:error] [pid 12513:tid 140185150932736] [client 10.165.254.1:28171] <1251314659108487> request [/ALFA/servlet/DecryptDownload?linkName=al_o1mm_carr20150630.csv] did NOT process successfully.................., referer:https://intgalf.xyz.com/ALFA/selectFileType.do?fileType=O1MM



Our topology is like this:

Client Browser <--> Firewall <--> Load Balancer <--> Web Proxies <--> Firewall <--> Weblogic Application Servers

Oracle support suggested as work around that we increase WLSocketsTimeOut in the plug-in, but I think that only masks the issue, as we still the errors.

We did a network trace and it looks like Apache is pre-maturely closing the connection to the WL server, but I can't be certain. We know that our firewall is not responsible.

Any ideas ? I thought Apache would work better then Sun One, but this has been the opposite. Is there some fundamental webserver tunable parameter that is so different between out of the box Sun One and out of the box Apache that could be causing this ?

[James Blond]

The weblogic plugin is not "native" apache, but a third party module. Apache itself offers mod_proxy_http (http://), mod_proxy_connect (https://) and mod_proxy_ajp ( ajp://). Is it an option not to use the mod_wl plugin but a native one?

Googling suggests that it is firewall timeout problem see https://community.oracle.com/thread/3889059?start=0&tstart=0