Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class
682 views

Integration Bridge - General Error when completing sync

Jump to solution

For the ALM Octane integration Bridge setup between ALM Octane and HP QC Enterprise/ALM for the defect entity, we performed the setup,  integrity check (with warnings), completed a simulation successfully and then when running a manual sync was run an error occured. 

Has anyone encountered this? I raised a support ticket and did not receive a response for one ticket. I submitted another and it got rejected.  The integration bridge is fairly new from what I understand and I haven't been able to get much traction for support on this error. 

Log snapshot below:

SERVER 11/28/2018,11:31:18,292 INFO Defect.To.ALM/QC.CREATE Creating identity maps.
SERVER 11/28/2018,11:31:18,292 INFO Creating identity maps
BRIDGE 11/28/2018,12:31:18,697 ERROR Defect Fatal error occurred. Synchronization failed. General Error: Failed to create record. Message: General Error: General error occurred: null
BRIDGE 11/28/2018,12:31:18,697 FATAL Fatal error occurred, the synchronization failed. Message: General Error: Failed to create record. Message: General Error: General error occurred: null
BRIDGE com.hp.sync.adapters.exceptions.FatalAdapterException: General Error: Failed to create record. Message: General Error: General error occurred: null
BRIDGE at com.hp.sync.alm.adapter.ALMEntityManager.internalBulkCreateUpdate(ALMEntityManager.java:343)
BRIDGE at com.hp.sync.alm.adapter.ALMEntityManager.createBulk(ALMEntityManager.java:267)
BRIDGE at com.hp.sync.shared.execution.sync.EntityHandlerImpl.createBulk(EntityHandlerImpl.java:130)
BRIDGE at com.hp.sync.executor.SyncBulkCreateExecutor.handleBulkExecution(SyncBulkCreateExecutor.java:45)
BRIDGE at com.hp.sync.executor.AbstractSyncBulkExecutor.execute(AbstractSyncBulkExecutor.java:84)
BRIDGE at com.hp.sync.executor.SyncEntityRemoteSupport.handleEntityCreateInBulk(SyncEntityRemoteSupport.java:454)
BRIDGE at com.hp.sync.executor.SyncEntityRemoteSupport.syncEntitiesToRemote(SyncEntityRemoteSupport.java:134)
BRIDGE at com.hp.sync.executor.SyncChanges.syncEntitiesToRemote(SyncChanges.java:338)
BRIDGE at com.hp.sync.executor.SyncChanges.syncPartitionToRemote(SyncChanges.java:292)
BRIDGE at com.hp.sync.executor.SyncChanges.syncEntitiesToRemoteInPartition(SyncChanges.java:281)
BRIDGE at com.hp.sync.executor.SyncChanges.createUpdateRemoteRecords(SyncChanges.java:252)
BRIDGE at com.hp.sync.executor.SyncChanges.sync(SyncChanges.java:139)
BRIDGE at com.hp.sync.executor.SynchronizeTaskExecutor.doTaskImpl(SynchronizeTaskExecutor.java:196)
BRIDGE at com.hp.sync.executor.SynchronizeTaskExecutor.doTaskImpl(SynchronizeTaskExecutor.java:73)
BRIDGE at com.hp.sync.executor.AbstractSyncTaskExecutor.execute(AbstractSyncTaskExecutor.java:52)
BRIDGE at com.hp.opb.executor.TaskThread.performTask(TaskThread.java:116)
BRIDGE at com.hp.opb.executor.TaskThread.run(TaskThread.java:57)
BRIDGE at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
BRIDGE at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
BRIDGE at java.lang.Thread.run(Thread.java:745)
BRIDGE Caused by: com.hp.sync.adapters.exceptions.FatalAdapterException: General Error: General error occurred: null
BRIDGE at com.hp.sync.alm.adapter.ALMErrorHandler.handleException(ALMErrorHandler.java:125)
BRIDGE at com.hp.sync.alm.adapter.ALMErrorHandler.handleException(ALMErrorHandler.java:82)
BRIDGE at com.hp.sync.alm.adapter.ALMRecord$FieldHandler.setCycleField(ALMRecord.java:996)
BRIDGE at com.hp.sync.alm.adapter.ALMDefectTypeRecord$DefectFieldHandler.setCycleFields(ALMDefectTypeRecord.java:83)
BRIDGE at com.hp.sync.alm.adapter.ALMRecord$FieldHandler.setEntityFields(ALMRecord.java:932)
BRIDGE at com.hp.sync.alm.adapter.ALMEntityManager.prepareEntityListForBulkOperation(ALMEntityManager.java:369)
BRIDGE at com.hp.sync.alm.adapter.ALMEntityManager.internalBulkCreateUpdate(ALMEntityManager.java:315)
BRIDGE ... 19 more
BRIDGE Caused by: java.lang.NullPointerException
BRIDGE at com.hp.sync.alm.adapter.ALMRecord$FieldHandler.setCycleField(ALMRecord.java:978)
BRIDGE ... 23 more
BRIDGE 11/28/2018,12:31:18,697 INFO Total run time: 17 seconds
BRIDGE 11/28/2018,12:31:18,697 INFO Disconnect called
BRIDGE 11/28/2018,12:31:18,697 INFO Disconnect completed

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Hello gchan, 

I work on the Octane Synchronizer R&D team.

From the log snipet that you sent, It seems that the cycle field for the defects cause the problem. If possible, can you try to clear the values from that field and retry the sync? Even if that is the cause, that should be supported and we will investigate further.

If you could send us the contents of the /product/log directory from your Integration Bridge installation, we would be happy to look into the issue.

Thanks,

Sergiu

View solution in original post

1 Reply
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Hello gchan, 

I work on the Octane Synchronizer R&D team.

From the log snipet that you sent, It seems that the cycle field for the defects cause the problem. If possible, can you try to clear the values from that field and retry the sync? Even if that is the cause, that should be supported and we will investigate further.

If you could send us the contents of the /product/log directory from your Integration Bridge installation, we would be happy to look into the issue.

Thanks,

Sergiu

View solution in original post

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.