This issue occurs due to a mismatch in the Gemfire versions of the gemfire.jar bundled with LiveCycle Core EAR and the one supplied with TCP locator in the <LiveCycle_root>/lib/caching directory. To verify the issue, compare the Gemfire version in the Gemfire logs for your application server at the following location on LiveCycle server with the Gemfire version in the GFLocator.log file for your TCP Locator.
- 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 the server-side Gemfire has a higher version.