Databases Reference
In-Depth Information
To debug the
ActiveDataServlet
related issues, set the
ActiveDataSer-
vlet
logger to
TRACE:32 (FINEST)
, and then search the
ActiveDataSer-
vlet
keywords to look for the information.
The following is an example of the logs produced by the ActiveDataServlet ser-
vlet:
doRequest: Method = POST; URL = http://bamhost1:9001/OracleBAM/ActiveDataServlet; Query = null; Session ID = nls4PB8CpvJ3L KkqvJ1LGG2pp1qMBnTYhTyPtXV3n2xnDF2Qr8n5!1135941767!1325513922380; Is Session Valid = true; Is Session From Cookie = true; Is Session From URL = false
Right after a new report/dashboard is rendered for the first time, it sends an
HTTP POST
request to the
ActiveDataServlet
, which registers the client
(report/dashboard) to ensure it gets called back when the Active Data arrives at
the Report Server in the future. Therefore, the previous message typically ap-
pears at this time frame, and can be used to troubleshoot the client/server com-
munication issues.
Troubleshooting the Active Data Cache and the Report
Cache
The following are the scenarios in which you should consider turning on loggers
to troubleshoot Active Data processing in the Active Data Cache or the Report
Cache:
•
The
ActiveDataPage flushAllActiveData
method is never called to
push the Active Data to the client.
•
The
ActiveDataPage flushAllActiveData
method is invoked,
however, the parameters passed to this method are incorrect. For example,
the XML payload for the
ChangeList
is incorrect.
•
The error messages in the
log
file indicate that the errors happen in one of
the
oracle.bam.adc.*
or
oracle.bam.reportcache.*
modules.
The following table lists the common loggers for the Active Data Cache and the
Report Cache:
