LDAP synchronization fails in TIBCO BusinessWorks™ ProcessMonitor when the timestamp of a Tomcat server and database server are out of sync.
Article ID: KB0085225
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks ProcessMonitor | - |
| Not Applicable | - |
Description
If you have a database server and the TIBCO BusinessWorks™ ProcessMonitor(BWPM) server on different machines, and the datetime setting of thess two machines are not in sync, then when you try to do a LDAP Synchronization it will fail with the error/entry,
“com.faizsiegeln.njams.config.LdapServlet: com.faizsiegeln.njams.a.b: Save failed. The configuration has been updated by another user in the meantime”
logged in the server.logs.
Though you will be able to do a test connection with the LDAP server and on your test you will see the user and roles in a popup window as per your LDAP query for roles/users, synchronization will fail and in the server.logs the error for "Save failed" will be logged.
Symptoms:
LDAP synchronization fails with the following error seen in the server.logs
2014-06-10 14:45:14,165 ERROR [http-bio-8088-exec-5] com.faizsiegeln.njams.config.LdapServlet: com.faizsiegeln.njams.a.b: Save failed. The configuration has been updated by another user in the meantime.
Cause:
If datetime of the database server and TIBCO BusinessWorks™ ProcessMonitor(BWPM) server machines is not in sync, the configuration update error, "ERROR [http-bio-8088-exec-5] com.faizsiegeln.njams.config.LdapServlet: com.faizsiegeln.njams.a.b: Save failed. The configuration has been updated by another user in the meantime." can occur.
Issue/Introduction
Resolution
Verify the datetime of the database server machine
and the TIBCO BusinessWorks™ ProcessMonitor(BWPM) server machine are synchronized.
Feedback
