Eclipse Community Forums: Newcomers » Can't run Update Manager: NCDFE for UpdateManagerUI

Home » Newcomers » Newcomers » Can't run Update Manager: NCDFE for UpdateManagerUI

Can't run Update Manager: NCDFE for UpdateManagerUI [message #238297]

Fri, 19 October 2007 11:39

Eclipse User

(I first wrote this in eclipse.platform a few days ago, but I got no
response.)

I'm using SDK 3.3.1. I've been using it for a few weeks, and I managed to
update a bunch of plugins when I first set it up, using the Update
Manager. Today, I thought to check to see if there was a new version of a
particular plugin, and when I tried to bring up the Update Manager,
nothing happened. I checked the console, and saw this:

java.lang.NoClassDefFoundError: org/eclipse/update/ui/UpdateManagerUI
at
org.eclipse.ui.internal.ide.update.ConfigurationManagerActio n$1.run(C
onfigurationManagerAction.java:43)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)

How the heck could I have lost my Update Manager classes?

I searched for this class in my plugins, and I found it in
"org.eclipse.update.ui_3.2.100.v20070615.jar". Why isn't Eclipse finding
this?

Note that I also have a separate installation of RAD 6, and a week or so
ago I updated the RAD Update Manager. I wonder if that somehow did
something to my Eclipse 3.3 Update Manager?

Any advice on fixing this?

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238319 is a reply to message #238297]

Fri, 19 October 2007 14:37

Eclipse User

Originally posted by: wharley.bea.com

"David Karr" <david.karr@wamu.net> wrote in message
news:be95c2da62101bf0d716ae50d333197b$1@www.eclipse.org...
> Note that I also have a separate installation of RAD 6, and a week or so
> ago I updated the RAD Update Manager. I wonder if that somehow did
> something to my Eclipse 3.3 Update Manager?

