Posts in Category "Performance"

Error when attempting to interact with a service managed by the Livecycle DSC container

- Siddharth Jain, Quality Manager @ Adobe

Issue

On WebSphere, errors are encountered on attempting to interact with a service managed by the Livecycle DSC container. The service is unexpectedly shown as inactive in the Livecycle administration console. Examination of the server logs (SystemOut.log) shows that the service failed to start due to class-loading issues (ClassNotFoundException errors).

Reason

The issue occurs as a result of a file-lock which prevents the DSC container from properly extracting the class files required by the DSC class-loader to a temporary directory on the local file-system. To confirm that this is the case, note the time-stamp of the ClassNotFoundException error thrown during service startup in the WAS SystemOut.log and then check that the WAS SystemErr.log contains warning messages of the form ‘The process cannot access this file because it is being used by another process’ around the same time.

Solution

To remove the lock, shut down the server and periodically try to manually delete the file for which the file-lock warning is appearing in SystemErr.log (the log file should contain the complete path of the file) . If the deletion succeeds within a reasonable amount of time, start the server and check that things are fine. If the file continues to stay locked for a long period of time, try restarting the machine.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

List of recent LiveCycle Quick Fixes

For a list of Quick Fixes available for Adobe LiveCycle ES2, ES2 SP1, ES2 SP2, and ES2.5, refer to this knowledgebase article. The Quick Fix list is categorized by version and LiveCycle components.

Once you’ve identified a Quick Fix that you want to apply, please get in touch with Adobe Enterprise Support for further details.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Content Services: WebSphere stops responding when many concurrent threads are running

When the storeContent operation for Content Services 9 is invoked with more than 30 threads, the WebSphere application server may stop responding.

Follow these steps to resolve the issue:

  1. In WebSphere Administrative Console, click Servers > Server Types > WebSphere application servers and then click a server name.
  2. In the right pane, click Thread pools under Additional Properties.
  3. Click WebContainer and, on the Configuration page, increase the value of the Maximum Size field by double the number of threads that you need to run. For example, increase the value of the Maximum Size field by 80 if you want to run 40 threads.
  4. Click Apply or OK.
  5. Click Save directly to the master configuration.
  6. Restart the WebSphere application server.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Content Services: Disable content indexing

You can disable content indexing to improve Content Services 9 performance. Disabling indexing also disables text-based search within new content. However, you can still search within already-indexed content.

Follow these steps to disable indexing:

  1. In the adobe-contentservices.ear file, navigate to LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
  2. Locate the following line:
    <type name=”cm:content”>
  3. Set the index enabled and tokenized properties to false.
  • Change <index enabled=”true”> to <index enabled=”false”>.
  • Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.

Disable the conversions required for indexing

To realize additional performance improvements, disable the conversions required for indexing. Follow these steps:

  1. In adobe-contentservices.ear, browse to contentservices.war\WEB-INF\classes\alfresco\extension.
  2. Preserve a backup of the custom-metadata-extractors-context file.
  3. Delete this file from the EAR.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

Content Services ES2: Improving performance

You can disable content indexing to improve Content Services ES2 performance. However, keep in mind that disabling indexing will also disable text-based search within new content. To disable indexing:
  1. In the adobe-contentservices.ear file, navigate to
    LiveCycle Content Services.ear/contentservices.war/WEB-INF/classes/alfresco/model and open the contentModel.xml file for editing.
  2. Locate the following line:
    <type name=”cm:content”>
  3. Set the index enabled and tokenized properties to false
  • Change <index enabled=”true”>  to <index enabled=”false”>.
  • Change <tokenized>true </tokenised> to <tokenized>false </tokenised>.
For additional performance improvements, you can disable the conversions required for indexing. To disable these conversions:
  1. In adobe-contentservices.ear, browse to 
    contentservices.war\WEB-INF\classes\alfresco\extension.
  2. Preserve a backup of the custom-metadata-extractors-context file.
  3. Delete this file from the EAR.
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)