A big problem: The Application Deads During Running.
Hi! everyone:
We four colleagues are developping an application use the observer/observerable pattern. In the normal case, this application starts about 20-40 threads some of which repait the GUI and some manipulate the database. With no exception and runtime error, the problem seemed strange: the computer will dead after 3 or 4 hours after start. We have tried resolve this problem through every way, but failed. And it's not seem to be the problem of system resource.
any advice will be appreciated.
thanks!
Dunhong Zhao.
Hi
Your question vould have much better chance of getting an answer if you included OS, JVM version and a description of how the computer dies (like for example does the OS die or just the program or does everything slow to a crawl).
On Windows 2000 I would recomend checking that you have not by mistake started to select text in a dos window since that stops any program that has output to that window.
Good luck
Samuel
Thanks for your response!
Our OS version is Windows98 4.0 and JVM is 1.3.0.
We have figured out that the system resources are over-consumed, especially the CPU. But we have no idea to find out where is the problem. We have redesign a thread that speeches the alarm messages and the thread that repaints the GUI, the application works better, but the problem still exists. I don't know much about java's garbage-collector mechanism, maybe this is the source of our problem? should I call the System.gc() every time when I finished the repainting? but I find it consumes more time this way. Maybe it's because we have used too much threads, and some of them cause a traffic jam?
thanks again.
I'm waiting for your advice.
