Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
214 views

HP uCMDB : Need a specific log file's name.

Jump to solution

Hi experts,

 

UCMDB: 9.05.CUP14.412

DDM Content Pack: 11.14.874

OS: RHEL

 

What Statistcs log file should I be looking at to get more information on the below error ?

 

2014-11-14 17:42:11,089 [664175877@Default-9501] Async request processing error
CMDB Operation Internal Error: class com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.exception.SynchronizerException : java.lang.NullPointerException : operation Synchronizer Command: Run Scheduled Sync Unit
appilog.framework.shared.manage.impl.MamResponseException: [ErrorCode [860] Error occurred while running synchronization. See statistics for more information]
CMDB Operation Internal Error: class com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.exception.SynchronizerException : java.lang.NullPointerException : operation Synchronizer Command: Run Scheduled Sync Unit
        at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation.execute(AbstractCommonOperation.java:88)
        at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.processRequest(RequestProcessor.java:156)
        at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor.access$200(RequestProcessor.java:48)
        at com.mercury.topaz.cmdb.server.manage.rpm.RequestProcessor$3.run(RequestProcessor.java:465)
        at com.mercury.topaz.cmdb.server.util.concurrent.MortbayQueuedThreadPoolFixed$PoolThread.run(MortbayQueuedThreadPoolFixed.java:555)
Caused by: com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.exception.SynchronizerException: [ErrorCode [860] Error occurred while running synchronization. See statistics for more information]
java.lang.NullPointerException
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.command.impl.AbstractSynchronizerCommandRunSyncUnit.runSynchUnit(AbstractSynchronizerCommandRunSyncUnit.java:293)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.command.impl.SynchronizerCommandRunDiffSynchronization.synch(SynchronizerCommandRunDiffSynchronization.java:54)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.command.impl.AbstractSynchronizerCommandRunSyncUnit.synchronizerExecute(AbstractSynchronizerCommandRunSyncUnit.java:169)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.impl.AbstractSynchronizerOperation.doExecute(AbstractSynchronizerOperation.java:21)
        at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractFrameworkOperation.commonExecute(AbstractFrameworkOperation.java:17)
        at com.mercury.topaz.cmdb.shared.manage.operation.impl.AbstractCommonOperation.execute(AbstractCommonOperation.java:62)
        ... 4 more
Caused by: java.lang.NullPointerException
        at com.hp.ucmdb.graph.v1.util.DefaultHashingStrategy.computeHashCode(DefaultHashingStrategy.java:17)
        at com.hp.ucmdb.graph.v1.util.HashingStrategyDecorator.computeHashCode(HashingStrategyDecorator.java:26)
        at gnu.trove.TObjectHash.index(TObjectHash.java:194)
        at gnu.trove.TObjectIntHashMap.get(TObjectIntHashMap.java:191)
        at com.hp.ucmdb.graph.v1.impl.AbstractUndirectedGraphQuery.buildGraph(AbstractUndirectedGraphQuery.java:56)
        at com.hp.ucmdb.graph.v1.impl.UndirectedGraphQueryImpl.<init>(UndirectedGraphQueryImpl.java:44)
        at com.mercury.topaz.cmdb.shared.tql.result.decorator.v1.TqlResultDecoratorFactory.createGraphQuery(TqlResultDecoratorFactory.java:137)
        at com.mercury.topaz.cmdb.shared.tql.result.decorator.v1.TqlResultDecoratorFactory.createGraphQuery(TqlResultDecoratorFactory.java:106)
        at com.mercury.topaz.cmdb.shared.tql.result.chunk.impl.GraphSplitUtils.splitTqlResult(GraphSplitUtils.java:127)
        at com.mercury.topaz.cmdb.shared.tql.result.chunk.impl.ChunkerFactory.createChunker(ChunkerFactory.java:106)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.base.SyncUtil.createTqlChunker(SyncUtil.java:249)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.base.SyncUtil.extractChunksFromTqlResult(SyncUtil.java:308)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.base.SyncUtil.SplitTqlResult(SyncUtil.java:273)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.base.FcmdbDataSynchronizerUtil.splitToChunksNew(FcmdbDataSynchronizerUtil.java:354)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.command.impl.AbstractSynchronizerCommandRunSyncUnit.replicateFromSimpleSource(AbstractSynchronizerCommandRunSyncUnit.java:1581)
        at com.mercury.topaz.cmdb.shared.fcmdb.synchronizer.operation.command.impl.AbstractSynchronizerCommandRunSyncUnit.runSynchUnit(AbstractSynchronizerCommandRunSyncUnit.java:262)
        ... 9 more

 

Thanks,

Praveen

0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: HP uCMDB : Need a specific log file's name.

Jump to solution

Hello ,

 

I hope you are doing well .

 

I understand that you need and I suggest that if you need to modify OOTB the best option is to contact PSO . They will help with your specific requirements .

 

Best Regards ,

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “

View solution in original post

0 Likes
3 Replies
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: HP uCMDB : Need a specific log file's name.

Jump to solution

Hello ,

 

Please review this document and inform me if it help you .

 

https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM00652148

 

Best regards ,

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: HP uCMDB : Need a specific log file's name.

Jump to solution

Hi Melissa,

 

Thank you for your effort and the support document.

The error I am troubleshooting is similar to the one on the document but I am using a different adapter.

 

There are no adapter-settings tag in the ServiceNowPushAdapter unlike in the XML integration adapter.

<adapter-settings>

            <adapter-setting name="replication.chunk.size">2000</adapter-setting>

</adapter-settings>

 

Is there anyway we could modify the OOTB adapter to control the Async request processing error ?

 

Thanks,

Praveen

 

 

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: HP uCMDB : Need a specific log file's name.

Jump to solution

Hello ,

 

I hope you are doing well .

 

I understand that you need and I suggest that if you need to modify OOTB the best option is to contact PSO . They will help with your specific requirements .

 

Best Regards ,

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “

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.