It sure sounds like it might have. (Everything worked before; you updated
RAD; now things don't work.)

How do you launch Eclipse? Do you specify command line arguments, use an
eclipse.ini, ...? Do you point to an explicit VM, or do you use whatever is
on the path?

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238347 is a reply to message #238319]

Fri, 19 October 2007 17:44

Eclipse User

This is my Eclipse 3.3 launch command:
C:\eclipse33\eclipse\eclipse.exe -vm "c:/Program
Files/Java/jdk1.5.0_11"/bin/java.exe -debug -consolelog -showlocation
-clean

The following is my current eclipse.ini contents:
-------------
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize 192m
-vmargs
-Xms40m
-Xmx1024m
-------------

Although today I changed it from a permsize of 96m and a max mem of 256m
to what is now (because I saw it run out of memory today). This problem
with the updater occurred before today.

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238424 is a reply to message #238347]

Sun, 21 October 2007 19:09

Eclipse User

Originally posted by: wharley.bea.com

"David Karr" <david.karr@wamu.net> wrote in message
news:fe3b2d426db9ba514253b901c48fcca5$1@www.eclipse.org...
> This is my Eclipse 3.3 launch command:
> C:\eclipse33\eclipse\eclipse.exe -vm "c:/Program
> Files/Java/jdk1.5.0_11"/bin/java.exe -debug -consolelog -showlocation -clean
>
> The following is my current eclipse.ini contents:
> -------------
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize 192m

I'm almost certain that is the wrong syntax. You should never have a space
in eclipse.ini. I don't remember offhand whether there's supposed to be a
newline there, a la

--launch.XXMaxPermSize
192m

or whether it's supposed to be a colon or an equals sign or something, a la

--launch.XXMaxPermSize:192m

but it's definitely not a space.

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238467 is a reply to message #238424]

Mon, 22 October 2007 11:09

Eclipse User

Originally posted by: eclipse6.rizzoweb.com

Walter Harley wrote:
> "David Karr" <david.karr@wamu.net> wrote in message
> news:fe3b2d426db9ba514253b901c48fcca5$1@www.eclipse.org...
>> This is my Eclipse 3.3 launch command:
>> C:\eclipse33\eclipse\eclipse.exe -vm "c:/Program
>> Files/Java/jdk1.5.0_11"/bin/java.exe -debug -consolelog -showlocation -clean
>>
>> The following is my current eclipse.ini contents:
>> -------------
>> -showsplash
>> org.eclipse.platform
>> --launcher.XXMaxPermSize 192m
>
>
> I'm almost certain that is the wrong syntax. You should never have a space
> in eclipse.ini. I don't remember offhand whether there's supposed to be a
> newline there, a la
>
> --launch.XXMaxPermSize
> 192m
>
> or whether it's supposed to be a colon or an equals sign or something, a la
>
> --launch.XXMaxPermSize:192m
>
> but it's definitely not a space.

That's right - no spaces allowed. Here's my current (3.3) eclipse.ini

-showsplash
-showlocation
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm C:\Java\JDK\1.6.0\bin\javaw.exe
-vmargs
-Xms40m
-Xmx512m

Eric

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238513 is a reply to message #238424]

Mon, 22 October 2007 18:03

Eclipse User

Fine, but that has nothing to do with my current problem. It's obviously
not making Eclipse being unable to find the update manager classes.
Everything else is working fine. I fixed it (putting the "256m" on the
next line), but it doesn't fix the problem. I still can't get the
UpdateManager to run.

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238550 is a reply to message #238513]

Tue, 23 October 2007 02:28

Eclipse User

Originally posted by: wharley.bea.com

"David Karr" <david.karr@wamu.net> wrote in message
news:e24a33c1140591a095f613deb0bf68f0$1@www.eclipse.org...
> Fine, but that has nothing to do with my current problem. It's obviously
> not making Eclipse being unable to find the update manager classes.
> Everything else is working fine. I fixed it (putting the "256m" on the
> next line), but it doesn't fix the problem. I still can't get the
> UpdateManager to run.

True enough. Still, hunting for unknown problems in the face of known
problems is often difficult.

Other than that issue, I don't see any problem with your launch options nor
any evidence that you're pointing to a suddenly-different VM; nor do I see
any evidence (in this one place) that installing RAD modified your Eclipse
install. That's what I was mainly looking for.

I still think that the RAD theory is a decent one, if only because it's the
only thing you've mentioned that changed in the right timeframe and that
could perhaps be related.

Is it possible for you to try creating a fresh Eclipse install and see if
the problem persists? (I recognize that if you're using the Update Manager,
you probably have a variety of additional plugins installed, so
"reinstalling Eclipse" might not be a simple proposition. But all I can do
is ask.)

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238640 is a reply to message #238550]

Tue, 23 October 2007 11:40

Eclipse User

Despite the fact that the RAD update manager changed in a similar
timeframe, they really are completely separate, and are really completely
different applications.

I don't think it's likely that I could even repeat this problem with a
fresh Eclipse install. It's more likely that Eclipse has somehow gotten
corrupted somehow. It would be nice if I could get some way to patch the
installation to fix this. Otherwise, I guess I'll reinstall it in a few
days.

Before I changed the eclipse.ini file, I had gotten a few OOM errors. The
out of the box configuration is often not very good for actual work. I
wonder if one of those OOM errors did this somehow. When I reinstall
again, I'll make sure my memory configuration is set before I start using
it.

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238655 is a reply to message #238640]

Tue, 23 October 2007 16:40

Eclipse User

Originally posted by: eclipse6.rizzoweb.com

David Karr wrote:
> Despite the fact that the RAD update manager changed in a similar
> timeframe, they really are completely separate, and are really
> completely different applications.
>
> I don't think it's likely that I could even repeat this problem with a
> fresh Eclipse install. It's more likely that Eclipse has somehow gotten
> corrupted somehow. It would be nice if I could get some way to patch
> the installation to fix this. Otherwise, I guess I'll reinstall it in a
> few days.

You could try just extracting the Update Manager-related bundles into
your existing Eclipse installation. Make sure the versions are exactly
the same (don't extract 3.3.1 onto a 3.3 installation).

>
> Before I changed the eclipse.ini file, I had gotten a few OOM errors.
> The out of the box configuration is often not very good for actual
> work.

Here's the eclipse.ini that is shipped with the "JEE Developers" package
for 3.3.1:

-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m

I think 512MB of heap should be enough for most users. Did you have to
bump it up?

Eric

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238687 is a reply to message #238655]

Wed, 24 October 2007 09:43

Eclipse User

I could use more clarification on the process you describe. By "bundles",
you mean jar files in the plugins directory? You're saying to extract the
contents directly into that directory?

Yes, I had to bump up the xmx.

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238711 is a reply to message #238687]

Wed, 24 October 2007 12:12

Eclipse User

Originally posted by: eclipse6.rizzoweb.com

David Karr wrote:
> I could use more clarification on the process you describe. By
> "bundles", you mean jar files in the plugins directory? You're saying
> to extract the contents directly into that directory?

I'm suggesting to re-download the Eclipse ZIP (or open it if you still
have it locally) and extract the Update Manager plugins (JARs, most
likely) into your existing Eclipse installation (in the /plugins directory).
Doing this is not generally recommended, and there is potential that you
could mess up your installation even more; but if your only alternative
is to completely re-install, this might be worth trying first since it
is a much less labor-intensive option.

Hope this helps,
Eric

Re: Can't run Update Manager: NCDFE for UpdateManagerUI [message #238738 is a reply to message #238711]

Wed, 24 October 2007 15:59

Eclipse User

Originally posted by: wegener.cboenospam.com

You mentioned RAD 6 in some of your earlier posts. Is it possible that you
opened up your Eclipse workspace with the RAD 6 product? If so, it is
possible that this made a change to the workspace that prevents the Eclipse
update manager from working.

As another thought, have you tried to run the update manager from a
different workspace? Start Eclipse and point to a new workspace location.
You shouldn't even need to create/import any projects. Open up the Update
Manager to see if you can get past the problem.

"Eric Rizzo" <eclipse6@rizzoweb.com> wrote in message
news:ffnqsh$qfs$1@build.eclipse.org...
> David Karr wrote:
> > I could use more clarification on the process you describe. By
> > "bundles", you mean jar files in the plugins directory? You're saying
> > to extract the contents directly into that directory?
>
> I'm suggesting to re-download the Eclipse ZIP (or open it if you still
> have it locally) and extract the Update Manager plugins (JARs, most
> likely) into your existing Eclipse installation (in the /plugins
directory).
> Doing this is not generally recommended, and there is potential that you
> could mess up your installation even more; but if your only alternative
> is to completely re-install, this might be worth trying first since it
> is a much less labor-intensive option.
>
> Hope this helps,
> Eric

Previous Topic:	eclipse crashes at startup
Next Topic:	[cdt-dev] Propoerty info on CDT4.0

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Nov 10 07:17:14 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter