LiveCycle database size grows inordinately on synching users periodically with Content Services ES installed
Issue
There is an issue in Adobe LiveCycle Content Services ES, version 8.2.1, where user synchronization from an external repository like Directory Server leads to inordinate growth in the LiveCycle database. This behavior is incorrect.
This issue occurs in the following conditions:
- A domain is created in User Manager that synchs the user on a periodic basis from a directory server
- Content Services ES is part of the LiveCycle deployment
Due to this issue following parts are affected:
- The table
tb_job_instancein the LiveCycle database increases in size after every synch. - The rows in this table do not get deleted forever.
- Due to the increase in database size, the database performance suffers.
Affected version 8.2.1.0, 8.2.1.1
Affected Database – The issue occurs for all databases.
Only those installations that have Content Services ES installed are affected.
Reason
To resolve this issue, there are two steps to be performed.
A. Modifying the User Manager Configuration
To resolve this issue you export the config.xml file from LiveCycle Administration Console, make the modifications described below and then reimport the config.xml file. You do not require any quickfix.
- Navigate to Settings > User Management > Configuration > Import and export configuration files.
- Click Export to download a copy of the config.xml file. Take a backup of this file.
- Open the config.xml file in an editor. Locate the
Adobe/LiveCycle/Config/UM/ExternalPrincipalStorageProvider/Settingsnode. - Set the value of the synchronous entry to true.
- Save and close the config.xml file.
- In LiveCycle Administration Console, return to Settings > User Management > Configuration > Import and export configuration files.
- On the Manual Configuration screen, ensure that User Management is selected as the configuration to import.
- In the Select a configuration file to import box, enter the full path and file name of the edited config.xml or click Browse to navigate to it.
- Click Import to continue. A message appears on the screen indicating that the file was successfully imported.
- Click OK to confirm the updated settings.
B. Deleting the stale entries
The above steps prevent the addition of new rows in the tb_job_instance. However, the table still contains the stale entries. To address this issue, perform the following steps:
- Stop the LiveCycle server.
- For MySQL run the following SQL command (for other database run a similar command to delete the stale entries).
MySql delete from tb_job_instance where operation_name='injectPrincipals'
- Restart the LiveCycle server.
Example
Following is an XML snippet showing the Adobe/LiveCycle/Config/UM/ExternalPrincipalStorageProvider/Settings node. The modified value is shown in bold.
<node name="ExternalPrincipalStorageProvider">
<map/>
<node name="Providers">
<map/>
<node name="ContentServices">
<map>
<entry key="endHook" value="onSyncEnd"/>
...
</map>
</node>
</node>
<node name="Settings">
<map>
<entry key="synchronous" value="true"/>
<entry key="present" value="true"/>
</map>
</node>
</node>
This content requires Flash
To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.
Download the free Flash Player now!
