Data import via localdb fails with timeout error

Data import via localdb fails with timeout error

Issue: SQL query timeouts after upgrade to version 4000.

Analysis:  The timeout error pops up before generating the data preview.



Log traces:
[14:34:01:353]|[12-04-2018]|[SYSERR]|[INFO]|[128]: 
ERROROCCURED,'NOSESSIONID',3246,'CLOUDDB_IMP_SCHEDULE_DETAILS',400,1543894441000,-1,'QUERY_EXECUTE_ERROR',',108,'','','','Sorry_ there is a problem while executing query.  Reason: ''Read timed out''','-NA-','-','192.168.252.1','192.168.252.1_sas','-Not Provided-','-Error Code not 500-','NONE'
com.adventnet.zoho.db.common.ZDBException: QUERY_EXECUTE_ERROR
at com.adventnet.zoho.db.clouddb.ZRCloudDBAPI.batchFilesAndImport(ZRCloudDBAPI.java:1148)
at com.adventnet.zoho.db.clouddb.ZRCloudDBImportScheduleTask.importScheduleSingleTable(ZRCloudDBImportScheduleTask.java:208)
at com.adventnet.zoho.db.clouddb.ZRCloudDBImportScheduleTask.executeTaskInTxn(ZRCloudDBImportScheduleTask.java:131)
at com.adventnet.zoho.db.common.TxnTask.executeCode(TxnTask.java:29)
at com.adventnet.persistence.ZDBPackageAccessUtil.invokeInTransaction(ZDBPackageAccessUtil.java:234)
at com.adventnet.zoho.db.common.TxnTask.executeTask(TxnTask.java:23)
at com.adventnet.zoho.db.clouddb.ZRCloudDBImportScheduleTask.executeTask(ZRCloudDBImportScheduleTask.java:59)
at com.adventnet.zoho.db.common.newscheduler.ZRTask.runTask(ZRTask.java:189)
at com.adventnet.zoho.db.common.newscheduler.ZTask.run(ZRTask.java:124)
at com.adventnet.zoho.db.common.newscheduler.ZRTask.run(ZRTask.java:175)
at com.adventnet.zoho.db.common.newscheduler.ZTask.run(ZRTask.java:89)
at com.adventnet.zoho.db.common.newscheduler.ZRTask.run(ZRTask.java:175)
at com.adventnet.zoho.db.common.newscheduler.ZTask.executeTask(ZRTask.java:43)
at com.adventnet.zoho.db.common.newscheduler.ZRTask.executeTask(ZRTask.java:175)
at com.adventnet.taskengine.internal.SchedulerBean.executeTask(SchedulerBean.java:631)
at sun.reflect.GeneratedMethodAccessor456.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.adventnet.mfw.bean.BeanProxy.invoke(BeanProxy.java:115)
at com.sun.proxy.$Proxy5.executeTask(Unknown Source)
at com.adventnet.taskengine.internal.ScheduleExecutor.executeNextTask(ScheduleExecutor.java:148)
at com.adventnet.taskengine.internal.ScheduleExecutor.run(ScheduleExecutor.java:76)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Read timed out
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2435)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1988)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:6310)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:7545)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:843)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:752)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:654)
at com.adventnet.zoho.db.clouddb.ZRCloudDBAPI$QueryTimeout.run(ZRCloudDBAPI.java:2695)
... 1 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1981)
... 11 more 

Solution: Add the below parameter in app.properties and restart the service.

import.clouddb.networktimeout=0


                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • Change module data : Import into Analytics Plus

                        Change module data : Import into Analytics Plus Note: When Analytics Plus officially supports Change module integration Out of the box, then these imported tables and reports might get overwritten. Please ensure to name the table as 'Change_localDB'. ...
                      • Unable to Connect to the Postgres SQL Database from Command Prompt

                        Issue : Unable to Connect to the Postgres SQL Database from Command Prompt Error : Analysis : IPv6 local connections are commented in <AnalyticsPlus home>\pgsql\data\pg_hba.conf file Solution : Open the file using notepad or wordpad as administrator ...
                      • Sync getting stuck in In-progress state

                        Issue:  Sync getting stuck in In-progress state. Usually, when the data type mismatch is present, this issue occurs. Logs required: <AnalyticsPlus>/pgsql/data/pg_log/ Check for the error trace by searching "ERROR:  invalid input syntax for" Sample ...
                      • Upgrade issue in build 3200

                        Upgrade issue in build 3200 The below cases were identified in local system and couple of customer's system during 3200 upgrade. Issue 1: PGSQL migration fails: Since this upgrade will upgrade pgsql version, pgsql has its own upgrade prior to ...
                      • Unable to sync between Servicedesk Plus and Analytics Plus - ATKey error

                        Issue: Unable to configure integration/sync between ServiceDesk Plus and Analytics Plus ERROR Message: FAILURE :Not able to get ATKey from Server. You can obtain the error log files from Support tab by clicking on the Support File link in the ...