Thread implementations are different (JVM on some linux kernels uses child process and shared memory to implement multithreading, it can depend on JVM settings and implementation) and can produce many anomalies if code is not thread safe. The right way is to make application code thread safe, workarounds can help to hide a problem, but not to solve it.
—
I ran into this same issue on JDK 1.5/Linux/client mode, while never seeing it under Windows
—–
I saw the error on Linux, and can verify that the problem has (so far) gone away when I added -server to the JVM
--
Thanks & Regards,
B.Chandra Shekhar.
Software Engineer,
Jiva Infotech Pvt Ltd.
No comments:
Post a Comment