Synclock clarification

[Johan Karlsson]

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource twice the
add function will execute without problems, right? And other threads trying
to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly only
refer to a single object, that is there is not "nested" locking, a deadlock
can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[drew]

True and yes there can be deadlocks still if you have more than one thread
and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource twice the add function will execute without problems, right? And other threads trying to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly only
refer to a single object, that is there is not "nested" locking, a deadlock can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[drew]

True and yes there can be deadlocks still if you have more than one thread
and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource twice the add function will execute without problems, right? And other threads trying to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly only
refer to a single object, that is there is not "nested" locking, a deadlock can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[Johan Karlsson]

Hi and thank you for the reply!
On the second question,

Could you explain to me how that deadlock would occure. That is, there is no
code that will lock two object within the same thread. Example, thread tA
will never lock object oA and oB at the same time, it will first lock oA, do
its business and then lock (and release oA) object oB. Thread tB will have
the same "rules" and never lock oA and oB at the same time.

I just cant figure out how a deadlock can occure then? But I'm kindofa
newbie in the threadworld.

Thanks

/Johan
"drew" <[e-mail]> wrote in message
news:uq**************@TK2MSFTNGP11.phx.gbl...

True and yes there can be deadlocks still if you have more than one thread
and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource twice

the

add function will execute without problems, right? And other threads

trying

to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly only refer to a single object, that is there is not "nested" locking, a

deadlock

can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[Johan Karlsson]

Hi and thank you for the reply!
On the second question,

Could you explain to me how that deadlock would occure. That is, there is no
code that will lock two object within the same thread. Example, thread tA
will never lock object oA and oB at the same time, it will first lock oA, do
its business and then lock (and release oA) object oB. Thread tB will have
the same "rules" and never lock oA and oB at the same time.

I just cant figure out how a deadlock can occure then? But I'm kindofa
newbie in the threadworld.

Thanks

/Johan
"drew" <[e-mail]> wrote in message
news:uq**************@TK2MSFTNGP11.phx.gbl...

True and yes there can be deadlocks still if you have more than one thread
and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource twice

the

add function will execute without problems, right? And other threads

trying

to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly only refer to a single object, that is there is not "nested" locking, a

deadlock

can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[drew]

You're correct in your assumption; as long as you code carefully and make
sure that you always release the first object before trying to acquire the
second object you should never have any deadlocks. You'll also want to make
sure you have finally's around to release the locks as well... with
threading always land on the carefull side.

drew
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:uI**************@tk2msftngp13.phx.gbl...

Hi and thank you for the reply!
On the second question,

Could you explain to me how that deadlock would occure. That is, there is no code that will lock two object within the same thread. Example, thread tA
will never lock object oA and oB at the same time, it will first lock oA, do its business and then lock (and release oA) object oB. Thread tB will have
the same "rules" and never lock oA and oB at the same time.

I just cant figure out how a deadlock can occure then? But I'm kindofa
newbie in the threadworld.

Thanks

/Johan
"drew" <[e-mail]> wrote in message
news:uq**************@TK2MSFTNGP11.phx.gbl...

True and yes there can be deadlocks still if you have more than one thread

and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource

twice the

add function will execute without problems, right? And other threads

trying

to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly

only refer to a single object, that is there is not "nested" locking, a

deadlock

can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan

[drew]

You're correct in your assumption; as long as you code carefully and make
sure that you always release the first object before trying to acquire the
second object you should never have any deadlocks. You'll also want to make
sure you have finally's around to release the locks as well... with
threading always land on the carefull side.

drew
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:uI**************@tk2msftngp13.phx.gbl...

Hi and thank you for the reply!
On the second question,

Could you explain to me how that deadlock would occure. That is, there is no code that will lock two object within the same thread. Example, thread tA
will never lock object oA and oB at the same time, it will first lock oA, do its business and then lock (and release oA) object oB. Thread tB will have
the same "rules" and never lock oA and oB at the same time.

I just cant figure out how a deadlock can occure then? But I'm kindofa
newbie in the threadworld.

Thanks

/Johan
"drew" <[e-mail]> wrote in message
news:uq**************@TK2MSFTNGP11.phx.gbl...

True and yes there can be deadlocks still if you have more than one thread

and more than one lockable resource.
"Johan Karlsson" <jo************@adnome.se> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hi all!

I just need a true or false answer for this statement.
Consider having a piece of code that boils down to this

Dim a = new ArrayList
SyncLock a
SyncLock a
a.Add("Something")
End SyncLock
End SyncLock

The question: Since it is the same thread that locks the resource

twice the

add function will execute without problems, right? And other threads

trying

to lock will just have to wait 'til their turn?

Another question while im at it: If all lockings withing an assembly

only refer to a single object, that is there is not "nested" locking, a

deadlock

can never occour? Right or wrong? Need some more clarification? :)

Thanks!

/Johan