Community
Participate
Working Groups
Using 20100202-1656_eclipse-jee-helios-M5-win32.win32.x86_64 I can create a dynamic web project, run it, debug it, etc., all seems fine. Oh, and that's using the built in "preview server" (which uses Jetty under the covers). If I then shutdown the workbench, there is a VM "crash", a message pops up that says "no exit data" and a VM dump left in my eclipse directory. Which I'll attach. I'll investigate if this happens for 32 bit package as well. and after that, I guess other types of servers. If I explicitly "stop" the server first, the workbench shuts down like normal.
Created attachment 158060 [details] core dump from one of the crashes
I'm moving this to WTP Server Tools, because it also happened using Tomcat 6.0.24 64 bit distribution. So ... I'm thinking there is something in servertools shutdown that, somehow, assumes 32 bit VM? Angel, do you all ever test using a 64 bit VM and 64 bit version of Eclipse?
Created attachment 158081 [details] screen captures of VM error dialog This is a screen capture of the VM's "crash" dialog. Not sure its useful, but just in case. Also, I should be explicit, I do not see the problem using a 32 bit VM and the 32 bit version of Eclipse. I only tried on a fresh, toy workspace, but if this prevents proper shutdown of the workbench (so that session data is not properly saved) then it would be a 'major' problem, and not just 'normal'. I have also tried with only the JEE package ... I have not tried just by "building my own from zip files" so that might be another thing to investigate. As far as I know, it could be "package specific" (i.e. something wrong with the JEE package build), but I think best if server tools takes a look.
Oh, and for those that don't keep it book marked, the 64 bit JEE package can be obtained from "nightly" builds on http://www.eclipse.org/epp/download.php
Hmm interesting. No we don't typically try 64 bits. From the dump thread I don't see anything that give me a clue as to what could be occuring. I wonder if this happens in linux 64 as well?
David, Have you had this problem happened again? since the dump shows a gpf error, I doubt this is anything regarding our java code. Perhaps try upgrading your JDK, to a more recent, or using a different JDK just to see if we can reproduce the problem.
I haven't seen again. Not that I've tested it all that much. But if no one else sees it, its not a problem. (You know .. like a tree that falls in the forest when no one is around makes no sound :)
