LiveCycle ES3 SP1: Gemfire errors in server log after installing patches on top of 10.0.2

Issue

If you are using TCP locators in a LiveCycle cluster with ES3 (10.0.2) and have installed a service pack or patches on top of this version, you may notice some errors in the server log similar to the following:

com.adobe.livecycle.cache.CacheRuntimeException: Error loading cache configuration
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.getCacheContainer(GemfireCacheAdapter.java:164)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.createRootRegion(GemfireCacheAdapter.java:853)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.init(GemfireCacheAdapter.java:218)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.<init>(GemfireCacheAdapter.java:207)
at com.adobe.livecycle.cache.adapter.CacheAdapterFactory.getCache(CacheAdapterFactory.java:103)

Caused by: com.gemstone.gemfire.SystemConnectException: Attempt to connect to distributed system timed out

If you have a UDP-based cluster caching mechanism, you are not affected by this issue.

Reason

This issue occurs when the Gemfire version on the server is different from the Gemfire version used by the TCP locators.  Gemfire.jar and GemFireVersion.properties are delivered in two different places in the LC installation – 1. Core EAR 2. /lib/caching directory.

Gemfire version 6.5.1.17 was used for LC ES3 (10.0.2).  To address some known issues a new Gemfire version (6.5.1.35) was used in later versions and patches.  This newer Gemfire version was used for the Core EAR, but unfortunately not included for updating the caching directory.

To verify the issue, compare the Gemfire version in the GFLocator.log file for your TCP Locator with the Gemfire version in the Gemfire logs for your application server at the following location:

  • JBoss: <adobe_temp_dir>/adobejb_<server_name>/caching/Gemfire.log
  • Weblogic: <adobe_temp_dir>/adobewl_<hostname>/caching/Gemfire.log
  • WebSphere: <adobe_temp_dir>/adobews_*/caching/Gemfire.log

You will find that Gemfire on the LiveCycle server has a higher version.

Solution

This issue has been addressed in SP2 and later patch versions.

Note: the patch installer will only update the default caching directory (<lc_install_dir>/lib/caching) on the machine where LC is installed.  If you are running LC on various machines, and/or use custom caching directories, you will need to update the 2 Gemfire files for your TCP locators manually.  All TCP locators need to be restarted before starting LC servers.

Workaround

For existing patches you can use the following workaround to fix the issue on your LiveCycle installation.

  1. Stop the LiveCycle server(s).
  2. Stop the TCP Locator(s).
  3. Go to <LC_INSTALL_DIR>/deploy folder.
  4. Open adobe-core-<appserver_name>.ear.
  5. Go to TCP locator installation directory. Typically the default location is <LC_INSTALL_DIR>/lib/caching.
  6. gemfire.jar and GemFireVersion.properties can be found here.
  7. Replace the two files above in the TCP locator with the same files from the core ear.
  8. Repeat the replacement procedure (steps 5 – 7) for each TCP locator.
  9. Start TCP Locator(s).
  10. Start LiveCycle server(s) in the Cluster.

Verify the Gemfire versions in GFLocator.log and Gemfire.log files. You should see the same Gemfire version in both files.

reference: (183615151/3327651)

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

Acrobat 10.1.4: Acrobat/Reader hangs while scanning

Issue

If you are scanning documents with Acrobat/Reader 10.1.4 using any mode (Grayscale/Color/BW),  Acrobat/Reader may hang when scanning is about to complete.

Reason

This is an issue in the 10.1.4 update and will be addressed in future versions.  It is also being discussed in our forums: http://forums.adobe.com/thread/1050323?start=0&tstart=0

Solution

Install the patch for Acrobat and Reader 10.1.4 (Windows only).

  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file: AdobeAcrobatReaderPatch10.1.4_3314564.zip
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file using a ZIP tool to a location on your local computer.
  • Double-click the AdobeAcrobatReaderPatch10.1.4_3314564.exe file to begin the update.
  • When a prompt notifies you that the update is complete, restart your computer.

_______________________________________________________________________________________________

 Install the patch for Acrobat and Reader 10.1.4 in silent mode (Windows only).
  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file: AdobeAcrobatReaderPatch10.1.4_3314564.zip
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file.
  • Open the command prompt “As Administrator.”
  • Type the path to the patch file executable, and add the -silent flag on the command line. For example:
    AdobeAcrobatReaderPatch10.1.4_3314564.exe -silent
    Silent mode suppresses all dialog boxes so you do not get a message indicating that the update is complete. The executable creates a log file “AcroPatchApplication1014.log” in the temp directory (%temp%).
  • When the update is complete, restart the computer.

reference: (3314564)

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