Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
1013 views

DB Push Adapter (relationship push) GetStatusAfterTimeout

Hello,

 

I'm using the OOTB DB push adapter to try and push some data into an external SQL server.

 

I was able to get the host information to push just fine.

 

But when trying to push the relationship part I keep getting the following error:

 

fcmdb.synchronizer.log - usually would load the TQL and parse out ID and attribute. But when running relationship TQL it error out.

2015-09-09 10:40:19,444  ERROR  [RequestProcessorAsyncPool-49012] - Error occured during sync [DB Push Test:DB Push Test_relation:Node Talk Node Push DB Example]
appilog.framework.shared.manage.impl.MamResponseException: [ErrorCode [898] Integration [{0}]: adapter [{1}] does not supported the action [{2}]{DB Push Test, DB Push, GetStatusAfterTimeout}]
appilog.framework.shared.manage.impl.MamResponseException: [ErrorCode [898] Integration [{0}]: adapter [{1}] does not supported the action [{2}]{DB Push Test, DB Push, GetStatusAfterTimeout}]
CMDB Operation Internal Error: class com.mercury.topaz.cmdb.shared.fcmdb.dataAccess.exception.AdapterAccessGeneralException : GetStatusAfterTimeout not supported by adapter : operation Data Access Operation: Get Status After Timeout : class com.mercury.topaz.cmdb.shared.base.CmdbException : 
CMDB Internal Error: Error while handling request: {request: ID='dd0ad94827a78db168a69a856f9b0b17' Message='General CMDB request' Operation='com.hp.ucmdb.dataAccess.operations.DataAccessAdapterCommandGetStatusAfterInterruption@5f597b6d' Customer ID='1, id name: Default Client' 
Context='CMDB Context: Customer id = '1, id name: Default Client' , User ID = '911' , Caller Application = 'UCMDB-UI,loggedInUser:{admin}''}
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.createCmdbResponseOnCmdbError(RequestProcessor.java:459)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.processRequest(RequestProcessor.java:203)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.handleRequest(RequestProcessor.java:123)
	at com.mercury.topaz.cmdb.server.manage.Framework.handleRequest(Framework.java:610)
	at com.mercury.topaz.cmdb.client.manage.api.impl.AbstractCmdbApi.executeCMDBOperation(AbstractCmdbApi.java:38)
	at com.mercury.topaz.cmdb.client.manage.api.impl.AbstractCmdbApi.executeOperation(AbstractCmdbApi.java:57)
	at com.mercury.topaz.cmdb.client.manage.api.impl.InternalApi.executeOperation(InternalApi.java:32)
	at com.mercury.topaz.cmdb.client.manage.api.impl.InternalApi.executeCMDBOperation(InternalApi.java:24)
	at com.mercury.topaz.cmdb.server.manage.ServerApiFacade.executeOperation(ServerApiFacade.java:56)
	at com.mercury.topaz.cmdb.server.manage.ServerApiFacade.executeOperation(ServerApiFacade.java:34)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.handleExceptionDuringInterruption(AbstractSynchronizerCommandRunSyncUnit.java:1313)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.updateData(AbstractSynchronizerCommandRunSyncUnit.java:1272)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.updateDataInChunks(AbstractSynchronizerCommandRunSyncUnit.java:498)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.replicateSingleTqlFromTopologyDiff(AbstractSynchronizerCommandRunSyncUnit.java:1667)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.replicateInstancesFromTopologyDiff(AbstractSynchronizerCommandRunSyncUnit.java:407)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.replicateFromTopologyDiff(AbstractSynchronizerCommandRunSyncUnit.java:346)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.runSynchUnit(AbstractSynchronizerCommandRunSyncUnit.java:267)
	at com.hp.ucmdb.synchronizer.operations.SynchronizerCommandRunFullSynchronization.synch(SynchronizerCommandRunFullSynchronization.java:61)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerCommandRunSyncUnit.synchronizerExecute(AbstractSynchronizerCommandRunSyncUnit.java:194)
	at com.hp.ucmdb.synchronizer.operations.AbstractSynchronizerOperation.doExecute(AbstractSynchronizerOperation.java:34)
	at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractFrameworkOperation.commonExecute(AbstractFrameworkOperation.java:17)
	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:158)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.doProcessRequest(RequestProcessor.java:217)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.doProcessRequestWithQueueLimitation(RequestProcessor.java:226)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.processRequest(RequestProcessor.java:190)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.access$300(RequestProcessor.java:49)
	at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor$4.run(RequestProcessor.java:537)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
	at java.lang.Thread.run(Thread.java:745)

For testing I'm using the OTB relatonship push. Node talk Node, with talk being the Root.

 

I'm also using default mapping for testing

<targetrelations> 
        <link source_link_type="talk" target_link_type="TALK" mode="update_else_insert" source_ci_type_end1="node" source_ci_type_end2="node">
            <target_ci_type_end1 name="node" />
            <target_ci_type_end2 name="node" />
            <targetprimarykey/>
            <target_attribute name="NAME" datatype="char" length="255" option="uppercase">
                <map type="direct" source_attribute="name"/>
            </target_attribute>
            <target_attribute name="DATA_NOTE" datatype="char" length="255" option="uppercase">
                <map type="direct" source_attribute="data_note"/>
            </target_attribute>
        </link>
</targetrelations>

Anyone have any idea wha the GetStatusAfterTimeOut error is?  

4 Replies
Highlighted
Absent Member.
Absent Member.

Re: DB Push Adapter (relationship push) GetStatusAfterTimeout

I've started to get this error after upgrade UCMDB to 10.21 CP17.

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: DB Push Adapter (relationship push) GetStatusAfterTimeout

I just upgraded from 10.20 CP 15 to 10.21 CP 17 and am getting this error on all push jobs to HPSM. 

Was a solution every identified?

 

John Krueger

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: DB Push Adapter (relationship push) GetStatusAfterTimeout

I'm also hitting this on 10.21.CUP1.440.  If anyone could post a solution that would be awesome.

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: DB Push Adapter (relationship push) GetStatusAfterTimeout

I am also getting the same error on UCMDB 10.21. 

com.merucry.topaz.cmdb.shared.base.cmdbexception: [errorcode [898] integration [{0}]: adapter [{1}] does not support the ation {[2}] {cmdb10xadapter, GetStatusAfterTimeout}].
Chuong - were you able to fix this or find a solution? Please let me know. thanks

Regards
Manoj
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.