Defect #968
Updated by Vít Švanda about 6 years ago
We have discovered a very odd behavior of customer contract synchronization.
* Synchronization has been linked against the table in MSSQL (net.sourceforge.jtds.jdbc.Driver).
* The system was created as duplicate a system for synchronizing identity.
* An error has occurred whenever synchronization is started:
<pre>
java.lang.NullPointerException
at eu.bcvsolutions.idm.acc.service.impl.ContractSynchronizationExecutor.getValueByMappedAttribute(ContractSynchronizatio
nExecutor.java:395)
at eu.bcvsolutions.idm.acc.service.impl.AbstractSynchronizationExecutor.handleIcObject(AbstractSynchronizationExecutor.j
ava:507)
at eu.bcvsolutions.idm.acc.service.impl.AbstractSynchronizationExecutor$DefaultResultHandler.handle(AbstractSynchronizat
ionExecutor.java:2123)
at eu.bcvsolutions.idm.ic.connid.service.impl.ConnIdIcConnectorService$2.handle(ConnIdIcConnectorService.java:250)
at org.identityconnectors.framework.impl.api.SearchResultsHandlerLoggingProxy.handle(SearchResultsHandlerLoggingProxy.java:64)
at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:101)
at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:262)
</pre>
* No LogItems were created. The error was only in the main synchronization log.
* *We We have never been able to simulate this problem.* problem.
* *Solution: By resolving the environment, re-creating the system with the same settings (including synchronization).* synchronization).
* *After After mapping has been reselected in a failed sync, this synchronization has started to work properly.* properly.