In Symantec Data Insight (SDI) version 1.02 there is an issue with the events-publishing mechanism which would be a cause for delayed processing of events by the index-writer job.
IndexWriterJob is not keeping up with the incoming rate
if(state != PAUSED && state != CALLJAVA) throw new IllegalStateException("call() called in inappropriate state");
a) The starting point for this JDBC is a C implementation of a driver
b) The C-source code of the driver is compiled using GCC to a binary that runs on MIPs architecture (it is easier to translate MIPs instructions to JavaByte code instructions).
c) The MIPs binary is then translated to a JAVA class (the JDBC)
d) The MIPS translated JAVA class is then run on top of NestedVM runtime, which is a virtual machine that emulates the MIPS operating system (system calls) and the MIPS hardware architecture (MMU etc)
e) NestedVM is loaded into the JRE when the JDBC is loaded
NestedVM runtime can go into an unexpected state, and would refuse to accept system calls allowing the queue to build up.
Provided an updated sqlite-jdbc-188.8.131.52.jar file
Here are the steps to apply the patch:
On all the 64-bit DataInsight machines:
1. Stop DataInsightComm and DataInsightWeb services.
cmd prompt> net stop DataInsightComm
cmd prompt> net stop DataInsightWeb
2. Take a backup of the C:\Program Files\Symantec\DataInsight\log folder and then delete all the existing log files in that folder.
3. Make a backup copy of the following files :
-- C:\Program Files\Symantec\DataInsight\reports\ReportEngine/plugins\org.eclipse.birt.report.data.oda.jdbc_2.3.2.v20090331-1440\drivers\sqlitejdbc-v056.jar
-- C:\Program Files\Symantec\DataInsight\tomcat\webapps\ROOT\WEB-INF\lib\sqlitejdbc-v056.jar
4. Download the attached file to the locations above.
5. Restart the services stopped in step 1.
cmd prompt> net start DataInsightComm
cmd prompt> net start DataInsightWeb
Verify under the “C:\Program…\DataInsight\log” folder on the Indexer/Management Server that the issue is resolved
Windows 2003 / 2008