ProActive Scheduler

Node owner check (when releasing node) seems to be broken with PAMR

Details

  • Description:
    Hide
    When using Scheduler/RM exposed through PAMR, the nodes cannot be freed :
    [WARN 2009-05-18 11:41:18,505] [RM.RMUserImpl.freeNodes] An attempt to free a node by another user (won't be performed) rmi://tagada.activeeon.com:6695/PA_JVM676109048_GCMNode-0

    It seems that two refs on the same active object exposed through PAMR are not equals.


    Note that in any case, the node owner mechanism should rely on ID instead of references.
    Show
    When using Scheduler/RM exposed through PAMR, the nodes cannot be freed : [WARN 2009-05-18 11:41:18,505] [RM.RMUserImpl.freeNodes] An attempt to free a node by another user (won't be performed) rmi://tagada.activeeon.com:6695/PA_JVM676109048_GCMNode-0 It seems that two refs on the same active object exposed through PAMR are not equals. Note that in any case, the node owner mechanism should rely on ID instead of references.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christian Delbé added a comment - 18/May/09 4:16 PM
See PROACTIVE-670
Show
Christian Delbé added a comment - 18/May/09 4:16 PM See PROACTIVE-670
Hide
Permalink
Christian Delbé added a comment - 18/May/09 5:11 PM
Fixed by 12677 :compare ID instead of reference. See PROACTIVE-670 for ref comparison.
Show
Christian Delbé added a comment - 18/May/09 5:11 PM Fixed by 12677 :compare ID instead of reference. See PROACTIVE-670 for ref comparison.

People

Dates

  • Created:
    18/May/09 2:04 PM
    Updated:
    04/Nov/09 5:01 PM
    Resolved:
    18/May/09 5:11 PM
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for ProAcrtive. Try JIRA - bug tracking software for your team.