Threading guidance to avoid potential deadlock...

[Mattias Sands�ter]

I get the warning "Warning: To avoid potential deadlock, operations that may block, such as networking, should be performed in a different thread than the commandAction() handler."

It starts when I start to access the file system, more specific when I try to list the roots with listRoot(). I know this would be fixed with threading but I am not so good at it. I did do some tries but without success.

Should I move all my filesystem methods into some threaded class or just parts of it? Please guide me into the right direction.

[pradeep u nair]

hi friend
call your function inside this block of code in the listener
new Thread(new Runnable(){
public void run()
{
try{
//your function call
}catch(Exception e){}
}
}).start();

hope this helps
Pradeep

[Mattias Sands�ter]

Thanks for trying help me.

Do you mean that when I arrive to a filesystem sensetive method call like listRoots() I just do like this:

Enumeration e = null;
new Thread(new Runnable(){
public void run(){
try{
e = FileSystemRegistry.listRoots();
}catch(Exception e){
;
}
}
}).start();

I tried this, but it couldn�t reach the e-variable from inside the inner class.
[ May 05, 2006: Message edited by: Mattias Sands�ter ]