MMBase

Can exist contemporary MMObjectNode's representing the same node -> problems with getRelations

Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.7.0
  • Fix Version/s: 2.0.0
  • Component/s: Core
  • Description:
    Hide
    original bugid: #6166
    Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance.
    I moved the 'relations' caches to org.mmbase.cache which fixes the problem with getRelations.

    But still, it seems a dangerous situation.
    Show
    original bugid: #6166 Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance. I moved the 'relations' caches to org.mmbase.cache which fixes the problem with getRelations. But still, it seems a dangerous situation.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michiel Meeuwissen added a comment - 2003-09-11 12:01
Can exist contemporary MMObjectNode's representing the same node -> problems with getRelations
Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance.
Show
Michiel Meeuwissen added a comment - 2003-09-11 12:01 Can exist contemporary MMObjectNode's representing the same node -> problems with getRelations Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance.
Hide
Permalink
Michiel Meeuwissen added a comment - 2003-09-11 12:03
Can exist contemporary MMObjectNode's representing the same node -> problems with getRelations
Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance.
I moved the 'relations' caches to org.mmbase.cache which fixes the problem with getRelations.

But still, it seems a dangerous situation.
Show
Michiel Meeuwissen added a comment - 2003-09-11 12:03 Can exist contemporary MMObjectNode's representing the same node -> problems with getRelations Because 'relation nodes' are cached in MMObjectNode instances. Invalidating this cache, works then only in one instance. I moved the 'relations' caches to org.mmbase.cache which fixes the problem with getRelations. But still, it seems a dangerous situation.
Hide
Permalink
Michiel Meeuwissen added a comment - 2009-09-21 21:35
WeakReferences are kept now in the NodeCache. This shoudl ensure that if a refence is hanging around somewhere, that it always be reused.
Show
Michiel Meeuwissen added a comment - 2009-09-21 21:35 WeakReferences are kept now in the NodeCache. This shoudl ensure that if a refence is hanging around somewhere, that it always be reused.
Hide
Permalink
Michiel Meeuwissen added a comment - 2009-11-30 10:52
fix was not yet ok.
Show
Michiel Meeuwissen added a comment - 2009-11-30 10:52 fix was not yet ok.

People

Dates

  • Created:
    2004-01-09 22:50
    Updated:
    2010-10-15 14:36
Atlassian JIRA (v4.1#519) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for MMBase Foundation. Try JIRA - bug tracking software for your team.