Java 6 - is anybody suddenly getting deadlocks in previously working code?
I just started getting deadlocks in code that's been running for some time on my mac pro 2nd edition (8 cores, 2 gb ram)
This code was using java 6 from Apple previously - with the upgrade to 1.6.0_13, it's now hanging in the middle of its run.
This code has been running for quite some time. Before OSX supported java 6 it also ran on java 5 no problem. it just started hanging after this update.
Is anybody else having a similar problem? Can the java update be uninstalled?
This code was using java 6 from Apple previously - with the upgrade to 1.6.0_13, it's now hanging in the middle of its run.
This code has been running for quite some time. Before OSX supported java 6 it also ran on java 5 no problem. it just started hanging after this update.
Is anybody else having a similar problem? Can the java update be uninstalled?
Comments
I just started getting deadlocks in code that's been running for some time on my mac pro 2nd edition (8 cores, 2 gb ram)
This code was using java 6 from Apple previously - with the upgrade to 1.6.0_13, it's now hanging in the middle of its run.
This code has been running for quite some time. Before OSX supported java 6 it also ran on java 5 no problem. it just started hanging after this update.
Is anybody else having a similar problem? Can the java update be uninstalled?
And the log files say what?
And the log files say what?
The log files say nothing useful. It's a long running multi-threaded application using eight threads. I have it print a status message every four minutes. I get the status message at 8:54am and that's the last thing I see.
The app is still running now (noon) with nothing coming out.
The application usually takes up every core - CPU utilization of 700%+ on my eight core MacPro.
Right now it's taking up 54% of one CPU. I've been trying kill -3 to get a thread dump and see what's going on, but nothing happens.
Any ideas?
The log files say nothing useful. It's a long running multi-threaded application using eight threads. I have it print a status message every four minutes. I get the status message at 8:54am and that's the last thing I see.
Leopard has a weird issue with the console logs not updating properly. The console log seems to use a different system from the other log files. In console, they show up in columns - Time, Sender and message, where other logs are just files.
Try running the app from the command line and it should print the message output to the terminal window.
Leopard has a weird issue with the console logs not updating properly. The console log seems to use a different system from the other log files. In console, they show up in columns - Time, Sender and message, where other logs are just files.
Try running the app from the command line and it should print the message output to the terminal window.
Thank you - I'll try that and let you know if that works. I'm running this from cron currently.
I'll try it both ways and see if I get the thread dumps both ways
The log files say nothing useful. It's a long running multi-threaded application using eight threads. I have it print a status message every four minutes. I get the status message at 8:54am and that's the last thing I see.
The app is still running now (noon) with nothing coming out.
The application usually takes up every core - CPU utilization of 700%+ on my eight core MacPro.
Right now it's taking up 54% of one CPU. I've been trying kill -3 to get a thread dump and see what's going on, but nothing happens.
Any ideas?
Perhaps Dtrace will help?
http://java.sun.com/javase/6/docs/te...vm/dtrace.html