Glad to hear that I could help!
Hey Martin, sorry for the slow response on this one - I've attached a thread dump for you in the hope you can shed some light on this, I'm now 10+ minutes into waiting for STS to open.
Thanks in advance, Stephen.
STS Thread dump.txt.zip
and after a force quit, pretty much the same:
STS Thread dump2.txt.zip
D'ya think this is the offending thread?
"Worker-0" prio=5 tid=116849000 nid=0x1184c0000 waiting for monitor entry [1184bf000]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.eclipse.wst.server.core.internal.Server.clearM oduleCache(Server.java:2454)
Question is though, if :
$ ps -ef | grep glassfish
502 8477 4519 0 12:07pm ttys000 0:00.00 grep glassfish
reveals nothing, who's holding the monitor..?
Last edited by stephenkerrmurphy; Aug 28th, 2012 at 06:10 AM.
That is an interesting thread dump. It looks like there is something causing a locking between different parts of the initialization process. Is this the case when you open an empty new workspace as well?
Hey Martin, no actually a spanking new workspace loads pretty quickly, as we'd expect - I'm still having the slow performance once loaded issues, but I'll try the patch and sts.ini setting recommended and get back to you.
I also try and recreate my workspace afresh and let you know how I get on.
Thanks for trying to resolve this for us mate, much appreciated - Stephen.
Has the patch been withdrawn Martin? Can't see it in the Dashboard and getting access denied from the update site...
The patch is not showing up on the Dashboard if it is already installed. Did you use a fresh installation of STS and that piece is not showing up? Once you installed that, it should not be there anymore. To check, you can activate the "show installed" checkbox on the top right of the extension install on the dashboard to verify. The patch is specific to the STS installation, not the workspace.
The "access denied" message is something that you get when you browse to that URL, since it doesn't have a index html page. It is just an update site. You can put that URL into the "install new software" dialog instead.
Sorry my bad, got it thanks...
Unfortunately still have the hang on STS start though, same thread dump, but this time it's a completely new workspace with my (git) projects re-imported..
STS Thread dump3.txt.zip
Any further thoughts?
Also are you planning (or already have) upgraded to Juno SR1 (http://stackoverflow.com/questions/1...dler-processes) to address the JPA Java Change Event handler processing?
Thanks again, Stephen.
Last edited by stephenkerrmurphy; Aug 28th, 2012 at 09:29 AM.
Thanks for the additional thread dumps. That is helpful!!!
And yes, we will update to Juno SR1 with STS 3.1.0 (planned for beginning of October, shortly after Juno SR1 is out).
I'm having performance issues related to upgrading an STS 2.9 project to 3.0.
I see the "JPA Java Change Event Handler (Waiting)" message after every code change. Occasionally, the STS 3.0 screen appears dimmed, with a white-ish display.
Other times, the UI of STS 3.0 lags considerably. It seems "JPA Java Change Event Handler (Waiting)" is constantly being processed.
Am I better off returning to STS 2.9 until the SR1 update of Juno can be folded into STS 3.0? I've already installed the STS 3.0 patch.
Thanks in advance.
What you could also do is to start with an Eclipse SDK 3.8 and install STS and all the other pieces manually:
The other way is to continue to use STS 2.9 and wait for STS 3.1.0 that will be based on Juno SR1.