GO!NotifyLink, when interfacing with Oracle Beehive version 184.108.40.206.0 and 220.127.116.11.0 servers, may experience an abundance of errors in the PIM logs and PIM information does not process successfully.
Synchronization is failing due to a concurrency issue with some internal cache within the OMA server of 18.104.22.168.0 / 22.214.171.124.0. Eventually the server crashes on a timing issue and PIM sysnchronizations fail.
A temporary workaround is to configure GO!NotifyLink so that only 1 client at a time hits the OMA midtier. When the GO!NotifyLink server processes one user at a time, synchronization is successful.
After reconfiguring GO!NotifyLink, it is also necessary to restart the OmaService:
./beectl restart --component_OmaService
A future release of Beehive will contain a fix that will resolve this issue permanently.