Upgrade tangosol to a new version

There are some problems that are fixed in the new version of tangosol. In particular a customer reported memory leak that is fixed in a new version of tangosol.

Bellow is my interaction with tangosol support

--------------------------------------------------------------------------------------------------------
Hi Anatoli,

The leak was caused by non-constant thread pool size (old ThreadLocalObject implementation was assuming that number of threads is pretty much constant). As a fix old impl was replaced with java.lang.ThreadLocal .

Upgrading to a new version should be pretty straightforward - all you need to do is to replace tangosol.jar and coherence.jar with new ones.

Regards,
Dimitri

On Sep 18, 2007, at 9:56 PM, Anatoli Kazatchkov wrote:

> Hi Dimitri,
>
> Thanks a lot for a quick response.
> I know that for support I should go through oracle-wide support centre, but I was unable to create an account on
> https://metalink.oracle.com and I really need to follow up with this email.
>
> It is our customer who is experiencing memory leak in production and it is not easy for us/him to update coherence library. The more realistic scenario is to provide some kind of work around for him.
>
> Are there any known workarounds?
> Is the problem specific for WebSphere?
> Can you provide a little bit more details on COH-994 (or can I access and read it somewhere?) so that we can come up with a workaround?
> Is there any specific scenario that triggers this memory leak?
>
> Thanks.
> Anatoli.
>
>
> Tangosol Support wrote:
>> Hi Anatoli,
>>
>> This looks like a known issue (COH-994) which was fixed in 3.3. You can download it here: http://www.oracle.com/technology/products/coherence/index.html
>>
>> Regards,
>> Dimitri
>>
>> On Sep 18, 2007, at 5:20 AM, Anatoli Kazatchkov wrote:
>>
>>> Hi guys,
>>>
>>> We have a problem using tangosol on a WebSphere. To be more specific we leak memory and get OutOfMemory exception. Tangosol Coherence Cache is used as a caching mechanism for hibernate.
>>>
>>> Having done some investigation on a heap dump we found that there are a lot of com.tangosol.util.ThreadLocalObject. Each of the object references another ThreadLocalObject (as can be seen on the screen shot). It also references ThreadPoolWorker that contains PageContext which probably the major contributor to OutOfMemory.
>>>
>>> To help us investigate further can you please answer these questions:
>>> How ThreadLocalObject is used and why ThreadLocalObject references another ThreadLocalObject?
>>> Can application specific code lead to such situation?
>>>
>>>
>>> Thanks.
>>> Anatoli.
>>> <Screenshot-IBM HeapAnalyzer.png>
>>