[ 
http://jira.jboss.com/jira/browse/JBCACHE-93?page=comments#action_12315763 ]
     
Bela Ban commented on JBCACHE-93:
---------------------------------

Doesn't compile, you have some HM specific classes. Please modify your code and 
resubmit it.
Thanks,

> Memory problem at repeated remote PUT
> -------------------------------------
>
>          Key: JBCACHE-93
>          URL: http://jira.jboss.com/jira/browse/JBCACHE-93
>      Project: JBoss Cache
>         Type: Bug
>     Versions: 1.2
>  Environment: * Windows cluster with two W2K servers, 2 JVMs per server 
> * JDK 1.4.2_05 
> * Application server is Oracle 9.0.3 AS 
> * one database server (Oracle)
>     Reporter: Henrik Nyberg
>     Assignee: Bela Ban
>      Fix For: 1.2.1
>  Attachments: JBCACHE-93.zip, SimpleCacheTest.java, SimpleCacheTest.java
>
>
> JBossCache does not properly garbage collect objects that are replicated 
> through the network and that replaces an already existing object in the local 
> cache. The existing local cache object that is being replaced by the remote 
> PUT is not garbage collected. 
> We have four caches in our setup, A, B, C, D. We describe the status for 
> cache A after the first iteration using an object sA1. We PUT that object 
> after every iteration into A using the same key ksA. 
> Iteration 1: 
> A updates status -> A(ksA,sA1) replicated to => B(ksA, sA1), C(ksA, sA1), 
> D(ksA, sA1) 
> Iteration 2: 
> A updates status -> A(ksA,sA2) replicated to => B(ksA, sA2), C(ksA, sA2), 
> D(ksA, sA2) 
> After iteration 2 the local object A(ksA,sA1) is probably correctly gc:ed, 
> since if we run this test in local mode the cache works reliably. The remote 
> objects B(ksA, sA1), C(ksA, sA1), D(ksA, sA1) however seem not to be 
> correctly gc:ed since the cache constantly eats memory when running in 
> replicated mode. 
> If we turn off the status replication, i.e. the repeated PUT of the status 
> object A(ksA, saN), the cache works like a charm. The only difference between 
> the two test cases is the PUT. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to