Crashing WEBI 4.1SP2FP3

Question

Hi all. Very strange issue that 100 percent correlates BI updating. Update 2008R2SP1 64bit environment from BI 4.1SP1FP2 to 4.1SP2FP3. Immediately following the update I experienced a very strange with WEBI (HTML). No matter what is being done with any WEBI report, creating, editing, viewing or whatever, after a very short period of inactivity the next mouse click after the inactivity will yield com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: FatalException occured. The cause was : com.businessobjects.corba.generic.container.proxy.internal.DependencyFailoverCallbackImpl$FailoverFatalException: Prepare failover failed. See attached screen shot.
As I mentioned this occurs with a any thing related to WEBI operations. The short period of inactivity that I mentioned seems to be right around a minute give or take a few seconds. As long as you are interacting with WEBI no problems. I have worked for over an hour with no problems, take a two minute phone call and its all over. I have many users with read only rights and they experience the same issues after a short time with no activity. This is not a session time out as there is no warning that session is about to end or no other friendly warnings. This issue was not present prior to updating to SP2FP3. I don't know very much at all about tomcat7 but I did find the error described above in my tomcat stderr.log. I have tested many reports on the desktop (thick client) and everything works fine there. I can leave a report open for hours with no problems. This poor behavior is limited strictly to WEBI (HTML). All other platform features are fine including the launch pad its self which will session time out normally. My tomcat settings did not change post upgrade and we are and have been using these configs for over a year. These config options were loaded by a vendor who put our system together:
-Djava.library.path=C:\Windows\SysWOW64\;C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\
-Dcatalina.base=C:\Program Files (x86)\SAP BusinessObjects\tomcat\
-Dcatalina.home=C:\Program Files (x86)\SAP BusinessObjects\tomcat\
-Djava.endorsed.dirs=C:\Program Files (x86)\SAP BusinessObjects\tomcat\common\endorsed\
-Dbobj.enterprise.home=C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\
-Xrs
-XX:MaxPermSize=512M
-Dbusinessobjects.olap.bin=
-Dbusinessobjects.olap.stylesheets=
-Djava.awt.headless=true
-XX:+HeapDumpOnOutOfMemoryError
-Xloggc:C:\Program Files (x86)\SAP BusinessObjects\tomcat\logs\tomcat.gc.log
-XX:+PrintGCDetails
-XX:+UseParallelOldGC
Initial Memory Pool BLANK MB
Maximum Memory Pool 2048 MB
Thread stack size 1024 KB
Is there something that could have changed in my WEBI processing servers in the upgrade process? Again nothing on the rest of the platform exhibits this ill behavior. I only mentioned tomcat because that is the only place that where the error thrown by WEBI shows up in a log.
Thank you for any advice anyone may have
have a good day

Answer 1

Josh,
Here is a cut from the last portion of recent trace log.
|92111bf9-cc22-b164-f866-a6f79c6b9718|2014 03 19 20:18:17:831|-0600|Error| |>>|E| |webiserver_KMGBKMMSDATA.WIP.Master|12260|14940|| |1|0|1|0|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|webiserver_KMGBKMMSDATA.WIP.Master.createSession|localhost:12260:14940.40460:1|CvnfsjwWLk18kqaRyc.ln0w887|||||||||||**ERROR:ServerLifeCycleManager:Info: Sessions in state DELETED: 0 [ServerLifeCycleManager.cpp;1150]
ServerLifeCycleManager.cpp:1150:void __cdecl ServerLifeCycleManager::dumpContextOnError(void): TraceLog message 814908
|4a6247de-ff22-e5d4-9949-a7956fd517a8|2014 03 19 20:18:17:831|-0600|Error| |>>|E| |webiserver_KMGBKMMSDATA.WIP.Master|12260|14940|| |1|0|1|0|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|webiserver_KMGBKMMSDATA.WIP.Master.createSession|localhost:12260:14940.40460:1|CvnfsjwWLk18kqaRyc.ln0w887|||||||||||**ERROR:ServerLifeCycleManager:Info: Sessions in state INVALID: 0 [ServerLifeCycleManager.cpp;1150]
ServerLifeCycleManager.cpp:1153:void __cdecl ServerLifeCycleManager::dumpContextOnError(void): TraceLog message 814909
|244bd64e-1707-8d84-9b5e-6e0df9dab62e|2014 03 19 20:18:17:831|-0600|Error| |>>|E| |webiserver_KMGBKMMSDATA.WIP.Master|12260|14940|| |1|0|1|0|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|webiserver_KMGBKMMSDATA.WIP.Master.createSession|localhost:12260:14940.40460:1|CvnfsjwWLk18kqaRyc.ln0w887|||||||||||**ERROR:ServerLifeCycleManager:Info: Sessions actually deleted: 0 [ServerLifeCycleManager.cpp;1153]
SchedulerImpl.cpp:668:void __cdecl SchedulerImpl::dumpContextOnError(void): TraceLog message 814910
|16c003da-1ab5-5e64-2ac4-223dc92a8260|2014 03 19 20:18:17:831|-0600|Error| |>>|E| |webiserver_KMGBKMMSDATA.WIP.Master|12260|14940|| |1|0|1|0|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|BIPSDK.ServiceMgr:getManagedService|KMGBKMMSDATA:1556:256.2183:26|webiserver_KMGBKMMSDATA.WIP.Master.createSession|localhost:12260:14940.40460:1|CvnfsjwWLk18kqaRyc.ln0w887|||||||||||**ERROR:SchedulerImpl:Info: max number of threads: 400 [SchedulerImpl.cpp;668]