Re: Problem starting Pulse tool hosted in Tomcat

Try as I might, I cannot replicate this problem. The significant part here is that the gemfire node does not seem to know its own hostname on startup whereas other systems do. (seems to have amnesia ). It's easy enough replicating the opposite

If you would, I'd like to ask you to try two more things.

Create an explicit entry in /etc/hosts on the gemfire node for itself - ie:

127.0.0.1   localhost

10.50.38.205   ccnscupadsgf01 ccnscupadsgf01.carecorenational.com

#127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4

::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

 

At some points, GemFire uses JNDI calls to resolve names, so to avoid any strangeness possible being introduced by Tomcat, could you simply start a server, using gfsh:

gfsh start server --locators=IDCPRDGFLOCATOR1[20003] --name=locator1

For both tests, you're looking for a line, in the log, like:

Entered into membership in group GF70 with ID 10.50.38.205(7967)<v1>:29066

Except it should contain the hostname of the server and not the IP.

And then

Initializing region _monitoringRegion_10.50.38.205(7967)<v1>29066

Should also appear with the hostname,

Thanks for your pateince.

--Jens