Article - CS338829

Error " java.rmi.RemoteException: Unable to locate cache server" in Slave Server Manager log and requests are responding slowly in Windchill

Modified: 02-Aug-2023   


Applies To

  • Windchill PDMLink 11.1

Description

  • Request is not responding from Web Browser; sometimes the UI is showing very quick; sometimes the result needs 5 or 10 minutes to show
  • This is Windchill Dedicated Cluster environment, Master has no any problem and all Slave Server Manager logs show error below
ERROR [ServerManagerRegistryPinger] wt.cache.server.wt.manager.jmx.ServerManagerRegistry - caught cache server call exception
java.rmi.RemoteException: Unable to put remote cache entry; nested exception is: 
    java.rmi.RemoteException: Unable to locate cache server; nested exception is: 
    wt.util.WTRemoteException: Unable to get server; nested exception is:
    java.rmi.ConnectException: Connection refused to host: <hostname>; nested exception is: 
    java.net.ConnectException: Connection refused: connect
    at wt.cache.RemoteCacheServer.putEntryInternal(RemoteCacheServer.java:404)
    at wt.cache.RemoteCacheServer.lambda$putEntry$19(RemoteCacheServer.java:333)
    at wt.cache.RemoteCacheServer.callTimeAndLogRemoteCallableLow(RemoteCacheServer.java:680)
    at wt.cache.RemoteCacheServer.callTimeAndLogRemoteCallable(RemoteCacheServer.java:652)
    at wt.cache.RemoteCacheServer.putEntry(RemoteCacheServer.java:330)
    at wt.cache.CacheManager.put(CacheManager.java:943)
    at wt.cache.CacheManager.put(CacheManager.java:931)
    at wt.manager.jmx.ServerManagerRegistry.pingMasterAndSlaves(ServerManagerRegistry.java:178)
    at wt.manager.jmx.ServerManagerRegistry$RegistryPinger.run(ServerManagerRegistry.java:322)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    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)
Caused by: java.rmi.RemoteException: Unable to locate cache server; nested exception is: 
    wt.util.WTRemoteException: Unable to get server; nested exception is:
    java.rmi.ConnectException: Connection refused to host: <hostname>; nested exception is: 
    java.net.ConnectException: Connection refused: connect
    at wt.cache.RemoteCacheServer.getCacheServer(RemoteCacheServer.java:630)
    at wt.cache.RemoteCacheServer.putEntryInternal(RemoteCacheServer.java:392)
    ... 15 more
Caused by: wt.util.WTRemoteException: Unable to get server; nested exception is:
    java.rmi.ConnectException: Connection refused to host: <hostname>; nested exception is: 
    java.net.ConnectException: Connection refused: connect
    at wt.manager.RemoteServerManager.remoteInvoke(RemoteServerManager.java:486)
    at wt.manager.RemoteServerManager.getServer(RemoteServerManager.java:278)
    at wt.manager.RemoteServerManager.getServer(RemoteServerManager.java:262)
    at wt.cache.RemoteCacheServer.getCacheServer(RemoteCacheServer.java:610)
    ... 16 more
Caused by: java.rmi.ConnectException: Connection refused to host: <hostname>; nested exception is: 
    java.net.ConnectException: Connection refused: connect
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129)
    at wt.manager.ServerManag
This is a printer-friendly version of Article 338829 and may be out of date. For the latest version click CS338829