Home » Modeling » EMF » [CDO] Locks management behavior.
| | | | |
| Re: [CDO] Locks management behavior. [message #428737 is a reply to message #428735] |
Sat, 28 March 2009 11:38   |
 Stephane fournier
Messages: 340
Registered: July 2009 |
Senior Member |
|
|
Hi Simon,
I'm not sleeping but I will be back to CDO stuff on Monday ;)
Thank you, Simon, for the quick fix. I will test that on Monday morning.
Stéphane.
On 28/03/2009 02:23, Simon McDuff wrote:
> You are probably sleeping: :-)
>
> Here the bugzilla:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270345
>
> Simon
>
> Simon McDuff wrote:
>> I fixed it... just waiting for the bugzilla !
>>
>> Simon
>>
>> Simon McDuff wrote:
>>>
>>> You are absolutely right. We have a problem in the core.
>>> Can you file a bugzilla please ?
>>>
>>> Simon
>>>
>>> Simon Mc Duff wrote:
>>>> Stéphane Fournier wrote:
>>>>
>>>>> Hi,
>>>>
>>>>> I'm testing the lock mechanism and I need some explanations.
>>>>
>>>>> Here is my scenario :
>>>>
>>>>> 1) Start an eclipse SDK
>>>>> 2) Open a CDOEditor from the CDO Session view on an existing
>>>>> resource (res1) with data.
>>>>> 3) Lock (writeLock)an object, let's say the root object 'A'.
>>>>
>>>>> 4) Start another eclipse SDK
>>>>> 5) Open a CDOEditor from the CDO Session view on the same resource
>>>>> (res1).
>>>>> 6) Try locking (writeLock) the root object 'A', as expected it is
>>>>> not possible you should have a NPE (see
>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270139).
>>>>> 7) Lock an object 'B'
>>>>> 8) Modify a B attribute whatever.
>>>>> 9) Save the resource res1.
>>>>
>>>>> 10) Go back to the first Eclipse sdk (first client)
>>>>> 11) Right click on object 'A', the writeLock is released.
>>>>
>>>>> Is it a normal behavior ?
>>>> No it is not the normal behavior.
>>>>
>>>>> If you lock an object A in a resource, any save operations from
>>>>> other open sessions release all locked objects ? I would think,
>>>>> only the locked objects owned by the session (which has performed
>>>>> the save operation) are released !
>>>> Not exactly. Locks are attached to views/transactions.
>>>> I will check our testcases first... after if I don`t see anything I
>>>> will look at the Ui of CDO to see what is happenning. Thank you for
>>>> the steps.
>>>>
>>>>
>>>>> Stephane.
>>>>
--
|
|
|
| Re: [CDO] Locks management behavior. [message #428767 is a reply to message #428737] |
Mon, 30 March 2009 07:58 |
Stephane fournier
Messages: 340
Registered: July 2009 |
Senior Member |
|
|
Hi Simon,
Are you back from the Con ? How was it ?
I've tested your fix, and it works :).
Stéphane.
Stéphane Fournier wrote:
> Hi Simon,
> I'm not sleeping but I will be back to CDO stuff on Monday ;)
> Thank you, Simon, for the quick fix. I will test that on Monday morning.
> Stéphane.
> On 28/03/2009 02:23, Simon McDuff wrote:
>> You are probably sleeping: :-)
>>
>> Here the bugzilla:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270345
>>
>> Simon
>>
>> Simon McDuff wrote:
>>> I fixed it... just waiting for the bugzilla !
>>>
>>> Simon
>>>
>>> Simon McDuff wrote:
>>>>
>>>> You are absolutely right. We have a problem in the core.
>>>> Can you file a bugzilla please ?
>>>>
>>>> Simon
>>>>
>>>> Simon Mc Duff wrote:
>>>>> Stéphane Fournier wrote:
>>>>>
>>>>>> Hi,
>>>>>
>>>>>> I'm testing the lock mechanism and I need some explanations.
>>>>>
>>>>>> Here is my scenario :
>>>>>
>>>>>> 1) Start an eclipse SDK
>>>>>> 2) Open a CDOEditor from the CDO Session view on an existing
>>>>>> resource (res1) with data.
>>>>>> 3) Lock (writeLock)an object, let's say the root object 'A'.
>>>>>
>>>>>> 4) Start another eclipse SDK
>>>>>> 5) Open a CDOEditor from the CDO Session view on the same resource
>>>>>> (res1).
>>>>>> 6) Try locking (writeLock) the root object 'A', as expected it is
>>>>>> not possible you should have a NPE (see
>>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270139).
>>>>>> 7) Lock an object 'B'
>>>>>> 8) Modify a B attribute whatever.
>>>>>> 9) Save the resource res1.
>>>>>
>>>>>> 10) Go back to the first Eclipse sdk (first client)
>>>>>> 11) Right click on object 'A', the writeLock is released.
>>>>>
>>>>>> Is it a normal behavior ?
>>>>> No it is not the normal behavior.
>>>>>
>>>>>> If you lock an object A in a resource, any save operations from
>>>>>> other open sessions release all locked objects ? I would think,
>>>>>> only the locked objects owned by the session (which has performed
>>>>>> the save operation) are released !
>>>>> Not exactly. Locks are attached to views/transactions.
>>>>> I will check our testcases first... after if I don`t see anything I
>>>>> will look at the Ui of CDO to see what is happenning. Thank you for
>>>>> the steps.
>>>>>
>>>>>
>>>>>> Stephane.
>>>>>
> --
|
|
|
| Re: [CDO] Locks management behavior. [message #428805 is a reply to message #428767] |
Tue, 31 March 2009 01:25 |
Simon Mc Duff
Messages: 596
Registered: July 2009 |
Senior Member |
|
|
Stéphane Fournier wrote:
> Hi Simon,
> Are you back from the Con ? How was it ?
Yes I'm back.. and so many things to do.
Eclipse Con (my first one) was very very good! I think I will go each
year now!! :-) I meet many people... Eike and I meet for the first
time!! It was memorable!! :-) It is good to put face on name !! Maybe
you will be there next year.
Simon
>
> I've tested your fix, and it works :).
Good!!
>
> Stéphane.
>
> Stéphane Fournier wrote:
>
>> Hi Simon,
>> I'm not sleeping but I will be back to CDO stuff on Monday ;)
>
>> Thank you, Simon, for the quick fix. I will test that on Monday morning.
>
>> Stéphane.
>
>
>> On 28/03/2009 02:23, Simon McDuff wrote:
>>> You are probably sleeping: :-)
>>>
>>> Here the bugzilla:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270345
>>>
>>> Simon
>>>
>>> Simon McDuff wrote:
>>>> I fixed it... just waiting for the bugzilla !
>>>>
>>>> Simon
>>>>
>>>> Simon McDuff wrote:
>>>>>
>>>>> You are absolutely right. We have a problem in the core.
>>>>> Can you file a bugzilla please ?
>>>>>
>>>>> Simon
>>>>>
>>>>> Simon Mc Duff wrote:
>>>>>> Stéphane Fournier wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>
>>>>>>> I'm testing the lock mechanism and I need some explanations.
>>>>>>
>>>>>>> Here is my scenario :
>>>>>>
>>>>>>> 1) Start an eclipse SDK
>>>>>>> 2) Open a CDOEditor from the CDO Session view on an existing
>>>>>>> resource (res1) with data.
>>>>>>> 3) Lock (writeLock)an object, let's say the root object 'A'.
>>>>>>
>>>>>>> 4) Start another eclipse SDK
>>>>>>> 5) Open a CDOEditor from the CDO Session view on the same resource
>>>>>>> (res1).
>>>>>>> 6) Try locking (writeLock) the root object 'A', as expected it is
>>>>>>> not possible you should have a NPE (see
>>>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=270139).
>>>>>>> 7) Lock an object 'B'
>>>>>>> 8) Modify a B attribute whatever.
>>>>>>> 9) Save the resource res1.
>>>>>>
>>>>>>> 10) Go back to the first Eclipse sdk (first client)
>>>>>>> 11) Right click on object 'A', the writeLock is released.
>>>>>>
>>>>>>> Is it a normal behavior ?
>>>>>> No it is not the normal behavior.
>>>>>>
>>>>>>> If you lock an object A in a resource, any save operations from
>>>>>>> other open sessions release all locked objects ? I would think,
>>>>>>> only the locked objects owned by the session (which has performed
>>>>>>> the save operation) are released !
>>>>>> Not exactly. Locks are attached to views/transactions.
>>>>>> I will check our testcases first... after if I don`t see anything I
>>>>>> will look at the Ui of CDO to see what is happenning. Thank you for
>>>>>> the steps.
>>>>>>
>>>>>>
>>>>>>> Stephane.
>>>>>>
>
>> --
>
>
|
|
|
Goto Forum:
Current Time: Sat Apr 27 01:47:02 GMT 2024
Powered by FUDForum. Page generated in 0.03220 seconds |
] 
Search
Help
Register
Login
Home
