Is there anything dangerous about using Thread.currentThread.sleep () in my main code?

Question

in my code i use

Thread.currentThread().sleep(sleepTime);

in the main part (without the Thread object) of the code.

It seems to be working fine, but I'm worried there might be some kind of hidden trap that will later bite my ass.

Is there a better way to make your main process sit for a while? or is it a prescribed methodology?

EDIT:

In response to why I do this ...

I have a process that connects via HTTP or FTP to remote hosts and does things.

In other words...

material...

connect to remote ...

do things with a remote connection ...

close connection ...

more stuff ...

repeat if necessary.

, . , , . , .

, , ...

...

...

MAIN ( )

a) "done"

b) , , , .

, , MAX_WAIT_TIME. , .

, ( ), while, , .

, ... - . , , , , , . , , ?

Answer 1

. , .

, .

Answer 2

? , , GUI - , .

, , .

- :

Thread.sleep(sleepTime);

currentThread() , . .

, IDE - (, ).

Answer 3

, 99 +% , , , . ?

Answer 4

, Thread.sleep - , . ( , , ), .

Answer 5

Thread.sleep, , InterruptedException.

Answer 6

""? , , , .

no-args, connect (SocketAddress, int), ( ). , .

setSoTimeout() , , read() , , . , .

Answer 7

AFAIR Thread.sleep() , Object.wait(long timeout). Object.wait(long timeout). , , , Object.wait(long timeout) .

Answer 8

People often use a timer to execute pending events, but I prefer ScheduleExecutorService. You can use the same thread pool for all your timeout actions. (You may have a thread pool of size 1)