I use Eclipse Java EE IDE Kepler for Web Developers with pydev.
The first instance of Eclipse hangs on startup while loading a workspace.
If i start eclipse again, a coexist second instance of eclipse works fine.
I used different workspaces, the problem is independent from the used workspace.
Thanks
I think that the best approach would be identifying the stack you have when it hangs and then reporting a bug (probably in Eclipse: https://bugs.eclipse.org/ but it may be in PyDev: https://sw-brainwy.rhcloud.com/tracker/PyDev depending on the trace).
On http://pydev.org/faq.html#PyDevFAQ-HowdoIReportaBUG%3F there's info on how to get information on a halting condition.
Related
I am using eclipse mars 4.5. Problem is, it always busy with scanning class path that actually makes eclipse too slow to work on. I am working on the multimodule OSGI projects, so there are around 30 projects in the workspace and eclipse every time starts scanning classpath for all projects.
can anybody help to optimize the eclipse and stopping auto class path scan for each project.
On my machine the vaadin designer scanned each projects of my workspace (in my case about 100 bundles), and this took very long (eclipse Mars.2 and Neon)
Hint: open visualvm - connect to eclipse pid; create a thread dump and analyze the worker threads of eclipse.
I have the same issue and the only things I do are:
Maven plugin:
If you use the maven plugin, on each project, choose the Maven option Disable Workspace Resolution the other project will not refers anymore those in the workspace.
Apparently this is a known bug and you can find some more solution like rebuilding the maven indexes here.
Maven in command line:
Another option I choose is to use the maven on command line (It's not perfect but in the environment I work in it is the best solution) and use the option "Offline" in the maven preferences. This is due to proxy which is not working from Eclipse but work from command line (my setup).
Personally I use both option but this is due to a very strict proxy which is not friendly; I think this is a good setup for OSGI as trying to resolve all dependencies could be very long.
Another point: try to see if you have circular dependencies, it can happens very quickly in OSGI environment and I guess that can also make the compiler to be mad.
I have an Eclipse Kepler IDE where ADT Plugins, CDT plugis, Android NDK and Java is installed. It is sort of my lifeline IDE at work. Without this my whole work will come to a standstill. I have this IDE installed on a Vbox Ubuntu machine and have been using it for the past one year(ever since the glorious JUNO version days!). About 2 months ago, my IDE was veyr slow so I upgraded it from Juno to Kepler expecting better performance. I must admit it was not any at all. Also, on my VBox, the IDE froze a couple of times whenever I plugged in a USB in my Virtual Box. I assumed it must be some bug with the USB and just left it. Today, all of a sudden (this is the 5th time I have rebooted my virtual image) whenever I tried to copy a piece of code in my IDE, the whole IDE freezes. Only a kill -9 pid number command came to rescue after that. What should I do? Please suggest!!
thanks a lot.
First, you should configure the Java VM to create a thread dump when Eclipse hangs. Eclipse doesn't just hang for the fun of it; something is wrong but since there is a deadlock, Eclipse can't tell you anymore. Read up on debugging deadlocks.
The next step when Eclipse is acting up is always to clean the .metadata folder since a crash sometimes corrupts important files in there. See this blog post.
If that also doesn't help, you can try to reinstall Eclipse. Install the plugins one after the other, noting down what you do until you find the one which breaks the others.
I am working on an application in Eclipse Helios and since yesterday every change in the code is not being applied when running the application. I have no idea what is going on. Is my Eclipse corrupted? Have some of you faced such situation? Many thaks.
You have probably disabled the automatic build, so Eclipse never compiles your changes. Check the main menu Project -> Build automatically.
This is my first attempt at creating an Eclipse plug-in. I've created one, along with a feature and update site. I set the target platform as my local Eclipse installation. When I run/debug the plugin from within the development environment everything works fine.
Now, my colleague installed the plug-in from the update site that I hosted. When he starts using any of the functionality exposed by my plugin he gets runtime exceptions.
He sees null pointer exceptions which didn't occur when I ran my plug-in project from my development environment.
I have a wizard that's part of my plug-in. When he close it he gets a "Unhandled event loop exception", and the wizard doesn't close. I didn't have this issue when I was running/debugging my plugin in my development environment.
Now I'm confused as to why the same plug-in is behaving differently in the production environment, as against the dev environment and when I was debugging it from my IDE. The target platform in both cases is the same Eclipse version. What could be the reasons?
And how do I debug the plug-in in a production environment? Is there a remote debugging capability for debugging the plug-ins on the production environment?
Any suggestions would be really useful!
To remote debug your plug-in, first add debug arguments to your target Eclipse .ini file
-vmargs
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
before launching it.
Then open another Eclipse instance with a workspace containing your plug-in project.
Open Run > Debug Configurations..., select Remote Java Application and create a new configuration.
As Project, browse and select your plug-in project.
Also fill in your connection properties (host of target Eclipse and port 1044).
Launching the newly created debug configuration allows you to debug your plug-in the same way you debug locally.
Now I'm confused as to why the same plug-in is behaving differently in
the production environment, as against the dev environment and when I
was debugging it from my IDE. The target platform in both cases is the
same eclipse version. What could be the reasons?
This is a classic: Eclipse plugins and RCP applications do indeed behave differently between PDT (the Eclipse IDE) and the exported product.
In your case, a NullPointerException thrown from the exported version but not from Eclipse is 9 times out of 10 an image or other resource files (properties, etc.) that is loaded by your code but is not listed in the build.properties of your plugin.
Anyway, you'll need to check the logs to retrieve the stacktrace and hunt down its cause. Such logs could be found in your friend's workspace under le .metadata/.log file
From your development workspace as it stands now, use the "Debug As -> Eclipse Application" menu item to startup a test workspace. When it starts up, you'll have two workspaces running: the original development workspace and the new test workspace. You can set breakpoints in your plugin code in the development workspace and run your plugin in the test workspace.
When your plugin execution in the test workspace gets to one of your breakpoints, execution will pause and you can use the Debug view in your development workspace to look at variables, set more breakpoints or anything else you want to do to debuf your plugin.
See the Apache Wiki for Developing with Eclipse.
Under Windows 10 with Tomcat running as a windows service I started:
tomcat8.5\bin\Tomcat8w.exe
& added in the Java tab as the first entry in Java Options to enable remote debugging:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
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..