I am using Rational Application Developer 7.5.3.When I open my workspace it shows "Initializing Java Tooling" - 1% for long time.It gets hanged up when I try to open any file in my workspace.
I have referred How can I disable "Initialize Java Tooling" on Eclipse startup? but couldn't get my problem resolved.
Kindly assist.
Eclipse's Bugzilla has a few bug reports about the product hanging during "Initializing Java Tooling". These bugs seem to have been resolved. You're using RAD 7.5.x which is based off a very old edition of Eclipse, so I wouldn't be surprised if the underlying Eclipse of RAD 7.5.x suffers from those "Initializing Java Tooling" bugs.
I remember encountering many of these "Initializing Java Tooling" hangs in previous versions of RAD, but haven't seen those in quite a while.
You may wish to upgrade to a later RAD version (the latest at the moment is 9.0.1). If that doesn't help, a PMR with IBM would be the way to go.
Related
I recently let STS update itself from 3.1 to 3.5 and now I'm getting errors regarding the MatchLocator class. I'm not sure what MatchLocator is, but it appears to be a core Eclipse service.
When I open STS I get 'Initializing Java Tooling' has encountered a problem.
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
After it's open I get an error marker for each applicationContext.xml in each project that says
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/core/search/matching/MatchLocator
No lines are marked, just that it's a "Spring Beans Problem"
When I close STS I get Problmes occurred while trying to save the state of the workbench with details:
An internal error occurred during: "Initializing Java Tooling".
org/eclipse/jdt/internal/core/search/matching/MatchLocator
I've tried downloading a fresh copy of STS 3.5 to a separate directory and each of my workspaces still have this error so I suspect the problem is in the .metadata directory. A couple other Stack Overflow posts have recommended deleting the workspace .metadata or .metadata\.plugins directories and letting Eclipse rebuild them for that workspace but that didn't fix it either.
I'm running on a Mac with these plugins: m2e Maven Integration and associated plugins, Scala IDE, STS and StartExplorer.
Is there a way to restore the missing MatchLocator files?
Fixed this by removing this file in each workspace:
[workspace]/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
Opening STS from the command line (on mac: ./STS.app/Contents/MacOS/STS -clean) and viewing stack traces on startup led me to this answer: https://stackoverflow.com/a/13884461/1637003
Now all the random ways this bug was manifesting itself have gone away: JUnit tests not running, cmd+clicking to open declarations not working, various MatchLocator errors on startup and shut down.
One of the simplest solution for this problem is that we have to launch a new eclipse IDE and again we install STS tool plugin then import your project.
It works well and u get free from errors.
I am Running Eclipse Kelper Build id: 20130614-0229 (the latest at time of writing)
I have installed the Web Tools Platform (WTP) and I am using a 'static web project'.
I keep getting an error alert box popping up with the error
Could not initialize class org.eclipse.jst.j2ee.project.facet.IJ2EEFacetConstants
Okay I have searched high and low for a solution, but of course the solution seems to be different for every version of eclipse. I went to a bug post on this at https://bugs.eclipse.org/bugs/show_bug.cgi?id=389968
but the advice was just to "get the right version of EPP for your workspace"
Okay so that advice is no help at all. How does one know what is the right version of their workspace? what do they mean by that anyway? by "for your workspace" are they referring to your version of Eclipse? or is that a separate issue?
I saw another response to this issue on stack overflow for Eclipse Juno, but it was simply a link to a temporary patch update site which no longer exists. Someone else on that thread claimed that Kelper had a fix for all of this. Clearly that is not the case and the people at Eclipse.org do not think this is a bug.
From update site, install below item:
|> Web, XML, Java EE and OSGi Enterprise Development
* Eclipse Java EE Developer Tools
I would guess that you are seeing this issue because you have not installed enough of WTP. That doesn't make this problem less of an issue, but at least you can look for workarounds in how you construct your installation. The easiest solution is to grab the "Eclipse IDE for Java EE Developers" package.
http://www.eclipse.org/downloads/
You need to install the JST Enterprise Core feature, org.eclipse.jst.enterprise_core.feature
I am trying to install the new WSO2 Developer Studio 2.1.0 into Eclipse. It appeared to install successfully, but when I try to start Eclipse it hangs forever (e.g. > 30 minutes) with the message “Loading Workbench”. On one attempt (after leaving it for maybe 45 minutes), it actually got as far as bringing up the Eclipse main window, but it hung there with the message “Marketplace DND Initialization”. The Eclipse process is steadily using about 25% of my CPU.
There is an error in my Eclipse workspace/.metadata/.log file:
!ENTRY org.eclipse.ui.navigator 4 0 2012-10-17 11:20:18.303
!MESSAGE An extension already exists with id "org.eclipse.ui.navigator.resourceContent".
This appears about 20 times per attempt to load Eclipse, all in the first few seconds after initiating the load.
I followed the WSO2 Developer Studio installation guide (http://dist.wso2.org/products/developer-studio/2.1.0/docs/install_guide.html). I was unclear about the prerequisites. It says “Eclipse WTP 3.1.0 or higher”, but that appears to be from old Eclipse versions (Galileo), so I didn’t worry about it. My Eclipse About screen says WTP 1.0. The other prerequisite was for Carbon Server. I am already running latest BPS server (beta), which includes Carbon, so I didn’t worry about it. Just to be sure, I later installed the latest stand-alone “Carbon Server”, but that didn’t help any.
I also tried increasing memory settings in eclipse.ini by 50% (to XXMaxPermSize: 384, -Xmx768m) from the default. No help.
Here is my system:
MS-Windows 7 Enterprise on a 64-bit laptop
Java 1.6
Eclipse IDE for Java EE Developers, Indigo 3.7, 32-bit. Version 1.4.0.20110615-0550
(relevant) Eclipse features:
WTP Version: 1.0.0.v201104180000-797B1CcNBHGC_DRAwXT3B
Subclipse 1.6.x
Aptana Studio 3.0.4 MS Windows x86 “Eclipse plug-in version”. Version: 3.0.4.201108101432-7E37B7HFEHCdSHSV5R_IyJetqA_B
CollabNet Merge Client 2.2.4
Any help would be appreciated.
Hi I faced the same problem especially with nested WSO2 projects / multi module Maven projects. A little change on my Eclipse Project Explorer Settings solved the problem for me.
What I have done:
Open View Customization menu on Eclipse Project Exlporer (the triangle in menu bar of the view)
Clicked "Customize View..."
Unchecked "Hide WSO2 Registry Resource Conflict Items" and "Hide nested projects"
Apply by clicking "OK"
As a result all nested folders will be shown in a flat layout (as usual from m2e-Integration for multimodule Maven projects) but the IDE is now faster and less cpu consuming and doesn't freeze on save anymore.
My Environement looks like:
OS: Windows 7 64bit
Eclipse Indigo Service Release 2 (Build: 20120216-1857)
Eclipse WTP 3.40
Java JDK 1.6.0_31 (32-bit)
WSO2 Developer Studio 2.1.0
M2E-Integration 1.2.0.20120903-1050
M2E-WTP 0.17.0.20121108-1856
Hope it helps
Edit: Sorry I forgot to mention that I had to go through the steps from Harshana first after a fresh installation of WSO2 Developer Studio 2.1.0. My JVM is parameterized with -Xms512m
-Xmx1384m.
Can you try to clean your System Temp folder before starting the Eclipse instance and see whether there is an improvement?
And please use a fresh Eclipse workspace after installing Developer Studio.
We have seen this behavior couple of times in the past and above 2 procedures and increased memory helped to resolve the issue.
Hope this helps!
Thanks and Regards,
Harshana
Developer studio 3.5 beta 2 is released. It improved with lot of bug fixes.
http://devamanthrils.wordpress.com/2014/01/14/developer-studio-3-5-0-beta-2-released/
I have been running eclipse properly. After it loads I get:
"Initializing Java Tooling".
Incompatible magic value 0 in class file org/eclipse/jdt/internal/core/search/BasicSearchEngine
I have been looking, and what I have found is Eclipse hanging initializing java tooling
I have set JAVA_HOME and -vm in eclipse.ini
Still, no success.
Any ideas would be appreciated
=======
Added after I solved the issue
(Stack Overflow won't let me post this as an answer cause I am of ill repute.)
Never mind.
It may be important to have the answer to what I did so that people that have the same issue does not have to go through the hoops I went.
First, I went to the Help/About Eclipse/Installation Details. In the Installation History, with using compare and revert, I started reverting what I had installed (Compare and Revert are pretty cool BTW.) I finally detected which was the latest stable version, and the installation that broke it all
Spring Source at http://dist.springsource.com/release/TOOLS/update/e3.7
Initially I selected some extra components that sounded cool, but the second time around I pretty much went for the required, plus support for AOP, Web Tools, and Flex and WebServices. Other than that I ignored all the rest of the stuff. That worked.
I had selected before (one of the ones that killed it, do not exactly which one), in addition to what I left installed: Spring Mylyn Integration Spring Tool Suite AWS Integration Spring Tool Suite Maven Support Eclipse Weaving Source
I also had the "Mylyn Builds Connector: Jenkins/Hudson integration", which had worked for me in the past. I still suspect that it was one of the Spring components.
I hope this helps
Usually, a restart will solve this issue. As #Carsten mentioned, close all open files and terminate eclipse then re-launch the application. I have encountered this problem many times. The causes of this range from:
Low memory assigned to eclipse. You could increase the memory by editing the eclipse.ini file and change the options -X* JAVA_OPTS
Loading large files (XML is always a culprit in this case).
Attempting to format large XML files
Immediately after installing a new plugin and not restarting eclipse right away
etc
Clean \Workspaces\MyEclipse 8.5 M2.metadata.plugins\org.eclipse.core.resources.projects folder after closing eclipse/myeclipse .That's it.
This is an STS issue however they blame it on an Eclipse bug which has been fixed:
https://issuetracker.springsource.com/browse/STS-696. If you look at the dependencies of the STS plugin you will notice that the Eclipse WTP version is way passed the one that is mentioned in the Eclipse Bug..
Since adding the Blackberry Java classes from their website into eclipse, I've had it where eclipse will randomly close, with no discernible pattern, rhyme, error or reason. Here is the environment/software packages that I am using:
Windows XP SP2
Eclipse v3.5.1
Blackberry Java Plugin v1.1.1.200911111641-15
Blackberry Java SDK 4.5.0.21
I've tried the usual steps of complete uninstall and reinstallation of Eclipse and the accompanying plugins on multiple systems with the same configuration, including one that had a fresh install of Windows XP SP2. Upgrading to Eclipse 3.6 didn't work (the plugin wont' install as it's the wrong version), nor the downgrade to 3.4 for the same reason. I also increased the heap size to 512 (system has two gigs of memory) as some research into Eclipse doing this type of thing with Groovy was resolved that way, but again, no dice. Eclipse works great when the blackberry plugins are not installed, and no entries of errors or issues in the event log are helping to show what the issue with these plug-ins might be.
So if anyone has ran into this issue, and even better, has a solution, I'd love to hear about it. Thanks in advance.
EDIT: An additional to my issue, autoComplete with the Blackberry SDK seems to make this extremely unstable, like almost a guaranteed crash. Is this fixable at all?
For anyone that loads this question up trying to find a solution, I've never found a fix. It seems to be a bug with this version of the IDE. If there is a fix, please post.
Did you try to downgrade Eclipse to 3.4 (Ganymede)? I experienced similar issues when I tried upgrading Eclipse to something greater than 3.4.2.
I think the problem is with the plugin, not the IDE. Eclipse has always been stable for me until I installed the BB plugin. Since then it crashes all the time. Since I've installed the release (non-beta) version of the plugin that was recently released I can't even get my project to build.
This could be a manifestation of this bug in Eclipse. Check your C:\eclipse directory for files like hs_err_pidxxxx.log. The file goes on to explain this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x753ba053, pid=3144, tid=5820
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [USP10.dll+0x1a053]
I've been experiencing this as well. It's completely debilitating. It causes Eclipse to just up and crash out of nowhere (and programming in a language as verbose as Java without Content-Assist is insane).
The bug has been fixed in Eclipse 3.6M7, but unfortunately I can't get the JDE Plug-in to install in the latest release candidate.
This is a known issue with Eclipse 3.5.X and has been fixed for 3.6.0
Bug Ticket link on Eclipse Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503
Looks like we are stuck with this until the next update to the BB Eclipse plugin.