IBM Support

Bulkload fails with "Cannot end bulkload"

Troubleshooting


Problem

bulkload.log contains: 2015-01-21 01:58:44,781 [t3544] INFO bulk.CdbConfigniaClient - Enabling Discovery and then disconnecting... 2015-01-21 01:58:44,781 [t3544] INFO bulk.CdbConfigniaClient - Bulk Load Program is notifying the server that it is done, id: 1421783405783 2015-01-21 01:59:17,249 [t3544] DEBUG remoting.RemoteServiceInvocationHandler - Calling method endBulkload on proxy for service ApiServerServiceInterface failed after retry 0 due to connection failure java.rmi.RemoteException: Cannot end bulkload and 2015-01-21 01:59:17,239 ApiServer [RMI TCP Connection(65183) -10.1.2.3] DEBUG remoting.RemoteServiceInvocationHandler - Calling method releaseResource on proxy for service SemaphoreServiceInterface failed permanently java.rmi.RemoteException: Cannot release resource: 1421783405783 for service=STORAGE then, at the end of the log... 2015-01-21 01:59:17,253 [t3544] ERROR bulk.CdbConfigniaClient - Filename: ControlApiImpl.java Line number: 513 Class name: com.collation.proxy.api.client.ControlApiImpl Method name: endBulkload com.collation.proxy.api.client.ControlApiImpl.endBulkload(ControlApiImpl.java:513) 2015-01-21 01:59:17,253 [t3544] ERROR bulk.CdbConfigniaClient - Filename: CMDBApiImpl.java Line number: 1279 Class name: com.collation.proxy.api.client.CMDBApiImpl Method name: endBulkload com.collation.proxy.api.client.CMDBApiImpl.endBulkload(CMDBApiImpl.java:1279) Additionally, the semaphore.log contains: 2015-01-27 19:48:56,066 Semaphore [Timeout timer] ERROR semaphore.SemaphoreService - [SemaphoreService.E.25] ERROR: Resource lock Caller=BULKLOAD, id=1422379724682, resource=STORAGE, runId=0 has timed out. Removing

Cause

Hitting a semaphore timeout. Close examination shows that the semaphore.log message appears 8 hours + 20 minutes after bulkload "disconnecting" message. There is a 500 multiplier on the api server timeout property value, the property is n *500 seconds.

Resolving The Problem

Increase the com.ibm.cdb.bulk.apiservertimeout in the dist/etc/bulkload.properties file. This does not require a TADDM restart, can also see the value at the beginning of the bulkload.log:

2015-01-27 11:28:15,171 [main] DEBUG bulk.CdbBulkLoaderProperties - api server timeout value is:120

[{"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

TADDM

Document Information

Modified date:
17 June 2018

UID

swg21696276