Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 245504

Re: HTTP Session Management for Tomcat: ServerConnectivityException

$
0
0

Hi Jens,

 

I turned on the highest level of logging for GemFire, and judging from the log file, the client is indeed able to access the locator...but it somehow still insists on trying to connect to a cache server at my local machine at port 40404.  If I run the cache server and locator on my local workstation, and configure the cache server to run on port 40404, all seems to be well.  So I wonder what I'm doing (or not doing) that causes the client to look at the default location for the cache server, rather than what's in my cache-client.xml file...

 

I've attached the log file.  My workstation's IP is 10.0.2.15.  The locator is running on my workstation at port 55224, and the cache server is also on my workstation, on port 40406.

 

Any ideas?

 

Thanks very much!

 

-Will


Viewing all articles
Browse latest Browse all 245504

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>