Log and audit events
Portlet load monitoring creates log file entries in SystemOut.log. Entries contains the portlet object ID, the portlet name, the WAR file name of the portlet and the EAR file display name. The log file entries consist of translated messages. For tools that monitor log files for events, we can check for log file entries related to Portlet load monitoring as described here.
Portlet load monitoring creates log file entries for the events described in the following list.
- Portlet load monitoring blocks a portlet because the portlet exceeds the maximum number of requests.
- If Portlet load monitoring blocks a portlet because it exceeded the maximum number of concurrent requests specified for it, Portlet load monitoring creates the following log file entry with the message code EJPPG3001W:
- EJPPG3001W: Portlet load monitoring disabled the portlet with object ID: Object_ID, portlet name: Portlet_Name, WAR file name: WAR_File_Name, EAR file display name: EAR_File_Display_Name, because the portlet exceeded its maximum number of requests.
- Portlet load monitoring blocks a portlet because the portlet exceeds the average response time.
- If Portlet load monitoring blocks a portlet because that portlet exceeded the average response time specified for this portlet, Portlet load monitoring creates the following log file entry with the message code EJPPG3002W:
- EJPPG3002W: Portlet load monitoring disabled the portlet with object ID: Object_ID, portlet name: Portlet_Name, WAR file name: WAR_File_Name, EAR file display name: EAR_File_Display_Name, because the portlet exceeded its average response time.
- Portlet load monitoring activates a portlet because the portlet returns to the reactivation limit.
- If Portlet load monitoring reenables a blocked portlet because the blocked portlet falls back down to the reactivation limit of concurrent requests defined for the portlet, Portlet load monitoring creates the following log file entry with the message code EJPPG3003I:
- EJPPG3003I: Portlet load monitoring reenabled the portlet with object ID: Object_ID, portlet name: Portlet_Name, WAR file name: WAR_File_Name, EAR file display name: EAR_File_Display_Name because number of portlet requests fell below the reactivation limit.
- Administrator manually blocks requests to a portlet.
- If a portal administrator manually blocks requests to a portlet, Portlet load monitoring creates the following log file entry with the message code EJPPD0101I:
- EJPPD0101I: Portal administrator admin_user_ID manually blocked requests to the portlet with object ID: Object_ID, portlet name: Portlet_Name, WAR file name: WAR_File_Name, EAR file display name: EAR_File_Display_Name
- Administrator manually unblocks requests to a portlet.
- If an administrator manually unblocks requests to a blocked portlet, Portlet load monitoring creates the following log file entry with the message code EJPPD0100I:
- EJPPD0100I: Portal administrator admin_user_ID manually unblocked requests to the portlet with object ID: Object_ID, portlet name: Portlet_Name, WAR file name: WAR_File_Name, EAR file display name: EAR_File_Display_Name.
In the log entry, the variables Object_ID, Portlet_Name, War_File_Name, EAR_File_Dislay_Name, admin_user_ID are substituted with the corresponding values for the affected portlet and the administrative user.
Example: If Portlet load monitoring blocks a portlet with the portlet name StdWorldClock because the portlet exceeded the maximum number of requests allowed, then the log file entry might look like this:
EJPPG3001W:Portlet load monitoring disabled the portlet with ObjectID: [ObjectIDImpl '3_MLSU3F540O0360ISG212TT2003', PORTLET_DEFINITION, VP: 0, [Domain: rel], DB: 0000-B6723F5E2100836180E45004D1BB0060], portlet name: StdWorldClock, WAR file name: StdWorldClock.war, EAR file display name: PA_StandardWorldClock because portlet exceeded its maximum number of requests.