0
What else can I help you with?
What is dfference between synchronization and asynchronization in java with example?
synchornisation is the process where more than one thread can be accessed by accesssing the shared object of the class.By syncornisation we can have the communication between threads.if one thread works then another thread automatically stops
Explain why interrupts are not appropriate for implementing synchronization?
Because they are completely unrelated things? Synchronization can be implemented with semaphores or mutexes.
Difference between yield method and sleep in java?
Thread.sleep(long milliseconds): The thread's sleep method sends the current thread into Non-Runnable state for the specified amount of time. But, this doesn't cause the thread to loose ownership of the acquired monitors. So, if the current thread is into a synchronized block/method, then no other thread will be able to enter that block/method.The Sleep method throws 'InterruptedException' if another thread interrupts it.There is another variant of the 'sleep()' method where it accepts two arguments - one, long milliseconds, and second, int nanoseconds. Simply put, this method causes the current thread to sleep for the specified number of milliseconds plus the specified number of nanoseconds. The second argument 'int nanoseconds' can acquire a value of the range 0-999999.wait() method: The wait() method also sends the current thread into Non-Runnable state like the sleep() method. But, the difference between the two is that in case of 'wait()' the locks are released before going into Non-Runnable state, so that any other thread that is waiting on the object can use it (Unlike the Sleep method - This is the big difference) Another apparent difference is that 'wait()' is an instance method, while sleep() is a static method. The method 'wait()' should be called for an object only when the current thread has already acquired lock for that object. This causes the current thread to wait either another thread invokes the 'notify()' method or the 'notifyAll()' method for this object, or a specified amount of time has elapsed and after that the thread starts participating in thread scheduling process to acquire the monitor of the object to proceed further.There are three variants of this method in the 'Object' class:-public final void wait(long timeout)public final void wait(long timeout, int nanoseconds)public final void wait()All the three methods throw InterruptedException & IllegalMonitorStateException. The first two may also throw IllegalArgumentException.The wait() method causes the current thread to place itself in the wait set for this object and then to relinquish any and all synchronization claims on this object. After the execution of this method invocation, the thread becomes disabled for any scheduling purposes and lies dormant until one of the following things happen:-* Any other thread invokes 'notify()' method this object and the thread under consideration is arbitrarily chosen as the thread to be awakened. * Any other thread invokes 'notifyAll()' for this object. * Any other thread interrupts the thread under consideration. * The specified amount of time has elapsed (in case first two variants of wait() are used) After any of the four above mentioned events happens, the thread is removed from the wait set for this object and re-enabled for thread scheduling. It'll compete for the rights to synchronize on the object in an usual manner and it'll keep doing this until it acquires control on the object and gains all the synchronization claims on the object, which it had acquired at the time of 'wait()' invocation. This means that after the return from wait() method, the synchronization state of object and of the thread will be exactly the same as it was before the wait() invocation.
Is an EUE thread a Non-Pressure sealed thread?
EUE thread is a pressure sealed thread as usual completion pup joints thread
Can a thread create a process?
No, a thread can't create aprocess, because the environment of the thread is a part of a process which created this thread.
What is thread synchonisation in os?
The thread synchronization is done for sharing of a common resource, to find the no. of resources in use, its count ,maximum resources in use... To establish this the various synchronization tools used are.. Events Waitable Timer
What is interprocess synchronization?
Processes might need to communicate to each. Interprocess of synchronization is the?æ management of resource among process. It ensures only a single thread (process) access a resource at a particular time.
What is dfference between synchronization and asynchronization in java with example?
synchornisation is the process where more than one thread can be accessed by accesssing the shared object of the class.By syncornisation we can have the communication between threads.if one thread works then another thread automatically stops
Synchronization in java?
Threads communicate primarily by sharing access to fields and the objects reference fields refer to. This form of communication is extremely efficient, but makes two kinds of errors possible: thread interference and memory consistency errors. The tool needed to prevent these errors is synchronization.
How does a monitor prevent multiple threads from concurrently executing inside the monitor?
A monitor is an exclusive locking mechanism available to every managed object. When you are writing instance methods within a class to update and read instance fields, you can utilize the monitor of the current object to synchronize access. A thread can use a monitor to block other threads for the period of time during which it is making a series of updates to an object. That means a monitor can be used in order to block other threads from seeing any single update until all of the updates have been completed.A monitor type presents a set of programmer-defined operations that are provided mutual exclusion within the monitor. The monitor type also contains the declaration of variables whose values define the state of an instance of that type, along with the bodies of procedures or functions that operate on those variables.The monitor construct ensures that only one process at a time can beactive within the monitor. However, the monitor construct, as defined so far, is not sufficiently powerful for modeling some synchronization schemes. For this purpose, we need to defineadditional synchronization mechanisms. These mechanisms are provided by the condition construct. A programmer who needs to write a tailor-made synchronization scheme can define one or more variables of type condition:condition x, y;The only operations that can be invoked on a condition variable are wait ()and signal(). The operation x.waitO ;means that the process invoking this operation is suspended until anotherprocess invokes x . s i g n a l ( ) ;The x. signal () operation resumes exactly one suspended process. If noprocess is suspended, then the signal () operation has no effect; that is, thestate of x is the same as if the operation had never been executed .This is showing how monitor is operating
What is difference between synchronization and inter thread communication?
Synchronization is the process by which, access to the objects by threads are controlled and at at time only one thread can access an object. This is done to ensure that there are no dirty read/write operations. If multiple threads access the same data simultaneously, we may end up with inconsistent data. To avoid it, we place such code in synchronized blocks/methods to ensure integrity of data. Inter thread communication is the process by which java threads can communicate with one another. They communicate to one another through some commands like wait, notify, notifyall etc.
Which provides better quality an interlaced monitor or noninterlaced monitor?
A non interlaced monitor is one where all the scan lines occur sequentially, whereas an interlaced monitor is one where all the odd scan lines occur, followed by all of the even scan lines, in alternating painting of the phospher.
What are some strategies for resolving thread contention in a multi-threaded application?
Some strategies for resolving thread contention in a multi-threaded application include using synchronization mechanisms like locks, semaphores, and mutexes to control access to shared resources, implementing thread-safe data structures, reducing the scope of synchronized blocks, and using thread pooling to limit the number of active threads. Additionally, optimizing the design of the application to minimize the need for shared resources can help reduce thread contention.
When was Transactional Synchronization Extensions created?
Transactional Synchronization Extensions was created in 2012.
Why current is not concidered while synchronization?
current is load dependent,after synchronization only current will flow
What are examples of synchronization?
SONET
What is thread safety and synchronization?
Thread safety is a term that is applied to a language's ability to safely modify the same memory location concurrently in multiple processes. A language that does not have thread safety cannot guarantee program correctness. Synchronization is one of the most common means of offering thread safety. To understand thread safety, you must first understand multitasking. A program running multiple tasks (called threads) at once does not actually run all of the threads at the exact same time. Instead, each task takes up a small sliver of the CPU's total processing time, and when it reaches a stopping point, or when an amount of time has elapsed, it is suspended, set aside, and the next task gets a chance to run. This happens so quickly that users have the appearance of many things running at once. However, when two threads are trying to use the same memory resource, bad things can happen if they are interrupted at the wrong time. Consider these two threads: Thread 1: Load x. Add 5 to x. Store this result in x. Thread 2: Load x. Add 10 to x. Store this result in x. Now, if thread 1 runs before or after thread 2, there is no problem. However, if thread 1 is interrupted, you might see a bug: X = 0 Thread 1: Load X (0) into reg1 (0). Thread 1: Add 5 to reg1 (5). Thread 2: Load x (0) into reg2 (0). Thread 2: Add 10 to reg2 (10). Thread 2: Store reg2 (10) into x (0 -> 10). Thread 1: Store reg1 (5) into x (10 -> 5). In case you missed it, you'll see that if 10 and 5 are added to x, the total should be 15. However, thread 2 preempted thread 1 at a critical point, and so thread 2 was unaware that x should have been 5, not 0. Since thread 1 had no idea that thread 2 was going to preempt the processing at that time, it didn't know that X changed to 10, and thus clobbered thread 2's work when it resumed. In order to fix this, you add a synchronization lock. This prevents a thread from starting after a critical point until the critical point has passed. It would look like this: Thread 1: Lock x. Load x. Add 5 to x. Store x. Unlock x. Thread 2: Lock x. Load x. Add 10 to x. Store x. Unlock x. Now, the logic might look like this: Thread 1: Lock x. Thread 1: Load x. Thread 1: Add 5 to x. Thread 2: Lock x. (Cannot lock, so wait). Thread 1: Store x. Thread 2: Lock x. Thread 2: Load x. Thread 2: Add 10 to x. Thread 2: Store x. In this example, thread 2 was forced to wait on the other thread. While overall processing speed is reduced, the system successfully added the numbers in order without losing any results; x would be 15 after those two threads were done.
