Have you tried it? What effect are you seeing that you feel may be because of this?
In general, it should have no effect, that does not mean it will not in some extreme cases, but it definately should not, and I (personally) don't know of any instances where it has.
I assume you are having some type of problem? If, so, then like I said,
explain your problem (fully) and we will better be able to help you.
> well, the problem that i felt was that when i run my
> class files on my machine(windows xp, dual core),
> Thread.sleep(60000) sleeps for 1 minute. but when i
> run it on a linux machine, Thread.sleep(60000) sleeps
> for 2 minutes. my application has a lot of threads.
I can't be 100% sure, but I'm pretty sure that sleep(60000) doesn't sleep for 2 minutes on the other machine.
> > well, the problem that i felt was that when i run
> my
> > class files on my machine(windows xp, dual core),
> > Thread.sleep(60000) sleeps for 1 minute. but when
> i
> > run it on a linux machine, Thread.sleep(60000)
> sleeps
> > for 2 minutes. my application has a lot of
> threads.
>
> I can't be 100% sure, but I'm pretty sure that
> sleep(60000) doesn't sleep for 2 minutes on the other
> machine.
I, wholeheartedly, agree.
Due to timing issues it may seem to sleep a few milliseconds more, but not double.
Of course, if there is a "real-time" (or even simply higher than the Java app) priority program running that is using a lot of the CPU it may seem like it sleeps a lot longer than 60000, but that is a different issue.