You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Vandahl (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/30 22:04:32 UTC

[jira] [Resolved] (JCS-82) Lateral Cache does not work with multiple writes to same object: OOS does not get reset

     [ https://issues.apache.org/jira/browse/JCS-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vandahl resolved JCS-82.
-------------------------------

       Resolution: Fixed
    Fix Version/s: jcs-1.4-dev

Fixed in SVN
                
> Lateral Cache does not work with multiple writes to same object: OOS does not get reset
> ---------------------------------------------------------------------------------------
>
>                 Key: JCS-82
>                 URL: https://issues.apache.org/jira/browse/JCS-82
>             Project: JCS
>          Issue Type: Bug
>          Components: TCP Lateral Cache
>    Affects Versions: jcs-1.3
>         Environment: JDK1.6 
> ALL Operating Systems
>            Reporter: Nikunj Trivedi
>            Assignee: Aaron Smuts
>              Labels: OOS, cache, jcs, lateral, reset_frequency
>             Fix For: jcs-1.4-dev
>
>
> In a Lateral cache environment, If a mutable object is written to JCS multiple times, only original copy is written every time by ObjectOutputStream of LateralTCPSender.
> This seems to be a known issue as per some forums, but not fixed since it could not be replicated.
> My case is as follows: Server A & B has a common mutable object (say StringBuffer) in cache. 
> JDK1.6 Server A:
> StringBuffer obj=new StringBuffer("Initial");
> jcs.put("key",obj);//This is visible to Server B
> obj.append("Append");
> jcs.put("key",obj);//This gets ignored, B still sees obj="Initial"
> I recompiled with LateralTCPSender.RESET_FREQUENCY from 70 to 1, it works fine.
> I suggest, either RESET_FREQUENCY should be 1 or use oos.writeUnshared.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira