concurrent-programming

I am working on the Executors in java to concurrently run more threads at a time. I have a set of Runnable Objects and i assign it to the Exceutors.The Executor is working fine and every thing is fine.But after all the tasks are executed in the pool ,the java program is not terminated,i think the Executor takes some time to kill the threads.please anyone help me to reduce the time taken by the executor after executing all tasks. The ExecutorService class has 2 methods just for this: shutdown() and shutdownNow() . After using the shutdown() method, you can call awaitTermination() to block until

I am a little bit confused about the use of yield() method in Java, specifically in the example code below. I've also read that yield() is 'used to prevent execution of a thread'. My questions are: I believe the code below result in the same output both when using yield() and when not using it. Is this correct? What are, in fact, the main uses of yield() ? In what ways is yield() different from the join() and interrupt() methods? The code example: public class MyRunnable implements Runnable { public static void main(String[] args) { Thread t = new Thread(new MyRunnable()); t.start(); for(int i

Is there a Mutex object in java or a way to create one? I am asking because a Semaphore object initialized with 1 permit does not help me. Think of this case: try { semaphore.acquire(); //do stuff semaphore.release(); } catch (Exception e) { semaphore.release(); } if an exception happens at the first acquire, the release in the catch block will increase the permits, and the semaphore is no longer a binary semaphore. Will the correct way be? try { semaphore.acquire(); //do stuff } catch (Exception e) { //exception stuff } finally { semaphore.release(); } Will the above code ensure that the

I have the following situation: I have 2 JVM processes (really 2 java processes running separately, not 2 threads) running on a local machine. Let's call them ProcessA an ProcessB . I want them to communicate (exchange data) with one another (e.g. ProcessA sends a message to ProcessB to do something). Now, I work around this issue by writing a temporary file and these process periodically scan this file to get message. I think this solution is not so good. What would be a better alternative to achieve what I want? haylem Multiple options for IPC : Socket-Based (Bare-Bones) Networking not