MyEclipse :: View topic - initializing java tooling...... and then off to vapor space.

MyEclipse: initializing java tooling...... and then off to vapor space.

lchalupa - Sep 19, 2006 - 09:48 PM
Post subject: initializing java tooling...... and then off to vapor space.

I start MyEclipse. IDE comes up. in lower right hand corner a message is displayed "initializing java tooling". I click on detail button to monitor, it never shows any progress and just hangs.

I also noticed that when I go into the prefereneces for a project, if I click on the build path button, the entire project will hang and I have to kill the java process to escape.

How do I diagnose this problem. Everything was working fine this morning.

I'm running version 3.2 of eclipse and 5.0 GA of MyEclipse.

I've tried rebooting the machine but that didn't help. I am able to recreate the problem everytime I start the IDE.

lee

support-rkalla - Sep 20, 2006 - 06:51 AM
Post subject:

Lee,
The first thing to do is to restart using the -clean option as outlined here:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10280.html

see if that helps, if it doesn't, try a new workspace:
File > Switch Workspace > C;\tempworkspace, hit OK to restart.

Now try those operations again, are they working?

infinity2heaven - Feb 02, 2009 - 07:35 PM
Post subject: it still hangs

I'm an IntelliJ user, unfortunately using myeclipse 7 since that is the default tool that our client uses. I've used myeclipse for a few days, although terribly slow I was able to setup my webapps and use it. However since the last 3 hours (that's a 360$ billing rate to the client), I've been stuck with this problem.

I tried "-clean" option and rebooted atleast eight times today.

I can't imagine that my client has purchased this software that doesnt even know how to start on its own. A pity, that I'm actually spending time in a forum to beg for help. (on how to start myeclipse without hanging)

infinity2heaven - Feb 02, 2009 - 09:23 PM
Post subject:

Deleted entire workspace, works now. Takes another half hour hr to
"setup" the workspace, perspective, server settings

support-rkalla - Feb 04, 2009 - 06:52 PM
Post subject:

infinity2heaven,

Was the workbench locking up on startup like clockwork -- in exactly the same spot every time? How long did you let it sit before killing the process and trying again?

infinity2heaven - Mar 27, 2009 - 02:31 PM
Post subject: the problem is back

I can't believe I have the same problem again, and on searching on google, I revert back to this same forum!

I think myeclipse completely goes for a toss when you add plugins in the dropin folder. It opens up and hangs forever at "Initializing Java Tooling ...." (30%) and that's it.

Do I want to delete my workspace? No.

I'm forwarding this case study to my manager to convince them to use IntelliJ or atleast the default eclipse since this is unacceptable.

SirronD - Apr 03, 2009 - 05:18 PM
Post subject: RE: the problem is back

I have the same problem. I try to start MyEclipse and it freezes at "Initializing Java Tooling" Always at 59%. The behavior is always the same, as soon as it gets to 59% the window showing memory jumps from around 300M to over 500M. And then the system freezes.

As a test I modified my myeclipse.ini from ".... -Xms512M -Xmx512M ..." to "... -Xms1024M -Xmx1024M ..."

That seemed to allow me to get past the problem. However, I do not know why all of a sudden I need to dedicate so much memory for this IDE. Also, after starting and getting past the Initializing Java Tooling, memory used drops back to the normal 300M range.

What is happening in "Initializing Java Tooling" and why does it all of a sudden need so much extra memory?

infinity2heaven - Apr 03, 2009 - 05:19 PM
Post subject:

I stopped using myeclipse. (Use core eclipse instead). It's not worth fighting for

SirronD - Apr 29, 2009 - 10:37 PM
Post subject: ugly work-around found for this issue (at least in my case)

ok, I found one very ugly work-around for this.

The work-around is to move the .project file from my largest project (move to some other location outside of workspaces). This allows myeclipse to start. Of course that project will show in the Navigator, but not operate. After eclipse finishes with "Initializing Java Tooling", then move the .project file back to its correct location, and open the project.

MyEclipse is doing some large task with the project. And another large task with initializing java tooling. Together these chew up all memory.

I don't know what it is doing with the project, and I cannot find any options or preferences to stop it from doing whatever it is doing. But removing the .project file stops it.

Also, note, after you move the project file back, you will need to wait as it does whatever it is doing before you try to do anything inside. (I usually try to wait 5-10 minutes - get morning coffee or tea during this time or catch up on net surfing.

In my case the projects are PHP projects, so there is no compiling. And the .project file contains only the name of the project within the xml body. So I don't know why it has to work so hard, but it does.

One very frustrating thing I have found with eclipse.
There is no way to see what is running in the background. So no way for an end-user of the application to address any problems. There is a "Progress" window which on occasion shows some titles, but it does not show most things (for example it does not show that eclipse is working with project at all)

support-rkalla - May 04, 2009 - 07:58 PM
Post subject: RE: ugly work-around found for this issue (at least in my ca

SirronD,

Can you paste the contents of the .project file as well as the .classpath file here of the offending project?

Also can you give me a quick overview of what you have in /dropins, as well as what 3rd party plugins you have installed into MyEclipse?

SirronD - May 04, 2009 - 11:31 PM
Post subject:

~/eclipse/dropins is empty. I don't know if there is another specific to MyEclipase. If so, tell me where to look.

here is the project file (although there is really not much to see).

Code:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>includes</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
</buildSpec>
<natures>
</natures>
</projectDescription>

I have the following (according to the "Add/Remove Software")
Scala Eclipse Plugin
Spring AJDT Extension
Spring Mylyn Extension
MyEclipse UML2
SFTP Plug-in
PHPeclipse
Visualiser Plug-in
Cross Reference Core Plugin
Cross Reference UI Plugin
MyLyn Task List (Required)
Remote System Explorer End-User Runtime
Eclipse FTP and WebDAV Support
Subversion Client Adapter - Required
Subversion Native Library Adapter (JavaHL) - Strongly Re....
Subclipse - Required

My projects are all PHP code, and I use Subversion/Subclipes to checkout/update/commit regularly in my project.

support-rkalla - May 05, 2009 - 11:58 PM
Post subject:

SirronD, thanks for the info. Given the project I have no idea what's happening during the "Java Tooling" Stage that is taking so long -- could be any one of those plugins. We'll try and reproduce/investigate this on our end.

SirronD - May 06, 2009 - 01:16 AM
Post subject:

Thanks.

Also, I don't think it is "Java Tooling" (or at least not java tooling by itself). I think it is something else going on with the project. So removing the project allows eclipse to start, and java tooling to run. Then moving the project file back causes whatever happens there. It is when both try to occur at the same time that the memory gets chewed up.

Also If I remember to "Close ALL" before I exit eclipse, it will start up OK. But that is an extra step that really should not be required (or if it is required, there should be a "close all on exit" preference.

gbrinkmann - May 20, 2009 - 09:49 AM
Post subject:

SirronD wrote:

Also If I remember to "Close ALL" before I exit eclipse, it will start up OK. But that is an extra step that really should not be required (or if it is required, there should be a "close all on exit" preference.

Thanks for the workaround hint (closing projects on exit)

It would be cool if the devs could wrap some major exception catching and timeout handling around startup and project initialization...

james_beninger - Sep 10, 2009 - 02:31 PM
Post subject: My workaround

I found that this problem can be solved by deleting (or renaming) the following directory:

WORKSPACE_HOME/.metadata/.plugins/org.eclipse.core.resources/.projects

This doesn't seem to have effected my workspace adversely.

support-nipun - Sep 10, 2009 - 05:06 PM
Post subject: RE: My workaround

Quote:

Thank you for posting your findings here for us.

anand.natarajan - Sep 11, 2009 - 10:18 PM
Post subject: Workable Solution

I had the same issue, i went to the workspace's metadata folder and deleted the .lock file. started myeclipse and it worked fine...

ricke999 - Nov 24, 2009 - 07:29 PM
Post subject: RE: My workaround

I backed up the <workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects directory and then deleted all of the files, leaving the directory structure intact. After restarting with the -clean option everything seems to be working.

ricke999 - Nov 24, 2009 - 07:36 PM
Post subject: RE: My workaround

I left out a step: I had to re-share the projects in SVN.

Right-click the project -> Share -> SVN -> Next > Finish

It might take a few seconds.

kamb - Dec 18, 2009 - 12:10 PM
Post subject: more info

I have had the same problem recently. Initializing java tooliing hangs (this time) at 1%

The previously mentioned work-around of getting rid of the .metadata/[..]/.projects dir worked.

But to add a bit of maybe useful extra information:

This started after I had an interruption in my network, and eclipse was unable to save my open files or my workspace. In fact, I had to force-quit eclipse.

On restarting, when it hung in Initializing Java Tooling, and I went to quit the app, a dialog came up that there were ongoing user processes:
Initializing Java Tooling, with the apparent subtask of
configuring classpath containers

maybe that is helpful.

cheers,

kamb - Dec 18, 2009 - 12:12 PM
Post subject: RE: more info

Oh, I should probably mention that I am running on Windows, and I am NOT running a MyEclipse distro.

wchen@cs.stanford.edu - Dec 20, 2009 - 05:44 PM
Post subject: RE: My workaround

James,

Thanks for the trick. It seems the quick dirty way to get around this long-standing MyEclipse issue.

In addition, I think you have to move the old .projects directory back. Otherwise, you will loose project information, such as CVS settings.

gogodil - Dec 27, 2009 - 02:41 PM
Post subject: Re: Workable Solution

anand.natarajan wrote:

I had the same issue, i went to the workspace's metadata folder and deleted the .lock file. started myeclipse and it worked fine...

Simply deleting the .lock file also solved the problem for me running Eclipse 3.5.1 on Ubuntu.

cd@pobox.com - Feb 21, 2010 - 05:52 PM
Post subject: Re: My workaround

james_beninger wrote:

Thanks for the tip - I was having this problem with *regular* Eclipse, and forcing it to rebuild what seems to be a resource cache solved it.

And just to clean MyEclipse's name on this (I used to be a happy MyEclipse user - it is worth its money when you don't want auto-setup of everything): this seems to be a "regular Eclipse" issue.

Regards

archville - Mar 06, 2010 - 06:13 PM
Post subject: RE: Re: My workaround

Has anyone been able to find a long term solution to this problem ? I first encountered this middle of Feb 2010, and still haven't had success.

I've tried most, if not all, of the approaches on this thread and have had only temporary relief (stays working for 1-2 workspace restarts). The fastest way I've been able to reproduce this problem, after applying one of the relief mechanisms is shown as follows:

1. Remove the org.eclipse.jdt.core folder within <Workspace-Dir>\.metadata\.plugins\
2. Restart <Installation-Dir>\MyEclipse 8.0\myeclipse.exe
3. View the start-up Progress tab show. It shows
Checking for Updates ...(100%)
and then everything is fine
4. Close and restart MyEclipse again, and viewing the Progress tab shows


Checking for Updates ...(100%)

Initializing Java Tooling...(1%)


And hangs there forever. Using the stop button in the Progress panel shows

Initializing Java Tooling (Cancel Requested)

and hangs there. Closing the Workspace window has similar results. A smaller panel pops up instead and displays something like


Progress Information
Saving workspace.
Saving workbench state.
Initializing Java Tooling (Cancel Requested)


MyEclipse 8.0 Installation Details
---------------------------------------

MyEclipse 8.0 Plugin View After Auto Update
-------------------------------------------------------

The Workbench Logs after the cleanup shows
---------------------------------------------------------------

The Workbench Logs after the restart (during the hangup) shows pretty much the same except for the timestamps and a WidgetMethodHandler object
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Apart from taking up valuable screen space on this post, I wonder if the logs are any help at all !? One point I wish to make is that I've been using version 8.0 since it came out and I "HAVE NOT" added any new plugins since Dec 2009. The problem first showed up somewhere in the middle of Feb, after the periodic and automated MyEclipse update check during startup. I did not have this or any related problem with Release 7.5.

Support guys, any idea why this happens ?

Thanks,
archville

archville - Mar 09, 2010 - 12:41 AM
Post subject: MyEclipse 8.0 - "Intializing Java Tooling ..." Pro

Does Support have no antidote for this problem ??

support-joy - Mar 09, 2010 - 12:06 PM
Post subject: RE: MyEclipse 8.0 - "Intializing Java Tooling ..."

archville,

Can you copy and paste contents of your MyEclipse.ini file? MyEclipse.ini(configuration settings) file is located in your MyEclipse installation dir. Can you verify if the contents is in the similar lines?

Quote:

-startup
../../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
../../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-install
C:/Program Files/Genuitec/Profiles/MyEclipse 8.x
-vm
C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll
-configuration
configuration
-vmargs
-Xmx768m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m

archville - Mar 10, 2010 - 07:03 AM
Post subject: Re: RE: MyEclipse 8.0 - "Intializing Java Tooling ...&a

The contents of my myeclipse.ini is pretty much the same as yours, except for the installation path, and one of the memory parameters, '-Xmx'. Here it is for your reference:

support-joy - Mar 10, 2010 - 09:10 AM
Post subject: RE: Re: RE: MyEclipse 8.0 - "Intializing Java Tooling .

archville,

Thank you for the details. Can you bump up the -Xmx to 768, restart your IDE and give it a shot?

archville - Mar 10, 2010 - 03:55 PM
Post subject: Re: RE: Re: RE: MyEclipse 8.0 - "Intializing Java Tooli

support-joy wrote:

...Can you bump up the -Xmx to 768, restart your IDE and give it a shot?

I just did. The "Initializing Java Tooling (1%)" just sits there. At least for 15 mins.

Support-Brian - Mar 11, 2010 - 11:39 AM
Post subject: RE: Re: RE: Re: RE: MyEclipse 8.0 - "Intializing Java T

Sometimes this could be caused by a "workspace gone bad" or a really heavy workspace. Do you have many large projects, with say many JARs or library containers attached to them? If you keep a smaller number of projects open, does that help?

You could try switching to a new workspace - (File > Switch Workspace) and import projects en mass or piecemeal into the new workspace from your old workspace. Doing a few projects at a time will help figure out if a particular project or group of projects are causing the problem. If the workspace was "bad" for some reason, you should have no problems in the new workspace with all your projects. Please let us know how it goes.

archville - Mar 11, 2010 - 09:07 PM
Post subject: Re: RE: Re: RE: Re: RE: MyEclipse 8.0 - "Intializing Ja

Support-Brian wrote:

Do you have many large projects, with say many JARs or library containers attached to them?

This is almost true. Roughly 20 projects, with some having as many as 25+ jars. Mostly dependencies.

Support-Brian wrote:

If you keep a smaller number of projects open, does that help?

I've had at least 10 projects added to the same workspace after the 1st occurrence of this problem in Feb. So I've added versus deducting. However, my earlier attempts to troubleshoot by addressing a few projects at a time was uneventful.

Support-Brian wrote:

You could try switching to a new workspace - (File > Switch Workspace) and import projects en mass or piecemeal into the new workspace from your old workspace. Doing a few projects at a time will help figure out if a particular project or group of projects are causing the problem. If the workspace was "bad" for some reason, you should have no problems in the new workspace with all your projects. Please let us know how it goes.

Now this, I had tried at least a few times, thanks to someone else who made the same suggestion.
-- Created a NEW workspace
-- Copied a set of projects at a time (using Operating System copy) from the old, into the new workspace
-- Imported the Projects within the new workspace
-- And so on...

This DID make a difference for a week or less. I'd estimate a few (< 5/6) MyEclipse restarts during that time period. I remember adding a few new projects during this period before the problem manifested again. I'm starting to wonder if these events coincided with using the new embedded Maven 2.

Regarding the volume of jars associated with projects in a workspace, I will attempt to isolate the larger projects into their own workspace, and migrate the rest to another. If this approach seems to temporarily subdue the problem, we won't know until many days later about the combination that may trigger its return. This problem may have deeper roots than just project size.

archville

archville - Apr 27, 2010 - 11:11 PM
Post subject:

This ugly beast has reared its head again. Roughly 5-6 weeks later. I may have stumbled into one of the reasons why this initiates, since I caught it at the first attempt. This incident had little to do with # of projects/jars.

After I started MyEclipse, and before the updates/tooling progress were complete, I attempted to open one of the projects in the current workspace. The IDE became non-responsive for at least 12+ mins before I closed the window on it. The next time MyEclipse was restarted, the freeze at 1% Java Tooling took effect.

If support is interested in any logs this time around, please let me know.

archville

support-joy - Apr 29, 2010 - 01:33 PM
Post subject:

archville,

I will escalate your issue to dev team member. They will get back to you on this
Sorry for the inconvenience.

archville - May 05, 2010 - 05:59 PM
Post subject:

Support,
Any feedback on this ? This is a continuing problem that needs a permanent resolution. All temporary fixes are only that - very temporary !! Nothing has changed in my environment since my last major post on this topic.

archville

Support-Brian - May 12, 2010 - 07:38 AM
Post subject:

archiville,

What is the last version of MyEclipse you have tried this in? The problem you describe does indicates an issue with the startup process - difficult to reproduce but something that changes significantly even between dot release of Eclipse (and these problems do exist in vanilla Eclipse as well). MyEclipse. 8.5 is based on 3.5.2 so you may experience different behavior here. In our last report you were using MyEclipse 8 which for this sort of issue would be very significantly different.

I have a few questions:
1) MyEclipse version currently using
2) Any plugins installed beyond just MyEclipse - like Subversive or Subclipse?
3) Suggestion: Edit your myeclipse.ini file and add "-clean" on a new line after the "-configuration configuration" line. This will increase the startup time to some extent, not too much. You could then remove the -clean argument or leave it in. If you have an active workspace in which you can reproduce this problem, does this fix it?

tomwolk - Jul 26, 2010 - 01:22 PM
Post subject:

Hi folks,

just had the same issue after I installed the latest JDK and deleted all the rest. The core bug seems to be in the classloading of webprojects but providing enough memory for the classes schould be a good workaround.

In my eclipse.ini I use following:

Code:

-vmargs
-Xms128m
-Xmx512m
-XX:MaxPermSize=128m

The MaxPermSize is important since that's where eclipse runs short of memory.

support-joy - Jul 28, 2010 - 09:47 AM
Post subject:

tomwolk,

Thank you for sharing your notes with us.