Error "Portlet Could Not Be Contacted" with Reverse Proxy and Load Balancer (Doc ID 452728.1)

Last updated on DECEMBER 08, 2016

Applies to:

Portal - Version 10.1.2.0.2 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.

Symptoms

After configuring multiple middle tiers behind a reverse proxy and a load balancer, there are many error messages like these in the portlets:

Portlet could not be contacted

In the same time the following error message is logged in the Portal's application.log:

portal: id=92743780452,1 ContentFetcher Unexpected Exception Request
Failed:java.net.SocketException: Connection reset name=content-fetcher7 label=pagePortlet
url=http://<host>:<port>/portal/page/portal?_mode=10&_cpage_id=1&_csite_id=6&_cstyl
e_id=1&_cstyle_site_id=6&_ccalledfrom=1&_cmode=3&_ctabstring=Build&_cdisplay_name=Portal%20Builder
time=155ms timeout=65000ms process=GotResponse


Steps To Reproduce:

  1. Set up multiple middle tiers behind a reverse proxy and a load balancer
  2. Notice that the Portal is slow and some portlets show the following error message:
    Portlet could not be contacted

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms