Although this call works fine when invoked on a storage node in a standalone cluster, it fails when invoked on storage node in WebLogic.
I can still get around it by using CacheFactory.getCache(cacheName).getCacheService(), but this inconsistent behavior seems odd.
WL version: 12.2.1.4.3
Coherence version: 12.2.1.4.20
java.lang.IllegalArgumentException: No scheme found for service ess-coherence-rest-1.0:ESSReferenceGridService
at com.tangosol.net.ExtensibleConfigurableCacheFactory.ensureService(ExtensibleConfigurableCacheFactory.java:416)
at com.tangosol.net.CacheFactory.getService(CacheFactory.java:196)
at com.telus.csm.essc.coherence.invocable.HotKeyInvocable.run(HotKeyInvocable.java:81)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:16)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.run(InvocationService.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:74)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:54)