JCS should never be run in debug, except during development testing. I don't plan on removing any of the debug level logging. I run in INFO, always.
If you don't have a lateral configured then the isLateral value is irrelevant. Likewise, if you don't have a disk cache, the isSpool value is irrelevant. These just place restrictions on the elements. The local port is the port the client will listen to, a callback port. Every client on a particular machine must use a different port. The remote service port is the port the remote service will listen to. They are completely different. One is a client setting, the other is a server setting. The service port is defined on the server so you can control what port the client will communicate with the the server on. Without this, I think some range of ports willbe used. This can be problematic if you have a firewall between the client and the server. The registry port is the port the server registers with. This is the port the client should be configured to use. The client goes to the registry, finds the server and then talks to the server on the service port. Aaron --- Alistair Forbes <[EMAIL PROTECTED]> wrote: > Hi, > > I eventually got a working remote cache, but I hope > someone can help with a > few issues: > > On the client-side, what does the LocalPort mean? > jcs.auxiliary.RC.attributes.LocalPort=1102 > > If this is for the remote callback (for updates on > the remote server), does > this correspond to the remote config param: > remote.cache.service.port=1102 > > IsLateral defaults to true. Should I disable this is > only using a Remote RMI > cache? > jcs.default.elementattributes.IsLateral=false > > > Inserting new values on the remote cache works. But > when I update "put()" > values for existing keys I get the warnings below. > The updates seem to be > successful, but maybe something goes wrong. > > 12:42:03,011 DEBUG [CompositeCache] Updating > auxilliary caches > 12:42:03,012 DEBUG [CompositeCache] Auxilliary cache > type: 2 > 12:42:03,016 DEBUG [RemoteCacheServer] qlist.length > = 3 > 12:42:03,017 DEBUG [CacheEventQueue] Event entering > Queue for testCache: > PutEvent for key: KEY99 value: > null > 12:42:03,017 DEBUG [CacheEventQueue] Event entering > Queue for testCache: > PutEvent for key: KEY99 value: > null > 12:42:03,017 DEBUG [CacheEventQueue] Event entering > Queue for testCache: > PutEvent for key: KEY99 value: > null > 12:42:03,018 DEBUG [RemoteCacheServer] put took 10 > ms. > 12:42:03,024 WARN > [CacheEventQueue$AbstractCacheEvent] > java.rmi.ConnectException: Connection refused to > host: 127.0.0.1; nested > exception is: > java.net.ConnectException: Connection > refused > 12:42:03,024 WARN > [CacheEventQueue$AbstractCacheEvent] Error while > running > event from Queue: PutEvent for key: KEY0 value: > null. Dropping Event and > marking Event Queue as non-functional. > 12:42:03,025 INFO [CacheEventQueue$QProcessor] > QProcessor exiting for > CacheEventQueue [listenerId=80, cacheName=testCache] > 12:42:03,028 WARN > [CacheEventQueue$AbstractCacheEvent] > java.rmi.ConnectException: Connection refused to > host: 127.0.0.1; nested > exception is: > java.net.ConnectException: Connection > refused > > > > I have been running the remote server in DEBUG. Are > the thousands of lines > with "12:45:04,093 DEBUG [DoubleLinkedList] > returning fist node" really > useful or could someone comment this out (and I > guess it should be first and > no fist). > > > Appreciate any help. > > Cheers > Al > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
