user10222290 wrote:I have 3 computers running pretty much continuously with time synchronised from one of the internet time servers. They never seem to be more than about 1/10 th second apart and any time corrections are very very small.
One server could want to synchronize it's OS time with another server when they connected each other for some business reasons.
Some threads have started to run before changing OS time, so these thread's sleep process will be influenced sometime seriously.I understand that but I would only expect this to be a problem when there is a significant change to the OS time. If each server is synchronized to a time server then the time corrections will be very very small.
If OS time was turned back some days, these thread could not wake up untill some days passed.Agreed but why would the "OS time be turned back some days" ?
sabre150 wrote:Yeah, I fully agree there.
I still don't see this 'bug' as a serious bug. I just see a design problem to be solved without changing the OS time on any computer.
user10222290 wrote:So we disagree on how serious the bug is. Since I designed my systems so that the server clock is synchronized to a time server and the actual time on the client clock does not really matter I don't see it as a serious bug. Since you have not taken these precautions you do!
I think this is two questions.
First, this is a bug, very basic bug, ever existed bug. Oracle should give fix as soon as quickly in my opinion, but that is not fact.
Second, I should be looking for another solution to avoid this problem not solve it. So that is not design problem, other solutions are not good suggestions.I don't really understand this. I designed my system to avoid the problem. I would like to know why you think it is not a design problem and why the other suggestions are not good.
In addition, my software is a product for many clients not a project for only client. So actual usage will be very complex and unpredictable. Maybe this bug is fatal problem in some cases. You guys should not think that this is not a serious problem.Presumably your clients are written in Java ( otherwise this thread would not be posted here) so since you have no control over the clients it seems you did not write the clients. Is that correct? If so then this is not your problem - it is a problem for those who did write the clients and you should raise a bug report against them.