Eclipse Error Initializing Spring Tooling

the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor. sts an internal error occurred during initializing java tooling java lang nullpointerexception Announcement Announcement Module Collapse No announcement yet. Error: 'Initializing Spring Tooling' initializing java tooling has encountered problem nullpointerexception has encountered a problem Page Title Module Move Remove Collapse X Conversation Detail Module Collapse Posts Latest eclipse initializing java tooling hang Activity Search Forums Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only

Initializing Java Tooling Has Encountered A Problem Sts

Filtered by: Clear All new posts micron Junior Member Join Date: Jan 2012 Posts: 2 #1 Error: 'Initializing Spring Tooling' has encountered a problem Feb 2nd, 2012, 10:32 AM Often, when I launch the SpringSource Tool Suite, I get the following error message: 'Initializing Spring Tooling' has encountered a problem. An internal error occurred during: "Initializing an internal error occurred during initializing spring uaa org eclipse jdt core javamodelexception Spring Tooling". Does anyone know why I'm getting this error and what it actually means? Could this be a bug in STS? Or, is there some configuration change that I can make to get rid of this? Here's some information about the software that I'm running: STS Version: 2.8.1.RELEASE STS Build Id: 201111221000 Java Version: Oracle JDK 1.7.0_02 (32-bit) OS: PCLinuxOS 2011.9 (32-bit) Linux kernel: 2.6.38.8 - Here's the error message and stack trace that I see when I launch STS from the console. (Note that the exception indicates that there is a problem opening a zip file because of too many open files. I have verified that the org.eclipse.wst.xsl.jaxp.debug_1.0.200.v2011030819 22.jar file exists and that it is a valid zip file.): An internal error occurred during: "Initializing Spring Tooling". org/springframework/beans/factory/xml/DelegatingEntityResolver !ENTRY org.eclipse.wst.xsl.jaxp.debug 4 0 2012-02-02 10:08:59.109 !MESSAGE FrameworkEvent ERROR !STACK 0 java.io.IOException: Exception in opening zip file: /opt/springsource/sts-2.8.1.RELEASE/plugins/org.eclipse.wst.xsl.jaxp.debug_1.0.200.v2011030819 22.jar at org.eclipse.osgi.framework.util.SecureAction.getZi pFile(SecureAction.java:291) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleF ile.basicOpen(ZipBundleFile.java:87) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleF ile.getZipFile(ZipBundleFile.java:100) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleF ile.checkedOpen(ZipBundleFile.java:73) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleF ile.getEntry(ZipBundleFile.java:245

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn eclipse neon download more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags

Eclipse Download

Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Eclipse internal error while initializing Java tooling up vote 24 down vote favorite 6 I am getting errors from Eclipse Indigo running on Windows 7 http://forum.spring.io/forum/spring-projects/springsource-tool-suite/113219-error-initializing-spring-tooling-has-encountered-a-problem Ultimate. For each of the following items: Android SDK content loader Building workspace Initializing Java Tooling Loading data for Android 2.3.3 Loading data for Android 4.03 this error is thrown: An internal error occurred during: "Initializing Java Tooling".java.lang.NullPointerException What should I do? eclipse share|improve this question edited Jun 27 '12 at 18:20 Keith Pinson 3,61242865 asked Jun 5 '12 at 6:41 al23dev 3021415 1 Your workspace might be corrupted. Try to create a blank new http://stackoverflow.com/questions/10892790/eclipse-internal-error-while-initializing-java-tooling workspace then import your existing projects into it. –papaiatis Jun 5 '12 at 6:47 add a comment| 6 Answers 6 active oldest votes up vote 15 down vote accepted Delete your existing workspace and then recreate the workspace and add your projects. share|improve this answer edited Apr 4 at 10:02 NiallMitch14 451112 answered Jun 5 '12 at 6:55 Abhinai 6341817 8 It's better, that is, it's easier and probably safer, to not use this method first. It's better to try closing and reopening projects as suggested in the other answer below. –L S Mar 6 '13 at 15:12 I tried closing and re-opening the project which took care of this problem. BUT I had other side-effects (CTRL+SHIFT+R did not get all files in the project). So finally deleted and re-created the project –Toothless Seer Mar 9 at 21:29 add a comment| up vote 53 down vote Close all open projects and exit Eclipse. Now you can open Eclipse without getting the error. Start opening your projects one by one to find which one causes the problem. This is most likely because you deleted a Device profile inside the AVD manager. Or you can start working on a new workspace, ( ie change your workspace ) , then try to import your project from the old workspace share|improve this answer answered Aug

