Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Applies To:: Symptoms Cause Solution References

    Uploaded by

    KoushikKc Chatterjee
    This document provides information about an incident (BEA-101020 [HTTP]) detected in the Enterprise Manager Grid Control alert log, including symptoms, cause, and solution. The incident occurs when particular links are accessed in Grid Control webpages and causes a response already committed error. Applying certain patches to the agent and adding a filter expression to the agent configuration file can suppress these harmless incidents and prevent unnecessary alerts. Manually clearing old alerts from the Grid Control user interface is also suggested.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Applies To:: Symptoms Cause Solution References

    Uploaded by

    KoushikKc Chatterjee
    23 views3 pages
    This document provides information about an incident (BEA-101020 [HTTP]) detected in the Enterprise Manager Grid Control alert log, including symptoms, cause, and solution. The incident occurs when particular links are accessed in Grid Control webpages and causes a response already committed error. Applying certain patches to the agent and adding a filter expression to the agent configuration file can suppress these harmless incidents and prevent unnecessary alerts. Manually clearing old alerts from the Grid Control user interface is also suggested.

    Original Description:

    Original Title

    Document 1139600 java 04

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides information about an incident (BEA-101020 [HTTP]) detected in the Enterprise Manager Grid Control alert log, including symptoms, cause, and solution. The incident occurs when particular links are accessed in Grid Control webpages and causes a response already committed error. Applying certain patches to the agent and adding a filter expression to the agent configuration file can suppress these harmless incidents and prevent unnecessary alerts. Manually clearing old alerts from the Grid Control user interface is also suggested.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    23 views3 pages

    Applies To:: Symptoms Cause Solution References

    Uploaded by

    KoushikKc Chatterjee
    This document provides information about an incident (BEA-101020 [HTTP]) detected in the Enterprise Manager Grid Control alert log, including symptoms, cause, and solution. The incident occurs when particular links are accessed in Grid Control webpages and causes a response already committed error. Applying certain patches to the agent and adding a filter expression to the agent configuration file can suppress these harmless incidents and prevent unnecessary alerts. Manually clearing old alerts from the Grid Control user interface is also suggested.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 3

    10/30/13 Document 1139600.

    Incident (BEA-101020 [HTTP]) detected in


    .../user_projects/domains/GCDomain/servers/EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml (Doc ID
    1139600.1)
    Modified: 06-Dec-2012 Type: PROBLEM

    In this Document

    Symptoms
    Cause
    Solution
    References

    APPLIES TO:

    Enterprise Manager for Fusion Middleware - Version 11.1.0.1 to 11.1.0.1


    Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
    Information in this document applies to any platform.

    SYMPTOMS

    In Enterprise Manager Grid Control 11g, the below alert is reported:

    Incident (BEA-101020 [HTTP]) detected in


    <>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml at time/line
    number: Fri Jun 4 18:22:01 2010/809

    Navigation: Login into Grid Control > Alerts > Critical

    Here are more details about this incident from the ADR incident readme.txt:

    Incident Id: 93
    Incident Source: SYSTEM
    Create Time: Thu Jun 17 08:37:27 EDT 2010
    Problem Key: BEA-101020 [HTTP]
    Application Name: emgc
    Error Message Id: BEA-101020

    Description
    Incident detected using watch rule "UncheckedException":
    Watch time: Jun 17, 2010 8:37:27 AM EDT
    Watch ServerName: EMGC_OMS1
    Watch RuleType: Log
    Watch Rule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    Watch DomainName: GCDomain
    Watch Data:
    DATE : Jun 17, 2010 8:37:27 AM EDT
    SERVER : EMGC_OMS1
    MESSAGE : [ServletContext@1872056488[app:emgc module:/em path:/em spec-version:2.5]] Servlet failed with Exception
    java.lang.IllegalStateException: Response already committed
    at weblogic.servlet.internal.ServletResponseImpl.objectIfCommitted(ServletResponseImpl.java:1591)
    at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:614)

    at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
    at oracle.sysman.eml.app.EMResponseWrapper.sendError(EMResponseWrapper.java:78)
    at oracle.sysman.core.app.exception.EMRuntimeExceptionFilter.doFilter(EMRuntimeExceptionFilter.java:102)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:502)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at racle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1cy0ssk2k1_250&id=1139600.1 1/3
    10/30/13 Document 1139600.1
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    SUBSYSTEM : HTTP
    USERID : <WLS Kernel>
    SEVERITY : Error
    THREAD : [ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'
    MSGID : BEA-101020
    MACHINE : <hostname>
    TXID :
    CONTEXTID :
    TIMESTAMP : 1276778247377

    Stack Trace
    java.lang.Throwable
    at oracle.dfw.impl.incident.DiagnosticsDataExtractorImpl.createIncident(DiagnosticsDataExtractorImpl.java:231)
    at oracle.dfw.spi.weblogic.JMXWatchNotificationListener.handleNotification(JMXWatchNotificationListener.java:195)
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1732)
    at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
    at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322)
    at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307)
    at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229)
    at weblogic.management.jmx.modelmbean.WLSModelMBean.sendNotification(WLSModelMBean.java:824)
    at weblogic.diagnostics.watch.JMXNotificationProducer.postJMXNotification(JMXNotificationProducer.java:79)
    at weblogic.diagnostics.watch.JMXNotificationProducer.sendNotification(JMXNotificationProducer.java:104)
    at com.bea.diagnostics.notifications.JMXNotificationService.send(JMXNotificationService.java:122)
    at weblogic.diagnostics.watch.JMXNotificationListener.processWatchNotification(JMXNotificationListener.java:103)
    at weblogic.diagnostics.watch.Watch.performNotifications(Watch.java:621)
    at weblogic.diagnostics.watch.Watch.evaluateLogRuleWatch(Watch.java:546)
    at weblogic.diagnostics.watch.WatchManager.evaluateLogEventRulesAsync(WatchManager.java:765)
    at weblogic.diagnostics.watch.WatchManager.run(WatchManager.java:525)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    CAUSE

    This occurs when a particular link(s) is/are accessed in Grid Control webpages. These have been reported in multiple bugs.

    SOLUTION

    If the errors and incident stack is exactly same, then this incident can be ignored. This is harmless and has no functional impact.

    To suppress these incident(s) Enterprise Manager Grid Control alerts from occurring, follow the below action plan:

    1. Apply Patch 9882856 in the AGENT_HOME monitoring the target for which the alert was raised.
    2. Refer Patch readme for further instructions.
    3. A filter expression similar to the database 10g Alert Log Filter expression in Note 949858.1 has to be created.

    .*BEA-(101020)\D.* - Any string


    .*BEA-(101020)\D.* - Followed by the string â​
    BEA-â​
    ​ ​
    .*BEA-(101020)\D.* - Then 101020
    .*BEA-(101020)\D.* - Followed by anything other than a digit
    .*BEA-(101020)\D.* - Followed by any string

    Which translates to the following errors:


    BEA-101020
    4. To add this filter expression, edit the AGENT_HOME/sysman/config/emd.properties file, add:

    adrAlertLogAsErrorCodeExcludeRegex=.*BEA-(101020)\D.*

    If you want to have a filter expression which ignores multiple incident, then the parameter value would be as below:

    adrAlertLogAsErrorCodeExcludeRegex=.*(BEA-(101020|567|6657)|OFM-(99999))\D.*

    Note: There should be no spaces.

    This will make sure that the WLS incidents that match this regex are filtered.
    5. Restart agent.

    The fix of Bug 9882856 is included from Grid Control Patch Set Update 11.1.0.1.2 (PSU 2) for Agent. For more details about Grid Control PSU, refer Note
    822485.1

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1cy0ssk2k1_250&id=1139600.1 2/3
    10/30/13 Document 1139600.1

    To manually clear the existing or old alerts about [..]EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml from Enterprise Manager Grid Control
    User Interface / webpage, apply Patch 9914120

    Patch 9882856 with the above filter will suppress the BEA-101020 incidents, created by the WLS server from being reported in Enterprise Manager Grid Control,
    but these would still be created in the Support Workbench page only.

    1. Display the WebLogic Server Administration Console


    2. In the Change Center, click Lock and Edit.
    3. In the left pane, expand Diagnostics and select Diagnostic Modules. The Summary of Diagnostic Modules page is displayed
    4. Click Module-FMWDFW. The Settings for Module-FMWDFW page is displayed.
    5. Select the Watches and Notifications tab
    6. Select the "UncheckedException" Watch
    7. Click Delete

    More information can be found in section 12.3.2 of the FMW PS1 Administrators Guide located here

    REFERENCES

    BUG:9850707 - GRID CONTROL 11G TAKE 35 MINUTES TO COMPLETELY START UP

    BUG:9757048 - BEA-101020 WLS ALERTS FOR GC11G ON RH5


    BUG:9761800 - METRIC COLLECTION ERROR INCIDENT (BEA-101020 [HTTP]) DETECTED IN
    BUG:9782364 - /CONSOLE/DATABASE/CONFIG CAUSES JAVA.LANG.ILLEGALSTATEEXCEPTION: RESPONSE ALREAD
    BUG:9804936 - RECEIVING BEA-101020 [HTTP] IN EMGC-OMS1 MANAGED SERVER
    BUG:9856570 - METRIC COLLECTION ERROR INCIDENT (BEA-101020 [HTTP]) DETECTED IN
    BUG:9882856 - FIX REQUIRED TO SUPPRESS INCIDENTS REPORTED IN WLS TARGETS
    NOTE:822485.1 - Oracle Recommended Patches -- Enterprise Manager Base Platform 10.2 to 11.1.0.1
    PATCH:9882856
    PATCH:9914120

    https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=1cy0ssk2k1_250&id=1139600.1 3/3

    You might also like