Background
I have been trying for the last week to rebase a clearcase view for my project, but every time I try I get a weird null exception depicted in the two windows below:
I do not know why this is occurring and need help determining how to even begin fixing this issue.
So far here is what I have tried:
Restarting the client
Restarting my computer
Refreshing the view and updating.
Updating my eclipse environment.
I have also seen a fix on the IBM website for a similar issue, but my version of Clearteam explorer is well beyond the version it prescribes for a fix:
When you are trying to login with the IBM Rational ClearTeam
Explorer (CTE) version 8.0.1.11 and later with the Eclipse
plugin, you may receive the following error: CRMAP7009: Command
"Login" failed: Error: "java.lang.IllegalStateException: null"
This behavior does not occur with CTE 8.0.1.10 with the Eclipse
plugin or with the standalone CTE 8.0.1.11 client.
It only occurs using the Sun JRE 6, not when using the IBM JRE
6.
My clearteam explorer version is 9.0.2:
Question
What are other possible actions I can take to fix the null pointer issue mentioned above?
OK, you're going to hate this, but the only thing I can do is ask questions and point you to IBM/HCL support.
Is this a web-based view? A snapshot view? A Dynamic view?
Does a new view work?
Are there any errors in the CTE workspace log? (%USERPROFILE%.Rational\CTE8\workspace.log)
Is this the CTE plugin installed into Eclipse? Or the CTE "full" client? And does it matter?
Have you tried this using the command line interface (cleartool/rcleartool as appropriate)
Does running in debug mode tell us anything additional? (See https://www.ibm.com/support/pages/how-enable-trace-ccrc-client-and-server) Note that on windows, CTE/eclipse will spawn a separate console window to print some eclipse diagnostic output that may or may not be important. You'll want to capture that before exiting the session.
If this is a web-based view, has anyone checked the WAN server logs?
CRMAP7009 is a "catch all" message for CTE, but since that is an exception message, it should be expanded upon SOMEWHERE. Half the battle is finding the rest of the message.
In those case, I always try and fall back to command line, using in your case cleartool rebase.
See "Rebase a stream on linux using cleartool" (the same idea applies on Windows), and "How to rebase in ClearCase on latest baselines?".
That way, I can see if the issue is with ClearCase itself or with the Eclipse ClearCase plugin.
Related
Problem while receiving an update from Eclipse to svn. The error message is '0x00000: Open Project' operation completed with error: 0x000000: Unable connection to 'blah-' project. Please check that SVN meta-information exists and it is supporting the form ...
Except that the operating system has been updated from Windows 7 to Windows 10, nothing has changed, but it is annoying and cumbersome to see such errors every time we update. Of course, there are solutions such as cleaning up or re-connecting, but I want to prevent this problem from occurring fundamentally.
Can you tell me what to look at?
Thank you for reading it.
I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log
I have been using the TFS plugin for eclipse with my companies TFS server for several months. Last week, my laptop crashed while eclipse was open and a connection to the TFS was present. Now, every time I launch eclipse, I get an error stating a connection could not be made to the server, throwing a NullPointerException.
To try to fix this, I cleaned eclipse from my system and removed the installed plugin and then reinstalled eclipse and the TFS plugin. Now, I am no longer getting this connection error on launch. I added the original TFS to the list of servers in eclipse and it can see all of the projects (see http://i.imgur.com/SbgyuRx.png).
However, trying to use any of the projects leads to a screen with an error message saying Error querying workspaces: null. The error log shows the plugin in question as com.microsot.tfs.client.common, with the stack trace saying An exception stack trace is not available.
I am using the same exact plugin installation that I originally used. I have no idea why I'm getting these errors.
The error logs may be helpful. You can view them by going to Help > Team Explorer Everywhere Support, then clicking on the Logs tab.
Ultimately, though, this is probably some corrupt configuration files. TEE performs some various background tasks and I suspect one of those was interrupted in the middle of some file I/O when your computer crashed. Deleting the cache directory may be helpful:
~/.microsoft/Team Foundation
When you restart Eclipse, you should get a dialog box that indicates that your TFS server information cannot be located, but when you reconnect to that TFS server, your projects should return to being TFS managed.
We use Eclipse (Indigo, with STS). Certain of our projects take inordinately long to build. Often the progress indicator sticks on, say, 87%, for 30 seconds.
I'm trying to find out what Eclipse is spending it's time on during the build cycle. I hope to be able to optimize the build or disable components that are causing it to be so slow. I'd like to see a log file saying ("compiling java code", "processing resources", etc).
I've poked around the log files in the .metadata directory. I've looked on the Eclipse site for tips. I've tried using "-debug" when starting Eclipse. I still can't find the information I'm looking for.
Is there any way to get Eclipse to spit out a log of what activities it is spending its time on when it builds a project?
What kind of projects are these? Java? Dynamic Web? Two things to look at for hints about what's going on are in the project Properties dialog; look at the Builders section and the Validation section. Try disabling the validations to see if that makes a difference in your build times.
To get some insight into what's happening at the times when the build seems to hang, try setting the -debug and -consoleLog options, as described here.
Disable your virus scanner software for your workspace and project directories. I increased the speed of my build in that way.
You can go to edit Windows->preference->general->workspace->build order to edit the default that exist according to your project need.
And check the maximum number of iteration when building with cycle.
I hope it works.
Since eclipse is a Java application, the usual debugging tools are at your disposal. In particular, you might try connecting to eclipse with JConsole and inspect the thread dump taken when the build "hangs", or run eclipse within a profiler.
You might find out things like a validator trying to download an xml schema, and waiting for the timeout since eclipse is not configured to use the corpoate proxy server - something which is very hard to find out by other means ;-)
Look into Apache Ant build scripts. Eclipse has support to auto generate them as a starting point instead of coding the whole thing by hand. The shop I worked in used tuned ANT scripts to optimize and control build order. We then piped output to log files using shell scripts.
You can try and replace with this aapt . My build for a particular project went from 3 minutes to 41 seconds....
This is an old post but thought of sharing my solution. I was using eclipse Luna and I noted that when you keep on working on a GIT branch without checking into git over the time the build becomes very slow. In my case I just deleted the folder .git and the file .gitignore and the build was very fast. Please note that this will disconnect eclipse from git, therefore use this aproach only if you know how to connect back to git branch using git commands.
I recently started using git with the egit plugin in eclipse, and I thought I had everything working. I cloned a remote repository to my machine, then made a change to a file, and went to commit the change via selecting the file in the project, and going to Team > Commit.... As soon as I do, I get the following error:
Unhandled event loop exception
org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
at org.eclipse.swt.SWT.error(SWT.java:4308)
at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:1826)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:687)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:96)
...
(output abbreviated)
I am fully willing to accept that this is a bug of sorts (even though I thought this was working earlier today), but I am hoping someone may have encountered this problem once before.
Any insights? Even if it is only who I should file the bug against? I can provide any additional details. I should also point out that things work fine if I commit through the git repository view.
The problem is that the particular git workflow is creating a SWT Browser component that is having trouble loading on your particular OS + Windowing system + mozilla library version combination. There is a bit of black magic that has to go on to make sure you get the right configuration to allow the SWT browser to work with your embedded mozilla renderer. You can get detailed information on the SWT FAQ page here.
Also there are many other posts on this site that talk about how to resolve the dreaded "NO MORE HANDLES" problem here.