MMBase

Cookies.java: does not implement nodeRemoteChanged

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.7.0
  • Fix Version/s: 1.7.1
  • Component/s: Builders
  • Description:
    Hide
    original bugid: #6578
    When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie.

    Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum

    Solution:

        /**
        * remote change on a cookie object detected
        */
        public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {
            super.nodeRemoteChanged(machine,number,builder,ctype);
            return(nodeChanged(machine,number,builder,ctype));
        }
    Added in 1.7 and head
    Show
    original bugid: #6578 When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie. Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum Solution:     /**     * remote change on a cookie object detected     */     public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {         super.nodeRemoteChanged(machine,number,builder,ctype);         return(nodeChanged(machine,number,builder,ctype));     } Added in 1.7 and head

Activity

Hide
Marcel Maatkamp added a comment - 2004-09-15 16:33
Cookies.java: does not implement nodeRemoteChanged
When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie.

Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum

Solution:

    /**
    * remote change on a cookie object detected
    */
    public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {
        super.nodeRemoteChanged(machine,number,builder,ctype);
        return(nodeChanged(machine,number,builder,ctype));
    }
Show
Marcel Maatkamp added a comment - 2004-09-15 16:33 Cookies.java: does not implement nodeRemoteChanged When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie. Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum Solution:     /**     * remote change on a cookie object detected     */     public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {         super.nodeRemoteChanged(machine,number,builder,ctype);         return(nodeChanged(machine,number,builder,ctype));     }
Hide
Marcel Maatkamp added a comment - 2004-09-15 16:38
Cookies.java: does not implement nodeRemoteChanged
When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie.

Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum

Solution:

    /**
    * remote change on a cookie object detected
    */
    public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {
        super.nodeRemoteChanged(machine,number,builder,ctype);
        return(nodeChanged(machine,number,builder,ctype));
    }
Added in 1.7 and head
Show
Marcel Maatkamp added a comment - 2004-09-15 16:38 Cookies.java: does not implement nodeRemoteChanged When www1 inserts a cookie, this newly inserted cookie is not spotted by www2, because nodeRemoteChange is not implemented in Cookies.java Since www2 relies on a cache (which is never flushed) the cache is never cleaned and www2 will always return -1 when asked to produce a mmbase-number for this cookie. Since our database has a unique-constraint on de cookie-table, www2 cannot insert a cookie with the new id, produces an Exception and returns -1.. ad infinitum Solution:     /**     * remote change on a cookie object detected     */     public boolean nodeRemoteChanged(String machine,String number,String builder,String ctype) {         super.nodeRemoteChanged(machine,number,builder,ctype);         return(nodeChanged(machine,number,builder,ctype));     } Added in 1.7 and head

People

Dates

  • Created:
    2004-09-15 16:39
    Updated:
    2006-11-24 13:44
    Resolved:
    2006-11-24 13:44