How To Identify Portlet Name By Error Message (Doc ID 461248.1)

Last updated on MARCH 08, 2017

Applies to:

Portal - Version 10.1.4.0 to 11.1.1.6.0 [Release 10gR2 to FMW11g]
Information in this document applies to any platform.
***Checked for relevance on 08-MAR-2013***

Goal

In the midtier_home/j2ee/OC4J_Portal/application-deployments/portal/OC4J_Portal_default_island_1/application.log (11g - MIDDLEWARE_HOME\user_projects\domains\ClassicDomain\servers\WLS_PORTAL\logs\WLS_PORTAL-diagnostic.log), error messages may occur similar to the following.  In order to troubleshoot further the portlet that is failing, it's helpful to know the name of the portlet and the provider that the error message is referring to.

Sample error message:

07/10/02 14:16:32 portal: id=3384608555024,1 Stall Timeout reached. Interrupting Fetcher name=content-fetcher3100 label=dbPortlet
url=http://servername.com:7777/portal/pls/portal/!PORTAL.wwpro_app_provider.execute_portlet/789025757/17 time=16515ms timeout=16000ms process=Dispatching

 In the above error message, the failure is occurring on a portlet with the provider_id = 789025757 and portlet_id = 17.  Knowing the portlet name and provider name allows users to find these in the Portal Navigator and identify which portlet may be failing on a page so that further troubleshooting can be performed.

Solution

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