How are you configuring the client Pool? Could you post the code/config for how this is being done?
Thanks --Jens On Mon, Dec 4, 2017 at 7:33 AM, Vahram Aharonyan <[email protected]> wrote: > Hi All, > > > > Before starting cache servers (through > org.apache.geode.cache.server.CacheServer#start) > in our distributed system we are performing > org.apache.geode.cache.server.CacheServer#setPort > to set custom port on which this cache server will listen for clients. > > Also we do have locator service started and cluster server/clients are > powered up with configured locators lists - we are using locators for > discovery. > > > > But even with these, we see that after connecting to distributed system > our clients are trying to connect to their 40404 port: > > > > [warning 2017/12/04 17:29:51.688 AMT d830cfd9-509b-4443-960e-5412c8f9b516 > <poolTimer-DEFAULT-30835> tid=0x24d09] Could not connect to: Data1:40404 > > java.net.ConnectException: Connection refused (Connection refused) > > at java.net.PlainSocketImpl.socketConnect(Native Method) > > at java.net.AbstractPlainSocketImpl.doConnect( > AbstractPlainSocketImpl.java:350) > > at java.net.AbstractPlainSocketImpl.connectToAddress( > AbstractPlainSocketImpl.java:206) > > at java.net.AbstractPlainSocketImpl.connect( > AbstractPlainSocketImpl.java:188) > > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > > at java.net.Socket.connect(Socket.java:589) > > at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) > > at org.apache.geode.internal.net.SocketCreator.connect( > SocketCreator.java:971) > > at org.apache.geode.internal.net.SocketCreator.connect( > SocketCreator.java:934) > > at org.apache.geode.internal.net.SocketCreator.connectForClient( > SocketCreator.java:898) > > at org.apache.geode.cache.client.internal.ConnectionImpl. > connect(ConnectionImpl.java:103) > > at org.apache.geode.cache.client.internal.ConnectionFactoryImpl. > createClientToServerConnection(ConnectionFactoryImpl.java:136) > > at org.apache.geode.cache.client.internal.ConnectionFactoryImpl. > createClientToServerConnection(ConnectionFactoryImpl.java:259) > > at org.apache.geode.cache.client.internal.pooling. > ConnectionManagerImpl.prefillConnection(ConnectionManagerImpl.java:762) > > at org.apache.geode.cache.client.internal.pooling. > ConnectionManagerImpl.prefill(ConnectionManagerImpl.java:706) > > at org.apache.geode.cache.client.internal.pooling. > ConnectionManagerImpl$PrefillConnectionsTask.run2( > ConnectionManagerImpl.java:854) > > at org.apache.geode.cache.client.internal.PoolImpl$PoolTask. > run(PoolImpl.java:1315) > > at java.util.concurrent.Executors$RunnableAdapter. > call(Executors.java:511) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at org.apache.geode.internal.ScheduledThreadPoolExecutorWit > hKeepAlive$DelegatingScheduledFuture.run(ScheduledThreadPoolExecutorWit > hKeepAlive.java:259) > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1149) > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748) > > > > Actually this is getting blocked because we don’t have 40404 port open in > firewall configuration,. This does not seem to have any functional impact > as well, but logs of client are getting filled. > > Can someone advice how to keep out client from attempting to connect to > default 40404 port? Is there some configuration parameter that needs to be > set for clients? > > > > Thanks, > > Vahram. >
