I had this exception raised: com.businessobjects.sdk.core.CoreException on my BI4.1 SP07 a while ago due to my configuration on WIReportServers to share the same Output Cache Directory using NAS.
I finally got the proof from the Webi tracing logs shows that the disk cache file is causing the Webi exception, com.businessobjects.sdk.core.CoreException.
|79a41e4e-13a8-35f4-6971-86eb53aa5763|2016 04 01 11:31:01:022|-0700|Debug| |<<| | |webiserver_WAPP847R.WebIntelligenceProcessingServer|39820|54896||}|0|1132|0|2|-|-|-|-|-|-||||||||||||GenericContainer_PollingThread:run:pluginPollingEvent: 0.016‑
- PollingThread.cpp:301:void __cdecl PollingThread::run(void): TraceLog message 429026
|1377875d-748e-bca4-fb6f-c68fe9d1c644|2016 04 01 11:31:01:022|-0700|Error| |>>|E| |webiserver_WAPP847R.WebIntelligenceProcessingServer|39820|54896|| |0|1133|0|1|-|-|-|-|-|-||||||||||||**ERROR:GenericContainer_PollingThread:polling threads don't terminate in expected timeframe, aborting [PollingThread.cpp;301]‑
See SAP KB 2057341 - Web Intelligence Processing Server Restarts due to threads being blocked for an extended period of time on http://service.sap.com/sap/support/notes/2057341 and 2052588 - Web Intelligence cache is growing continuously beyond the set value if the Output Cache Directory location is specified as a Network drive/UNC path
Symptom
- Web Intelligence Processing Server restarts at random
- Scheduled and run-on-demand reports display WIS 30270 or WIS 30111 if sessions are active when the server restarts
- In the logs the following line can be observed immediately prior to the restart
- **ERROR:GenericContainer_PollingThread:polling threads don't terminate in expected timeframe, aborting [PollingThread.cpp;301]
Environment
- SAP BusinessObjects Business Intelligence 4.0
- SAP BusinessObjects Business Intelligence 4.1
Cause
A thread on the WebI Processing Server has been blocked for an extended period of time and the server restarts itself to resolve the issue
Resolution
Determine the locked thread by determining which thread stays alive through eight polls, which are logged prior to the line "GenericContainer_PollingThread:watchdog retries: #/8"
If the hung thread in question is polling for CTPlugin, then the issue may be caused by the Web Intelligence Processing Server "Output Cache Directory" setting pointing to a network share. Repointing the "Output Cache Directory" to a disk local to the Web Intelligence Processing Server has resolved this issue for several deployments.
Therefore, the resolution is to set Webi output cache to their host local disk instead of NAS share folder.
Regards,
Jin-Chong