You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Patricia Shanahan <pa...@acm.org> on 2010/12/01 18:34:44 UTC
Re: Does anyone understand OutriggerServerImpl?
Given the non-response, I assume I'll need to work out how it works, and
does not work, from the code. :-(
Patricia
Patricia Shanahan wrote:
> Specifically, does anyone understand
> com.sun.jini.outrigger.OutriggerServerImpl's match method?
>
> I'm investigating an intermittent unexpected match timeout under a
> stress workload with a lot of running threads.
>
> If someone happens to understand how this is supposed to work, it might
> save me some time. There is enough synchronization in
> OutriggerServerImpl to make me think there is some concurrency going on,
> but there does not seem to be enough use of volatile and/or
> synchronization to look memory model safe to me.
>
> Patricia
>
Re: Does anyone understand OutriggerServerImpl?
Posted by Gregg Wonderly <gr...@wonderly.org>.
I have not had a chance to go look at it to see what I remember about it yet.
Sorry
Gregg
On 12/1/2010 11:34 AM, Patricia Shanahan wrote:
> Given the non-response, I assume I'll need to work out how it works, and does
> not work, from the code. :-(
>
> Patricia
>
> Patricia Shanahan wrote:
>> Specifically, does anyone understand
>> com.sun.jini.outrigger.OutriggerServerImpl's match method?
>>
>> I'm investigating an intermittent unexpected match timeout under a stress
>> workload with a lot of running threads.
>>
>> If someone happens to understand how this is supposed to work, it might save
>> me some time. There is enough synchronization in OutriggerServerImpl to make
>> me think there is some concurrency going on, but there does not seem to be
>> enough use of volatile and/or synchronization to look memory model safe to me.
>>
>> Patricia
>>
>
>