Board ExportXMLWordPrintable Details https://tedvinke.wordpress.com/2010/06/21/eclipse-initializing-java-tooling-hangs/ Type: Bug Status: Resolved Priority: Minor Resolution: Fixed Affects Version/s: 3.7.0.RELEASE Fix Version/s: 3.7.1.RELEASE Component/s: None Labels: None Description I get this initializing java error popping out regularly with STS 3.7.0 (latest release build). It happens when I open my development workspace. eclipse.buildId=3.7.0.201506290652-RELEASE-e45 java.version=1.7.0_80 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA initializing java tooling Framework arguments: -product org.springsource.sts.ide Command-line arguments: -data file:/home/kdvolder/workspaces-sts/spring-ide/ -os linux -ws gtk -arch x86_64 -product org.springsource.sts.ide -clean org.eclipse.core.jobs Error Mon Jun 29 15:10:43 PDT 2015 An internal error occurred during: "Initializing Spring Tooling". java.lang.IllegalArgumentException: Attempted to beginRule: P/org.springframework.ide.eclipse.boot, does not match outer scope rule: Beans Model Initialization at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134) at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333) at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85) at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:307) at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:120) at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2189) at org.eclipse.core.internal.resources.Project.touch(Project.java:1304) at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:115) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:794) at org.eclipse.jdt.internal.core.JavaModelManager$10.run(JavaModelManager.java:2798) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241) at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2814) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1895) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:3298) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaPro

on Eclipse - startup hangs on various operations: Initializing Java Tooling Repository registry initialization STS/Eclipse does not seem to respond to anything - the UI freezes and that's it! I've had this on several occassions with no apparent cause on my part. Usually it has something to do with fiddling with (adding libraries to) the classpath and/or cleaning the project. Some users report Eclipse hangs at "Initializing Java Tooling" at 30% for 20-30 secs after which everything continues normally, but I don't have that much luck🙂 I've tried the most suggested actions in forum posts, such a starting STS/Eclipse with the -clean parameter which most of the times doesn't work in my configuration. If you inspect the .log files under the workspace's .metadata folder you might find something of interest, but quite often STS/Eclipse just hangs without anything written to the log in my case. The largeness of your project or the amount of projects quite often seem to be one of the causes. Here are a few workarounds and/or solutions that might prove succesful: Start a new workspace and import the project back in - which is just plain tedious and annoying although it quite often works Close all projects before you exit Eclipse after which Eclipse normally restarts. Some users have reported it does seem related to a configured Tomcat server instance. If you have this configured a possible workaround instead of reimporting your projects in a new workspace, is to rename the .project file in workspace/Servers, restarting, removing and adding the Server configuration again. The solution I found - which seems to work most of the times - is to remove or rename the .projects folder in .metadata/.plugins/org.eclipse.core.resources in the workspace folder. This doesn't seem to affect any project and the .project folder will be recreated when Eclipse restarts. Hopefully someone with this problem saves some time because of this. Ofcourse the real problem needs to be addressed by the guys and girls over at Eclipse. Share this:TweetMoreEmailPrint Ted Vinke I'm a software developer and Java enthusiast. I like clean and modular code, enjoy Agile projects and have a passion for trying our new things. I try to learn and teach every day, and occasionally I'm even able to blog about it :-) I currently work for First8, a Java software development company base