Highlighted
Outstanding Contributor.
Outstanding Contributor.
737 views

[SQLServer JDBC Driver]Execution timeout expired.

Jump to solution

We are seeing the following error messages in the UCMDB server error.log

2015-02-16 14:39:09,563 [Discovery Probe Task-420] (TasksGeneratorImpl.java:1612) ERROR - Failed save new tasks state in the db 
com.mercury.jdbc.sqlserverbase.ddc: [mercury][SQLServer JDBC Driver]Execution timeout expired.
	at com.mercury.jdbc.sqlserverbase.ddd2.executeBatch(Unknown Source)
	at com.mercury.jdbc.sqlserverbase.ddd6.executeBatch(Unknown Source)
	at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
	at com.hp.ucmdb.discovery.server.dal.DiscoveryDestDAO.deleteJobDestinations(DiscoveryDestDAO.java:620)
	at com.hp.ucmdb.discovery.server.dal.DiscoveryDestDAO.deleteJobDestinations(DiscoveryDestDAO.java:765)
	at com.hp.ucmdb.discovery.server.utils.TasksGeneratorImpl.updateDB(TasksGeneratorImpl.java:1609)
	at com.hp.ucmdb.discovery.server.utils.TasksGeneratorImpl.getNextTasks(TasksGeneratorImpl.java:1376)
	at com.hp.ucmdb.discovery.server.utils.TasksGeneratorImpl.generateJobsRelatedTasks(TasksGeneratorImpl.java:729)
	at com.hp.ucmdb.discovery.server.framework.discovery.manager.AutoDiscoveryProbeManagerImpl.generateJobsRelatedTasks(AutoDiscoveryProbeManagerImpl.java:707)
	at com.hp.ucmdb.discovery.framework.probe.operations.AutoDiscoveryOperationJobRelatedTasks.executeProbeOperation(AutoDiscoveryOperationJobRelatedTasks.java:25)
	at com.hp.ucmdb.discovery.framework.probe.operations.AbstractAutoDiscoveryProbeOperation.doExecute(AbstractAutoDiscoveryProbeOperation.java:25)
	at appilog.framework.shared.manage.operation.impl.AbstractMamOperation.commonExecute(AbstractMamOperation.java:30)
	at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation$OperationExecuteFlowTrackingCommand.execute(AbstractCommonOperation.java:87)
	at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation$OperationExecuteFlowTrackingCommand.execute(AbstractCommonOperation.java:60)
	at com.mercury.topaz.cmdb.shared.manage.flowmanagement.api.FlowManager.execute(FlowManager.java:227)
	at com.mercury.topaz.cmdb.shared.manage.operation.flow.OperationInFlowDefaultExecutor.execute(OperationInFlowDefaultExecutor.java:23)
	at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation.execute(AbstractCommonOperation.java:159)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.doProcessRequest(RequestProcessor.java:211)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.doProcessRequestWithQueueLimitation(RequestProcessor.java:220)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.processRequest(RequestProcessor.java:184)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.access$300(RequestProcessor.java:43)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor$4.run(RequestProcessor.java:531)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
	at java.lang.Thread.run(Thread.java:722)
2015-02-16 14:39:09,563 [Discovery Probe Task-420] (TasksGeneratorImpl.java:1379) WARN  - Failed update cmdb with the new task. Error msg: java.lang.RuntimeException: Failed save new tasks state in the db 
2015-02-16 14:49:10,081 [TasksDispatchingThread] (DiscoveryDestDAO.java:203) ERROR - Insert new destinations Failed
com.mercury.jdbc.sqlserverbase.ddc: [mercury][SQLServer JDBC Driver]Execution timeout expired.
	at com.mercury.jdbc.sqlserverbase.ddd2.executeBatch(Unknown Source)
	at com.mercury.jdbc.sqlserverbase.ddd6.executeBatch(Unknown Source)
	at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
	at com.hp.ucmdb.discovery.server.dal.DiscoveryDestDAO.deleteJobDestinations(DiscoveryDestDAO.java:620)
	at com.hp.ucmdb.discovery.server.dal.DiscoveryDestDAO.insertJobDestinations(DiscoveryDestDAO.java:182)
	at com.hp.ucmdb.discovery.server.utils.disptach.actions.AbstractDispatchAction.saveTaskInDB(AbstractDispatchAction.java:94)
	at com.hp.ucmdb.discovery.server.utils.disptach.actions.TriggerTqlHashCodeCalculator.saveTaskInDB(TriggerTqlHashCodeCalculator.java:70)
	at com.hp.ucmdb.discovery.server.utils.disptach.actions.AbstractDispatchActionFlow.dispatchObjectsOnJob(AbstractDispatchActionFlow.java:238)
	at com.hp.ucmdb.discovery.server.utils.disptach.actions.AbstractDispatchActionFlow.handle(AbstractDispatchActionFlow.java:123)
	at com.hp.ucmdb.discovery.server.utils.disptach.DispatchManager$DispatchingThread.authorizedRun(DispatchManager.java:855)
	at com.hp.ucmdb.discovery.server.utils.AbstractAuthorizedThread$1.executeInContext(AbstractAuthorizedThread.java:26)
	at com.hp.ucmdb.discovery.server.utils.AbstractAuthorizedThread$1.executeInContext(AbstractAuthorizedThread.java:23)
	at com.mercury.topaz.cmdb.shared.manage.AuthorizationContextUtils.executeInSystemAuthorizationContext(AuthorizationContextUtils.java:24)
	at com.hp.ucmdb.discovery.server.utils.AbstractAuthorizedThread.run(AbstractAuthorizedThread.java:23)

 These error messages come from a large CallHome processing result set to add / delete CallHome event CIs in the UCMDB database. We would like to know if there is a setting parameter that can be adjusted to increase the timeout for the database job?

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.

Re: [SQLServer JDBC Driver]Execution timeout expired.

Jump to solution

Hello,

 

First of all please verify the fragmentation indexes for UCMDB database.

If the indexes are ok and you don't have the jdbc.properties file created please run the below steps:

 

1.  ceate file <cmdb>\conf\jdbc.properties

 

2. add into file (or modify if the configurations exists and timeout < 3600)

        SQLServer = ddmssql
        ddmssql.QueryTimeout = 3600

 

3. You can increase the timeout of the DB query to 1 hour .(you need to restart the server afterwards).

 

Best regards,

Johnny

 

View solution in original post

0 Likes
1 Reply
Highlighted
Absent Member.
Absent Member.

Re: [SQLServer JDBC Driver]Execution timeout expired.

Jump to solution

Hello,

 

First of all please verify the fragmentation indexes for UCMDB database.

If the indexes are ok and you don't have the jdbc.properties file created please run the below steps:

 

1.  ceate file <cmdb>\conf\jdbc.properties

 

2. add into file (or modify if the configurations exists and timeout < 3600)

        SQLServer = ddmssql
        ddmssql.QueryTimeout = 3600

 

3. You can increase the timeout of the DB query to 1 hour .(you need to restart the server afterwards).

 

Best regards,

Johnny

 

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.