You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Bob Scheifler (JIRA)" <ji...@apache.org> on 2010/08/22 15:44:16 UTC

[jira] Created: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

SDM LookupCache multi-LUS stale proxy/discard problems
------------------------------------------------------

                 Key: RIVER-345
                 URL: https://issues.apache.org/jira/browse/RIVER-345
             Project: River
          Issue Type: Bug
          Components: net_jini_lookup
            Reporter: Bob Scheifler
         Attachments: changeset_r14156.diff

Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.

Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Peter Firmstone (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901171#action_12901171 ] 

Peter Firmstone commented on RIVER-345:
---------------------------------------

HI Bob,

Thanks for the patch, can you upload the SDM source file complete, there a couple of patch problems?

Regards,

Peter.

> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r14156.diff
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Updated: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by Peter Firmstone <ji...@zeus.net.au>.
Bob,

Your ServiceItemReg appears to have an addProxy(proxy, newItem)  method 
which returns boolean, that we don't.

Regards,

Peter.

Bob Scheifler (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Bob Scheifler updated RIVER-345:
> --------------------------------
>
>     Attachment: changeset_r14156.diff
>
>   
>> SDM LookupCache multi-LUS stale proxy/discard problems
>> ------------------------------------------------------
>>
>>                 Key: RIVER-345
>>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>>             Project: River
>>          Issue Type: Bug
>>          Components: net_jini_lookup
>>            Reporter: Bob Scheifler
>>         Attachments: changeset_r14156.diff
>>
>>
>> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
>> Patch attached is from an independently maintained version, so your line numbers may vary.
>>     
>
>   


[jira] Updated: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Bob Scheifler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Scheifler updated RIVER-345:
--------------------------------

    Attachment: changeset_r14156.diff

> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r14156.diff
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Bob Scheifler (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901232#action_12901232 ] 

Bob Scheifler commented on RIVER-345:
-------------------------------------

Sorry, scratch the incorrect reference to RIVER-324, the base multiple-LUS changes I meant to refer to hadn't been contributed back yet.  They are now attached, along with full source.

> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r13051.diff, changeset_r14156.diff, ServiceDiscoveryManager.java
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Bob Scheifler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Scheifler updated RIVER-345:
--------------------------------

    Attachment: changeset_r13051.diff
                ServiceDiscoveryManager.java

> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r13051.diff, changeset_r14156.diff, ServiceDiscoveryManager.java
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905723#action_12905723 ] 

Hudson commented on RIVER-345:
------------------------------

Integrated in River-trunk #318 (See [https://hudson.apache.org/hudson/job/River-trunk/318/])
    RIVER-345: re-apply patch by Bob Scheiffler


> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r13051.diff, changeset_r14156.diff, ServiceDiscoveryManager.java
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RIVER-345) SDM LookupCache multi-LUS stale proxy/discard problems

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RIVER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904049#action_12904049 ] 

Hudson commented on RIVER-345:
------------------------------

Integrated in River-trunk #310 (See [https://hudson.apache.org/hudson/job/River-trunk/310/])
    River-345 patch merged into ServiceDiscoverManager

Serialization Issue fixed in RemoteEvent and RemoteDiscoveryEvent, unit tests included.

Null pointer fixed in RemoteEvent, when null MarhalledObject is passed in and converted to a null MarshalledInstance.

Other changes relate to new method signatures, and the ExecutionContextManager.

The ExecutionContextManager will probably be removed.  The RevokeableDynamicPolicy will be moved out of the Public API, since this is still experimental.


> SDM LookupCache multi-LUS stale proxy/discard problems
> ------------------------------------------------------
>
>                 Key: RIVER-345
>                 URL: https://issues.apache.org/jira/browse/RIVER-345
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_lookup
>            Reporter: Bob Scheifler
>         Attachments: changeset_r13051.diff, changeset_r14156.diff, ServiceDiscoveryManager.java
>
>
> Fixes for some problems mostly introduced by the fix to RIVER-324, related to stale proxies and discard issues when multiple LUS are present.
> Patch attached is from an independently maintained version, so your line numbers may vary.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.