Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>That is the whole concept of synchronization, if you are taking a lock on an object (or a class), none of the other threads can access any synchronized blocks.</p> <p>Example </p> <pre><code>Class A{ public void method1() { synchronized(this)//Block 1 taking lock on Object { //do something } } public void method2() { synchronized(this)//Block 2 taking lock on Object { //do something } } } </code></pre> <p>If one thread of an Object enters any of the synchronized blocks, all others threads <strong>of the same object</strong> will have to wait for that thread to come out of the synchronized block to enter any of the synchronized blocks. If there are N number of such blocks, only one thread of the Object can access only one block at a time. Please note my emphasis on <strong>Threads of same Object</strong>. The concept will not apply if we are dealing with threads from different objects. </p> <p>Let me also add that if you are taking a lock on <strong>class</strong>, the above concept will get expanded to any object of the class. So if instead of saying <code>synchronized(this)</code>, I would have used <code>synchronized(A.class)</code>, code will instruct JVM, that irrespective of the Object that thread belongs to, make it wait for other thread to finish the synchronized block execution.</p> <p>Edit: Please understand that when you are taking a lock (by using synchronized keyword), you are not just taking lock on one block. You are taking lock on the object. That means you are telling JVM "hey, this thread is doing some <strong>critical work</strong> which might change the state of the object (or class), so don't let any other thread do any other <strong>critical work</strong>" . Critical work, here refers to all the code in synchronized blocks which take lock on that particular Object (or class), and not only in one synchronized block. </p>
    singulars
    1. This table or related slice is empty.
    1. POTwo Synchronized blocks execution in Java
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKamal
    1. USKamal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTwo Synchronized blocks execution in Java
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CObut the synchronized blocks are completely independent. so why is it getting blocked.
      singulars
      1. PO
      1. USMobiz Tech Team
    2. COYou need to understand this- you are not taking lock on a block, you are taking a lock on the Object (or class)
      singulars
      1. PO
      1. USKamal
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload