Threads and System.in

[luis gallo]

I am trying to create 2 threads: thread1 does a process and keyboardThread accepts a user keyboard input. While the thread1 is running no user input should be accepted. When thread1 finishes keyboardThread should be active to accept a user input (for example like "stop"), for a specified given time, when a new thread1 will start, and blocking again user inputs.
To pause the keyboardThread a method called pause was created.
But how to put all this together?
Thanks a lot you guys for your help,
luis

here is the code:

public class Threads {
public static void main (String args[]){
long timeToRepeatProcess = 3000l;
Thread keyboardThread = new KeyboardThread();
keyboardThread.start();

Thread thread1;
while (true)
{
thread1 = new Thread1();
thread1.start();
try{
thread1.join();
Thread.sleep(timeToRepeatProcess);
} catch(InterruptedException e){}
} 


}
}
.........................
public class Thread1 extends Thread{
public void run(){
for(int i=0; i<5;i++){
System.out.println(getName()+" "+i);
try { 
Thread.sleep((long)(500*Math.random()));
 } catch (InterruptedException ioe) { }
}
}
}
..................

import java.io.*;
public class KeyboardThread extends Thread
{
BufferedReader bufferedReader;
boolean flag = true;

public void run() {
while (flag)
{
bufferedReader = new BufferedReader(new InputStreamReader(System.in)); 
String input="";
try { 
System.out.println("input something");
 input = bufferedReader.readLine(); 
} catch (IOException ioe) { }
}
}
public void pause(){
try{
if (bufferedReader!=null) bufferedReader.close();
}catch (java.io.IOException e){} 
flag = false;
}
}

[ April 02, 2003: Message edited by: Jim Yingst ]

[raimondas zemaitis]

I'd suggest you look into "Producer - consumer" example in Java Tutorial at Sun's site.
This is almost identical situation with yours.

[luis gallo]

Thanks I saw that - but I discovered the problem. The System.in stream when closed is closed and you cannot open it any more. That's why I experienced some strange behavior.

[Mr. C Lamont Gilbert]

Yes, I think closing the reader also closes the stream it was reading. Try just closing the thread itself, or setting some variable in the thread that lets it know the next time it gets info, to ignore the info and just end.