Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Locators not starting, ES3 install. Can't bootstrap

Avatar

Level 4

I am trying to install a JBOSS/ES3 clustered env and am currently in the config manager trying to bootstrap the db.

Based on the logs I am having a locator issue.

2012-04-30 14:07:05,360 ERROR [STDERR] (http-10.24.210.48-8080-1) Caused by: com.gemstone.gemfire.GemFireConfigException: Unable to contact a Locator service.  Operation either timed out or Locator does not exist.  Configured list of locators is "[njes1s7462<v0>:22345, NJES1S7580<v0>:22345]".

Back in ES2.5 when i started the locators it would create a .locator + gemfire.log

file in the ES2.5\lib\caching folder.  When i start it in ES3, no .locator file is created and the gemfire.log is found under the C:\TEMP folder.

Checking the gemfire.log i see that it isn't able to connect to the locators on either node.

[config 2012/04/30 14:52:15.719 EDT GemfireCacheAdapter <SimpleThreadPoolWorker-4> tid=0xdd] Checking for license in "vfszip:/C:/jboss-5.1_mssql2008r2cl/server/LC3_APOC_CL/deploy/adobe-livecycle-jboss.ear/adobe-cache-all.jar/gemfireLicense.zip/".

[info 2012/04/30 14:52:15.734 EDT GemfireCacheAdapter <SimpleThreadPoolWorker-4> tid=0xdd] GemFire P2P Listener started on  tcp:///10.24.210.48:50490

[info 2012/04/30 14:52:16.812 EDT GemfireCacheAdapter <PingSender> tid=0xfd] unable to connect to locator  njes1s7462<v0>:22345

[info 2012/04/30 14:52:17.859 EDT GemfireCacheAdapter <PingSender> tid=0xfd] unable to connect to locator  NJES1S7580<v0>:22345

My run.bat file has the following JAVA OPTS added on 1 node

set JAVA_OPTS=%JAVA_OPTS% -Djboss.partition.name=APOC_ES3_CL

set JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=LC3APOC1 -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true -Dprogram.name=%PROGNAME%

set JAVA_OPTS=%JAVA_OPTS% -Dadobe.cache.cluster-locators=10.24.210.48[22345],10.24.210.199[22345]

And

set JAVA_OPTS=%JAVA_OPTS% -Djboss.partition.name=APOC_ES3_CL

set JAVA_OPTS=%JAVA_OPTS% -Dadobeidp.serverName=LC3APOC2 -Dfile.encoding=utf8 -Djava.net.preferIPv4Stack=true -Dprogram.name=%PROGNAME%

set JAVA_OPTS=%JAVA_OPTS% -Dadobe.cache.cluster-locators=10.24.210.48[22345],10.24.210.199[22345]

On the 2nd node.  The only difference is the -Dadobeidp.serverName parameter.  LC3APOC1 vs LC3APOC2.

I dont think the startlocator.bat is even looking at the run.bat files yet, so i really dont know what the issue is.

5 Replies

Avatar

Level 2

Did you start locator by starting startlocator.bat file in /lib/caching folder prior to deploying ear to application server?

What GFlocator.log (present under /lib/caching folder) says?

Avatar

Level 2

Hi, did you can resolve this problem? I have the same problem and I can`t find the solution.

Regards

Avatar

Level 2

HI,

Could you provide the following details on this?

1.OS/Server environment ?

2. What happend when you execute startlocator.bat/startlocator.sh ?

3. Any GFlocator.log file in TCP locator folder (/lib/caching) ?

Thanks,

Pankaj Parashar

Avatar

Level 4

hi

its been over a year since i posted this problem but there were 2 issues with the locators in ES3.

If you selected the default installation for ES3, it installs into C:\Adobe\Adobe LiveCycle ES3\ folder.  The startlocator.bat file (or rather the java call inside) doesnt like the fact that there are 2 spaces in the folder name.  Adobe<space>LiveCycle<space>ES3.  When installing change the folder path ie. C:\Adobe\LiveCycle ES3 <-- 1 space.  Your other option is to copy the the lib\caching folder onto a desktop and start from there..

The 2nd issue we had had to do with a mismatch of 2 files between the in the adobe-core-jboss.ear in the deploy folder and the one in the locators folder.

the gemfire.jar and gemfireversion.properties have to be the same version.

Here are details

http://blogs.adobe.com/dmcmahon/2012/10/22/livecycle-es3-sp1-gemfire-errors-in-server-log-after-inst...

Avatar

Level 2

Thanks Pankaj and g5Spark,

1. Server production enviroment: Windows server 2008, ADEP, JBoss, SQL

2. When I execute startlocator.bat registres this lines in the gemfire.log:

[info 2013/06/12 20:58:51.443 CST GemfireCacheAdapter <PingSender> tid=0x12a] unable to connect to locator  srv-adb-01<v0>:3013

[info 2013/06/12 20:58:52.457 CST GemfireCacheAdapter <PingSender> tid=0x12a] unable to connect to locator  srv-adb-02<v0>:3013

3. When I execute startlocator.bat (C:\Adobe\ADEP\Document Services 10.0\lib\caching) don`t create GFLocator.log

4. JBoss log register:

2013-06-12 21:30:01,479 ERROR [org.jboss.ejb.plugins.LogInterceptor] (main) RuntimeException in method: public abstract com.adobe.pof.schema.POFDomain com.adobe.pof.schema.POFDataDictionaryLocal.getDomain(java.lang.String,com.adobe.idp.Context) throws com.adobe.pof.POFException:

com.adobe.livecycle.cache.CacheRuntimeException: Error loading cache configuration

.

.

.

Caused by: com.gemstone.gemfire.GemFireConfigException: Unable to contact a Locator service.  Operation either timed out or Locator does not exist.  Configured list of locators is "[srv-adb-01<v0>:3013, srv-adb-02<v0>:3013]".

5. The folder installation is: C:\Adobe\ADEP\Document Services 10.0 (Production Enviroment, This can be the problem? )

6. The gemfire.jar and gemfireversion have the same version.

7. I copy lib/caching in desktop, execute and create GFlocator.log, apparently works OK, but when I start JBoss have the same error.

Did you see something that help me to solve it?

Thanks very much.