Cost/benefits of release() on NamedCache

Question

Based on the javadoc I'm a little concerned about the cost of calling release() on NamedCache every time the cache reference is looked up and used.
I'm running an app inside Weblogic 8.1 SP2 using the Coherence RAR. Every invocation of the cache will occur inside a transaction. I'm using the following as my basic pattern:
CacheAdapter adapter = getCacheAdapter();
try
NamedCache map = adapter.getNamedCache("CacheName", getClass().getClassLoader());
try
// Do cache stuff
finally
map.release();
finally
closeCacheAdapter(adapter);
Note that methods like this may be called hundreds of times inside a single transaction. Moreover, in some circumstances, 10k+ objects may be added to the cache (on system startup).
I guess my first question is, do I really need the map.release()? I'm always using the class loader of my cache wrapper, so I'd imagine that the container can't release that class loader in any case.
Second, how can I estimate how much time the release() call is going to cost me?
Any help would be appreciated. Thanks.
--Peter                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

Answer 1

Gene,
Thank you for your quick response. You've helped clarify the issue.
I would like to request a clarification in the javadoc in a future version. I can't seem to find anywhere in the doc where it says that you shouldn't call release() on a NamedCache returned by a CacheAdapter.
As far as the 10k+ goes, I'm not crazy about it either. But there is a legacy code base here, with legacy behavior. Essentially we're using the AppCycleListener interface to allow us to listen to startup events and preload the cache. This is effectively exclusive, but I believe that Weblogic treats it as if we're inside a transaction. I know that it did for our earlier revision, which used the server initializer interface.
Thanks again for the help.
--Peter