Last updated on NOVEMBER 03, 2016
Applies to:Oracle Coherence - Version 3.5.3 and later
Information in this document applies to any platform.
Making an initial connection to a Coherence cluster, be it as a member of the cluster or over Coherence*Extend, to perform an operation does add overhead as the cache configuration is loaded and parsed and the connection is created and membership negotiated. Coherence lazily initializes services and as a result code using the API to work with caches won't join the cluster until the first call is made to perform work with a cache. This article will demonstrate a simple technique, suitable for JSP or Servlet based web applications which are interacting with a Coherence cluster using the Coherence for Java APIs. In this specific case Coherence*Web is not being used and this article is not applicable to that environment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms