Home » Eclipse Projects » Equinox » RCP App Fails on startup: IllegalStateException
| | |
| Re: RCP App Fails on startup: IllegalStateException [message #50894 is a reply to message #50865] |
Thu, 20 October 2005 01:06   |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
A couple things.
- Bugzilla is more effective for this kind of issue
- The application service is registered by the runtime plugin. I suspect
that you are not installing/starting the runtime. It should be listed on
the osgi.bundles list in the config.ini or on the command as a -D vm arg.
- when you export the features, what are you doing for a launcher,
startup.jar, config.ini etc. You should consider defining a PRODUCT and
exporting the product and then packaging that up.
Jeff
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:dj5lut$g94$1@news.eclipse.org...
> Can anyone shed any light on this?
>
> thx
>
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dj0td9$fb2$1@news.eclipse.org...
> > FYI, I use the feature export functionality of eclipse so that all
> plugins,
> > both eclipse and ours, are moved into a staging area for the application
> > packaging step whereby I run a script which builds a self-extracting
> > executable. So I'm using the same plugins that are used in my
functional
> > development environment. I've been hoping that something is "shoddy"
> > somewhere but I still don't understand what the source of this error is.
> > I've stepped through the code in the dev environment but I'm not
> connecting
> > the dots as to what circumstances will cause this to fail
> > (ParameterizedRunnable returns null):
> >
> > EclipseStarter.java
> >
> > public static Object run(Object argument) throws Exception {
> > if (Profile.PROFILE && Profile.STARTUP)
> > Profile.logEnter("EclipseStarter.run(Object)()", null); //$NON-NLS-1$
> > if (!running)
> > throw new
> > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > // if we are just initializing, do not run the application just
return.
> > if (initialize)
> > return new Integer(0);
> > initializeApplicationTracker();
> > if (Profile.PROFILE && Profile.STARTUP)
> > Profile.logTime("EclipseStarter.run(Object)()", "applicaton tracker
> > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > LINE 364>>>>ParameterizedRunnable application =
(ParameterizedRunnable)
> > applicationTracker.getService();
> >
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dioesh$ceb$1@news.eclipse.org...
> > > We just migrated from 3.1 M6 to 3.1.1 and our RCP application will not
> run
> > > as a standalone application (but works fine as a launch configuration
> from
> > > the IDE).
> > > I'm guessing this is something obvious but I can't seem to find it.
> This
> > > occurs
> > > whether I try to point to an existing workspace or not.
> > >
> > >
> > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > !MESSAGE Application error
> > > !STACK 1
> > > java.lang.IllegalStateException: Unable to acquire application
service.
> > > at
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > at
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51085 is a reply to message #50894] |
Thu, 20 October 2005 15:20 |
 paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Thanks Jeff,
I usually assume user error or configuration rather than a bug. For this
particular issue, I assumed something configuration related as this worked
fine for our 3.0x and 3.1M builds. This problem arose with the migration
from 3.1M6 to 3.1.1.
We do have a product and application defined and our
INSTALL/configuration/config.ini contains the following entries (we have
never specified the osgi.bundles parameter):
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
on
eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
The INSTALL/features directory contains two features both of which have a
feature.xml:
com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
com.eyeris.eyeprofit.ui.plugins_1.0.0
The INSTALL/plugins directory now contains all IDE and proprietary plugins
(a result of trying to debug the problem)
As for the launcher, the INSTALL directory contains what we've used
previously:
eclipse.exe
startup.jar
..eclipseproduct
And our startup parameters are also how they've been previously:
"C:\Program Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
So it sounds like we need to update the config.ini with at least one bundle,
which one(s)?
osgi.bundles =??
Paul
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:dj6qii$vm7$1@news.eclipse.org...
> A couple things.
>
> - Bugzilla is more effective for this kind of issue
> - The application service is registered by the runtime plugin. I suspect
> that you are not installing/starting the runtime. It should be listed on
> the osgi.bundles list in the config.ini or on the command as a -D vm arg.
> - when you export the features, what are you doing for a launcher,
> startup.jar, config.ini etc. You should consider defining a PRODUCT and
> exporting the product and then packaging that up.
>
> Jeff
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dj5lut$g94$1@news.eclipse.org...
> > Can anyone shed any light on this?
> >
> > thx
> >
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dj0td9$fb2$1@news.eclipse.org...
> > > FYI, I use the feature export functionality of eclipse so that all
> > plugins,
> > > both eclipse and ours, are moved into a staging area for the
application
> > > packaging step whereby I run a script which builds a self-extracting
> > > executable. So I'm using the same plugins that are used in my
> functional
> > > development environment. I've been hoping that something is "shoddy"
> > > somewhere but I still don't understand what the source of this error
is.
> > > I've stepped through the code in the dev environment but I'm not
> > connecting
> > > the dots as to what circumstances will cause this to fail
> > > (ParameterizedRunnable returns null):
> > >
> > > EclipseStarter.java
> > >
> > > public static Object run(Object argument) throws Exception {
> > > if (Profile.PROFILE && Profile.STARTUP)
> > > Profile.logEnter("EclipseStarter.run(Object)()", null);
//$NON-NLS-1$
> > > if (!running)
> > > throw new
> > > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > // if we are just initializing, do not run the application just
> return.
> > > if (initialize)
> > > return new Integer(0);
> > > initializeApplicationTracker();
> > > if (Profile.PROFILE && Profile.STARTUP)
> > > Profile.logTime("EclipseStarter.run(Object)()", "applicaton tracker
> > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > LINE 364>>>>ParameterizedRunnable application =
> (ParameterizedRunnable)
> > > applicationTracker.getService();
> > >
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dioesh$ceb$1@news.eclipse.org...
> > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP application will
not
> > run
> > > > as a standalone application (but works fine as a launch
configuration
> > from
> > > > the IDE).
> > > > I'm guessing this is something obvious but I can't seem to find it.
> > This
> > > > occurs
> > > > whether I try to point to an existing workspace or not.
> > > >
> > > >
> > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > !MESSAGE Application error
> > > > !STACK 1
> > > > java.lang.IllegalStateException: Unable to acquire application
> service.
> > > > at
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > at
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51113 is a reply to message #51085] |
Thu, 20 October 2005 16:13 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
I tried add the following to config.ini but still got the same error:
osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
org.eclipse.core.runtime
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:dj8cj9$2rr$1@news.eclipse.org...
> Thanks Jeff,
> I usually assume user error or configuration rather than a bug. For this
> particular issue, I assumed something configuration related as this worked
> fine for our 3.0x and 3.1M builds. This problem arose with the migration
> from 3.1M6 to 3.1.1.
>
> We do have a product and application defined and our
> INSTALL/configuration/config.ini contains the following entries (we have
> never specified the osgi.bundles parameter):
>
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> on
> eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
>
> The INSTALL/features directory contains two features both of which have a
> feature.xml:
>
> com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> com.eyeris.eyeprofit.ui.plugins_1.0.0
>
> The INSTALL/plugins directory now contains all IDE and proprietary plugins
> (a result of trying to debug the problem)
>
> As for the launcher, the INSTALL directory contains what we've used
> previously:
>
> eclipse.exe
> startup.jar
> .eclipseproduct
>
> And our startup parameters are also how they've been previously:
>
> "C:\Program
Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
>
> So it sounds like we need to update the config.ini with at least one
bundle,
> which one(s)?
>
> osgi.bundles =??
>
> Paul
>
>
>
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> news:dj6qii$vm7$1@news.eclipse.org...
> > A couple things.
> >
> > - Bugzilla is more effective for this kind of issue
> > - The application service is registered by the runtime plugin. I
suspect
> > that you are not installing/starting the runtime. It should be listed
on
> > the osgi.bundles list in the config.ini or on the command as a -D vm
arg.
> > - when you export the features, what are you doing for a launcher,
> > startup.jar, config.ini etc. You should consider defining a PRODUCT and
> > exporting the product and then packaging that up.
> >
> > Jeff
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dj5lut$g94$1@news.eclipse.org...
> > > Can anyone shed any light on this?
> > >
> > > thx
> > >
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > FYI, I use the feature export functionality of eclipse so that all
> > > plugins,
> > > > both eclipse and ours, are moved into a staging area for the
> application
> > > > packaging step whereby I run a script which builds a self-extracting
> > > > executable. So I'm using the same plugins that are used in my
> > functional
> > > > development environment. I've been hoping that something is
"shoddy"
> > > > somewhere but I still don't understand what the source of this error
> is.
> > > > I've stepped through the code in the dev environment but I'm not
> > > connecting
> > > > the dots as to what circumstances will cause this to fail
> > > > (ParameterizedRunnable returns null):
> > > >
> > > > EclipseStarter.java
> > > >
> > > > public static Object run(Object argument) throws Exception {
> > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> //$NON-NLS-1$
> > > > if (!running)
> > > > throw new
> > > >
IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > // if we are just initializing, do not run the application just
> > return.
> > > > if (initialize)
> > > > return new Integer(0);
> > > > initializeApplicationTracker();
> > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > Profile.logTime("EclipseStarter.run(Object)()", "applicaton
tracker
> > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > LINE 364>>>>ParameterizedRunnable application =
> > (ParameterizedRunnable)
> > > > applicationTracker.getService();
> > > >
> > > >
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP application will
> not
> > > run
> > > > > as a standalone application (but works fine as a launch
> configuration
> > > from
> > > > > the IDE).
> > > > > I'm guessing this is something obvious but I can't seem to find
it.
> > > This
> > > > > occurs
> > > > > whether I try to point to an existing workspace or not.
> > > > >
> > > > >
> > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > !MESSAGE Application error
> > > > > !STACK 1
> > > > > java.lang.IllegalStateException: Unable to acquire application
> > service.
> > > > > at
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > at
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
> > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51198 is a reply to message #51113] |
Thu, 20 October 2005 23:07 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
This worked however...
osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:dj8foc$7j1$1@news.eclipse.org...
> I tried add the following to config.ini but still got the same error:
>
> osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> org.eclipse.core.runtime
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dj8cj9$2rr$1@news.eclipse.org...
> > Thanks Jeff,
> > I usually assume user error or configuration rather than a bug. For
this
> > particular issue, I assumed something configuration related as this
worked
> > fine for our 3.0x and 3.1M builds. This problem arose with the
migration
> > from 3.1M6 to 3.1.1.
> >
> > We do have a product and application defined and our
> > INSTALL/configuration/config.ini contains the following entries (we have
> > never specified the osgi.bundles parameter):
> >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > on
> > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> >
> > The INSTALL/features directory contains two features both of which have
a
> > feature.xml:
> >
> > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > com.eyeris.eyeprofit.ui.plugins_1.0.0
> >
> > The INSTALL/plugins directory now contains all IDE and proprietary
plugins
> > (a result of trying to debug the problem)
> >
> > As for the launcher, the INSTALL directory contains what we've used
> > previously:
> >
> > eclipse.exe
> > startup.jar
> > .eclipseproduct
> >
> > And our startup parameters are also how they've been previously:
> >
> > "C:\Program
> Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> >
> > So it sounds like we need to update the config.ini with at least one
> bundle,
> > which one(s)?
> >
> > osgi.bundles =??
> >
> > Paul
> >
> >
> >
> > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > news:dj6qii$vm7$1@news.eclipse.org...
> > > A couple things.
> > >
> > > - Bugzilla is more effective for this kind of issue
> > > - The application service is registered by the runtime plugin. I
> suspect
> > > that you are not installing/starting the runtime. It should be listed
> on
> > > the osgi.bundles list in the config.ini or on the command as a -D vm
> arg.
> > > - when you export the features, what are you doing for a launcher,
> > > startup.jar, config.ini etc. You should consider defining a PRODUCT
and
> > > exporting the product and then packaging that up.
> > >
> > > Jeff
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dj5lut$g94$1@news.eclipse.org...
> > > > Can anyone shed any light on this?
> > > >
> > > > thx
> > > >
> > > >
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > FYI, I use the feature export functionality of eclipse so that all
> > > > plugins,
> > > > > both eclipse and ours, are moved into a staging area for the
> > application
> > > > > packaging step whereby I run a script which builds a
self-extracting
> > > > > executable. So I'm using the same plugins that are used in my
> > > functional
> > > > > development environment. I've been hoping that something is
> "shoddy"
> > > > > somewhere but I still don't understand what the source of this
error
> > is.
> > > > > I've stepped through the code in the dev environment but I'm not
> > > > connecting
> > > > > the dots as to what circumstances will cause this to fail
> > > > > (ParameterizedRunnable returns null):
> > > > >
> > > > > EclipseStarter.java
> > > > >
> > > > > public static Object run(Object argument) throws Exception {
> > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> > //$NON-NLS-1$
> > > > > if (!running)
> > > > > throw new
> > > > >
> IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > // if we are just initializing, do not run the application just
> > > return.
> > > > > if (initialize)
> > > > > return new Integer(0);
> > > > > initializeApplicationTracker();
> > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > Profile.logTime("EclipseStarter.run(Object)()", "applicaton
> tracker
> > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > LINE 364>>>>ParameterizedRunnable application =
> > > (ParameterizedRunnable)
> > > > > applicationTracker.getService();
> > > > >
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP application
will
> > not
> > > > run
> > > > > > as a standalone application (but works fine as a launch
> > configuration
> > > > from
> > > > > > the IDE).
> > > > > > I'm guessing this is something obvious but I can't seem to find
> it.
> > > > This
> > > > > > occurs
> > > > > > whether I try to point to an existing workspace or not.
> > > > > >
> > > > > >
> > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > !MESSAGE Application error
> > > > > > !STACK 1
> > > > > > java.lang.IllegalStateException: Unable to acquire application
> > > service.
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > at
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > at
org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51308 is a reply to message #51198] |
Sat, 22 October 2005 00:37 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
yes. That is the standard osgi.bundles list for Eclipse. The runtime gives
you the registry etc and the update.configurator installs all the rest of
the bundles.
Jeff
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:dj97vt$8a9$1@news.eclipse.org...
> This worked however...
>
> osgi.bundles=org.eclipse.core.runtime@2:start,
> org.eclipse.update.configurator@3:start
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dj8foc$7j1$1@news.eclipse.org...
> > I tried add the following to config.ini but still got the same error:
> >
> > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > org.eclipse.core.runtime
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dj8cj9$2rr$1@news.eclipse.org...
> > > Thanks Jeff,
> > > I usually assume user error or configuration rather than a bug. For
> this
> > > particular issue, I assumed something configuration related as this
> worked
> > > fine for our 3.0x and 3.1M builds. This problem arose with the
> migration
> > > from 3.1M6 to 3.1.1.
> > >
> > > We do have a product and application defined and our
> > > INSTALL/configuration/config.ini contains the following entries (we
have
> > > never specified the osgi.bundles parameter):
> > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > on
> > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > >
> > > The INSTALL/features directory contains two features both of which
have
> a
> > > feature.xml:
> > >
> > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > >
> > > The INSTALL/plugins directory now contains all IDE and proprietary
> plugins
> > > (a result of trying to debug the problem)
> > >
> > > As for the launcher, the INSTALL directory contains what we've used
> > > previously:
> > >
> > > eclipse.exe
> > > startup.jar
> > > .eclipseproduct
> > >
> > > And our startup parameters are also how they've been previously:
> > >
> > > "C:\Program
> > Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > >
> > > So it sounds like we need to update the config.ini with at least one
> > bundle,
> > > which one(s)?
> > >
> > > osgi.bundles =??
> > >
> > > Paul
> > >
> > >
> > >
> > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > A couple things.
> > > >
> > > > - Bugzilla is more effective for this kind of issue
> > > > - The application service is registered by the runtime plugin. I
> > suspect
> > > > that you are not installing/starting the runtime. It should be
listed
> > on
> > > > the osgi.bundles list in the config.ini or on the command as a -D vm
> > arg.
> > > > - when you export the features, what are you doing for a launcher,
> > > > startup.jar, config.ini etc. You should consider defining a PRODUCT
> and
> > > > exporting the product and then packaging that up.
> > > >
> > > > Jeff
> > > >
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > Can anyone shed any light on this?
> > > > >
> > > > > thx
> > > > >
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > FYI, I use the feature export functionality of eclipse so that
all
> > > > > plugins,
> > > > > > both eclipse and ours, are moved into a staging area for the
> > > application
> > > > > > packaging step whereby I run a script which builds a
> self-extracting
> > > > > > executable. So I'm using the same plugins that are used in my
> > > > functional
> > > > > > development environment. I've been hoping that something is
> > "shoddy"
> > > > > > somewhere but I still don't understand what the source of this
> error
> > > is.
> > > > > > I've stepped through the code in the dev environment but I'm not
> > > > > connecting
> > > > > > the dots as to what circumstances will cause this to fail
> > > > > > (ParameterizedRunnable returns null):
> > > > > >
> > > > > > EclipseStarter.java
> > > > > >
> > > > > > public static Object run(Object argument) throws Exception {
> > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> > > //$NON-NLS-1$
> > > > > > if (!running)
> > > > > > throw new
> > > > > >
> > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > // if we are just initializing, do not run the application
just
> > > > return.
> > > > > > if (initialize)
> > > > > > return new Integer(0);
> > > > > > initializeApplicationTracker();
> > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > Profile.logTime("EclipseStarter.run(Object)()", "applicaton
> > tracker
> > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > (ParameterizedRunnable)
> > > > > > applicationTracker.getService();
> > > > > >
> > > > > >
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP application
> will
> > > not
> > > > > run
> > > > > > > as a standalone application (but works fine as a launch
> > > configuration
> > > > > from
> > > > > > > the IDE).
> > > > > > > I'm guessing this is something obvious but I can't seem to
find
> > it.
> > > > > This
> > > > > > > occurs
> > > > > > > whether I try to point to an existing workspace or not.
> > > > > > >
> > > > > > >
> > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > !MESSAGE Application error
> > > > > > > !STACK 1
> > > > > > > java.lang.IllegalStateException: Unable to acquire application
> > > > service.
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > at
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
Source)
> > > > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > Source)
> > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > at
> org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51658 is a reply to message #51308] |
Wed, 26 October 2005 15:13 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Jeff,
I thought this had resolved my build issues but I had forgotten that during
the troubleshooting process I had copied all of the Eclipse plugins into the
build area that is used as the source for building an installable image.
Anyway, upon realization of that, I removed all but the required plugins
(the same list of plugins used in my dev environment and specified in my
launch configuration). This broke my build and the platform could not find
my application as specified in the config.ini file. Anyway, now I'm
confused and clearly do not understand the configuration requirements for
RCP applications in 3.1.1. Do I need to specify additional bundles in the
config.ini for RCP applications (i.e. plugin which represents the primary
feature, all of them, etc.)??
As a reminder, all of this was functional in 3.01 and through 3.1 M6.
Here is how the application directory is structured:
INSTALL_LOC/
startup.jar
eclipse.ini
eclipse.exe
.eclipseproduct
/workspace
/plugins
...
/features
feature1(required eclipse plugins)
feature.xml
feature2(our plugins)
feature.xml
/configuration
config.ini
The config.ini contains:
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
on
eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start
This is the list of required eclipse plugins that our RCP application
depends on:
id="org.apache.ant"
id="org.apache.lucene"
id="org.eclipse.compare"
id="org.eclipse.core.commands"
id="org.eclipse.core.expressions"
id="org.eclipse.core.filebuffers"
id="org.eclipse.core.resources"
id="org.eclipse.core.resources.compatibility"
id="org.eclipse.core.resources.win32"
id="org.eclipse.core.runtime"
id="org.eclipse.core.runtime.compatibility"
id="org.eclipse.draw2d"
id="org.eclipse.emf"
id="org.eclipse.emf.common"
id="org.eclipse.emf.common.ui"
id="org.eclipse.emf.ecore"
id="org.eclipse.emf.ecore.xmi"
id="org.eclipse.emf.edit"
id="org.eclipse.emf.edit.ui"
id="org.eclipse.gef"
id="org.eclipse.help"
id="org.eclipse.help.appserver"
id="org.eclipse.help.base"
id="org.eclipse.help.ui"
id="org.eclipse.help.webapp"
id="org.eclipse.jface"
id="org.eclipse.jface.text"
id="org.eclipse.osgi"
id="org.eclipse.pde.runtime"
id="org.eclipse.swt"
id="org.eclipse.swt.win32.win32.x86"
id="org.eclipse.team.core"
id="org.eclipse.team.ui"
id="org.eclipse.text"
id="org.eclipse.tomcat"
id="org.eclipse.ui"
id="org.eclipse.ui.cheatsheets"
id="org.eclipse.ui.editors"
id="org.eclipse.ui.forms"
id="org.eclipse.ui.ide"
id="org.eclipse.ui.intro"
id="org.eclipse.ui.views"
id="org.eclipse.ui.win32"
id="org.eclipse.ui.workbench"
id="org.eclipse.ui.workbench.compatibility"
id="org.eclipse.ui.workbench.texteditor"
id="org.eclipse.update.configurator"
id="org.eclipse.update.core"
id="org.eclipse.update.core.win32"
id="org.eclipse.update.scheduler"
id="org.eclipse.update.ui"
id="org.junit"
thanks in advance
Paul
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:djc1ju$lk2$1@news.eclipse.org...
> yes. That is the standard osgi.bundles list for Eclipse. The runtime
gives
> you the registry etc and the update.configurator installs all the rest of
> the bundles.
>
> Jeff
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dj97vt$8a9$1@news.eclipse.org...
> > This worked however...
> >
> > osgi.bundles=org.eclipse.core.runtime@2:start,
> > org.eclipse.update.configurator@3:start
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dj8foc$7j1$1@news.eclipse.org...
> > > I tried add the following to config.ini but still got the same error:
> > >
> > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > org.eclipse.core.runtime
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > Thanks Jeff,
> > > > I usually assume user error or configuration rather than a bug. For
> > this
> > > > particular issue, I assumed something configuration related as this
> > worked
> > > > fine for our 3.0x and 3.1M builds. This problem arose with the
> > migration
> > > > from 3.1M6 to 3.1.1.
> > > >
> > > > We do have a product and application defined and our
> > > > INSTALL/configuration/config.ini contains the following entries (we
> have
> > > > never specified the osgi.bundles parameter):
> > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > on
> > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > >
> > > > The INSTALL/features directory contains two features both of which
> have
> > a
> > > > feature.xml:
> > > >
> > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > >
> > > > The INSTALL/plugins directory now contains all IDE and proprietary
> > plugins
> > > > (a result of trying to debug the problem)
> > > >
> > > > As for the launcher, the INSTALL directory contains what we've used
> > > > previously:
> > > >
> > > > eclipse.exe
> > > > startup.jar
> > > > .eclipseproduct
> > > >
> > > > And our startup parameters are also how they've been previously:
> > > >
> > > > "C:\Program
> > > Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > >
> > > > So it sounds like we need to update the config.ini with at least one
> > > bundle,
> > > > which one(s)?
> > > >
> > > > osgi.bundles =??
> > > >
> > > > Paul
> > > >
> > > >
> > > >
> > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > A couple things.
> > > > >
> > > > > - Bugzilla is more effective for this kind of issue
> > > > > - The application service is registered by the runtime plugin. I
> > > suspect
> > > > > that you are not installing/starting the runtime. It should be
> listed
> > > on
> > > > > the osgi.bundles list in the config.ini or on the command as a -D
vm
> > > arg.
> > > > > - when you export the features, what are you doing for a launcher,
> > > > > startup.jar, config.ini etc. You should consider defining a
PRODUCT
> > and
> > > > > exporting the product and then packaging that up.
> > > > >
> > > > > Jeff
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > Can anyone shed any light on this?
> > > > > >
> > > > > > thx
> > > > > >
> > > > > >
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > FYI, I use the feature export functionality of eclipse so that
> all
> > > > > > plugins,
> > > > > > > both eclipse and ours, are moved into a staging area for the
> > > > application
> > > > > > > packaging step whereby I run a script which builds a
> > self-extracting
> > > > > > > executable. So I'm using the same plugins that are used in my
> > > > > functional
> > > > > > > development environment. I've been hoping that something is
> > > "shoddy"
> > > > > > > somewhere but I still don't understand what the source of this
> > error
> > > > is.
> > > > > > > I've stepped through the code in the dev environment but I'm
not
> > > > > > connecting
> > > > > > > the dots as to what circumstances will cause this to fail
> > > > > > > (ParameterizedRunnable returns null):
> > > > > > >
> > > > > > > EclipseStarter.java
> > > > > > >
> > > > > > > public static Object run(Object argument) throws Exception {
> > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> > > > //$NON-NLS-1$
> > > > > > > if (!running)
> > > > > > > throw new
> > > > > > >
> > > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > // if we are just initializing, do not run the application
> just
> > > > > return.
> > > > > > > if (initialize)
> > > > > > > return new Integer(0);
> > > > > > > initializeApplicationTracker();
> > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > Profile.logTime("EclipseStarter.run(Object)()", "applicaton
> > > tracker
> > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > (ParameterizedRunnable)
> > > > > > > applicationTracker.getService();
> > > > > > >
> > > > > > >
> > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
application
> > will
> > > > not
> > > > > > run
> > > > > > > > as a standalone application (but works fine as a launch
> > > > configuration
> > > > > > from
> > > > > > > > the IDE).
> > > > > > > > I'm guessing this is something obvious but I can't seem to
> find
> > > it.
> > > > > > This
> > > > > > > > occurs
> > > > > > > > whether I try to point to an existing workspace or not.
> > > > > > > >
> > > > > > > >
> > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > !MESSAGE Application error
> > > > > > > > !STACK 1
> > > > > > > > java.lang.IllegalStateException: Unable to acquire
application
> > > > > service.
> > > > > > > > at
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > at
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> Source)
> > > > > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > Source)
> > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > at
> > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #51817 is a reply to message #51658] |
Thu, 27 October 2005 02:14 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Paul,
The structure looks good. I can't think of anything that changed after M6.
The error you were getting in the orginal post is very low-level and is
indicating to me that the runtime plugin is not starting. Try the following
to investigate further.
- put -console -noexit on the command line. This should give you an OSGi
console and stop Equionx from exiting
- at the osgi> prompt, type ss (short status)
- you should see a list of bundles.
- look at the list carefully. You want everything to be in RESOLVED or
ACTIVE state. plugins that are in INSTALLED state are potential problems.
- for any bundle that is listed as INSTALLED, get its number and type diag
NN where NN is the bundle id number.
- this should report the reasons why it is not RESOLVED or ACTIVE.
- if you find some problems, try to fix them.
The only other thing I can think of is that the product definition should
specify the application. Please ensure that hte product extension has the
correct application id.
For now that is all I can think of.
Jeff
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:djo6ed$oab$1@news.eclipse.org...
> Jeff,
> I thought this had resolved my build issues but I had forgotten that
during
> the troubleshooting process I had copied all of the Eclipse plugins into
the
> build area that is used as the source for building an installable image.
> Anyway, upon realization of that, I removed all but the required plugins
> (the same list of plugins used in my dev environment and specified in my
> launch configuration). This broke my build and the platform could not
find
> my application as specified in the config.ini file. Anyway, now I'm
> confused and clearly do not understand the configuration requirements for
> RCP applications in 3.1.1. Do I need to specify additional bundles in the
> config.ini for RCP applications (i.e. plugin which represents the primary
> feature, all of them, etc.)??
>
> As a reminder, all of this was functional in 3.01 and through 3.1 M6.
>
> Here is how the application directory is structured:
>
> INSTALL_LOC/
> startup.jar
> eclipse.ini
> eclipse.exe
> .eclipseproduct
> /workspace
> /plugins
> ...
> /features
> feature1(required eclipse plugins)
> feature.xml
> feature2(our plugins)
> feature.xml
> /configuration
> config.ini
>
> The config.ini contains:
>
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> on
> eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> osgi.bundles=org.eclipse.core.runtime@2:start,
> org.eclipse.update.configurator@3:start
>
> This is the list of required eclipse plugins that our RCP application
> depends on:
>
> id="org.apache.ant"
> id="org.apache.lucene"
> id="org.eclipse.compare"
> id="org.eclipse.core.commands"
> id="org.eclipse.core.expressions"
> id="org.eclipse.core.filebuffers"
> id="org.eclipse.core.resources"
> id="org.eclipse.core.resources.compatibility"
> id="org.eclipse.core.resources.win32"
> id="org.eclipse.core.runtime"
> id="org.eclipse.core.runtime.compatibility"
> id="org.eclipse.draw2d"
> id="org.eclipse.emf"
> id="org.eclipse.emf.common"
> id="org.eclipse.emf.common.ui"
> id="org.eclipse.emf.ecore"
> id="org.eclipse.emf.ecore.xmi"
> id="org.eclipse.emf.edit"
> id="org.eclipse.emf.edit.ui"
> id="org.eclipse.gef"
> id="org.eclipse.help"
> id="org.eclipse.help.appserver"
> id="org.eclipse.help.base"
> id="org.eclipse.help.ui"
> id="org.eclipse.help.webapp"
> id="org.eclipse.jface"
> id="org.eclipse.jface.text"
> id="org.eclipse.osgi"
> id="org.eclipse.pde.runtime"
> id="org.eclipse.swt"
> id="org.eclipse.swt.win32.win32.x86"
> id="org.eclipse.team.core"
> id="org.eclipse.team.ui"
> id="org.eclipse.text"
> id="org.eclipse.tomcat"
> id="org.eclipse.ui"
> id="org.eclipse.ui.cheatsheets"
> id="org.eclipse.ui.editors"
> id="org.eclipse.ui.forms"
> id="org.eclipse.ui.ide"
> id="org.eclipse.ui.intro"
> id="org.eclipse.ui.views"
> id="org.eclipse.ui.win32"
> id="org.eclipse.ui.workbench"
> id="org.eclipse.ui.workbench.compatibility"
> id="org.eclipse.ui.workbench.texteditor"
> id="org.eclipse.update.configurator"
> id="org.eclipse.update.core"
> id="org.eclipse.update.core.win32"
> id="org.eclipse.update.scheduler"
> id="org.eclipse.update.ui"
> id="org.junit"
>
> thanks in advance
>
> Paul
>
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> news:djc1ju$lk2$1@news.eclipse.org...
> > yes. That is the standard osgi.bundles list for Eclipse. The runtime
> gives
> > you the registry etc and the update.configurator installs all the rest
of
> > the bundles.
> >
> > Jeff
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:dj97vt$8a9$1@news.eclipse.org...
> > > This worked however...
> > >
> > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > org.eclipse.update.configurator@3:start
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dj8foc$7j1$1@news.eclipse.org...
> > > > I tried add the following to config.ini but still got the same
error:
> > > >
> > > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > > org.eclipse.core.runtime
> > > >
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > > Thanks Jeff,
> > > > > I usually assume user error or configuration rather than a bug.
For
> > > this
> > > > > particular issue, I assumed something configuration related as
this
> > > worked
> > > > > fine for our 3.0x and 3.1M builds. This problem arose with the
> > > migration
> > > > > from 3.1M6 to 3.1.1.
> > > > >
> > > > > We do have a product and application defined and our
> > > > > INSTALL/configuration/config.ini contains the following entries
(we
> > have
> > > > > never specified the osgi.bundles parameter):
> > > > >
> > > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > > on
> > > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > >
> > > > > The INSTALL/features directory contains two features both of which
> > have
> > > a
> > > > > feature.xml:
> > > > >
> > > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > > >
> > > > > The INSTALL/plugins directory now contains all IDE and proprietary
> > > plugins
> > > > > (a result of trying to debug the problem)
> > > > >
> > > > > As for the launcher, the INSTALL directory contains what we've
used
> > > > > previously:
> > > > >
> > > > > eclipse.exe
> > > > > startup.jar
> > > > > .eclipseproduct
> > > > >
> > > > > And our startup parameters are also how they've been previously:
> > > > >
> > > > > "C:\Program
> > > > Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > > >
> > > > > So it sounds like we need to update the config.ini with at least
one
> > > > bundle,
> > > > > which one(s)?
> > > > >
> > > > > osgi.bundles =??
> > > > >
> > > > > Paul
> > > > >
> > > > >
> > > > >
> > > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > > A couple things.
> > > > > >
> > > > > > - Bugzilla is more effective for this kind of issue
> > > > > > - The application service is registered by the runtime plugin.
I
> > > > suspect
> > > > > > that you are not installing/starting the runtime. It should be
> > listed
> > > > on
> > > > > > the osgi.bundles list in the config.ini or on the command as
a -D
> vm
> > > > arg.
> > > > > > - when you export the features, what are you doing for a
launcher,
> > > > > > startup.jar, config.ini etc. You should consider defining a
> PRODUCT
> > > and
> > > > > > exporting the product and then packaging that up.
> > > > > >
> > > > > > Jeff
> > > > > >
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > > Can anyone shed any light on this?
> > > > > > >
> > > > > > > thx
> > > > > > >
> > > > > > >
> > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > > FYI, I use the feature export functionality of eclipse so
that
> > all
> > > > > > > plugins,
> > > > > > > > both eclipse and ours, are moved into a staging area for the
> > > > > application
> > > > > > > > packaging step whereby I run a script which builds a
> > > self-extracting
> > > > > > > > executable. So I'm using the same plugins that are used in
my
> > > > > > functional
> > > > > > > > development environment. I've been hoping that something is
> > > > "shoddy"
> > > > > > > > somewhere but I still don't understand what the source of
this
> > > error
> > > > > is.
> > > > > > > > I've stepped through the code in the dev environment but I'm
> not
> > > > > > > connecting
> > > > > > > > the dots as to what circumstances will cause this to fail
> > > > > > > > (ParameterizedRunnable returns null):
> > > > > > > >
> > > > > > > > EclipseStarter.java
> > > > > > > >
> > > > > > > > public static Object run(Object argument) throws Exception
{
> > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> > > > > //$NON-NLS-1$
> > > > > > > > if (!running)
> > > > > > > > throw new
> > > > > > > >
> > > >
IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > > // if we are just initializing, do not run the application
> > just
> > > > > > return.
> > > > > > > > if (initialize)
> > > > > > > > return new Integer(0);
> > > > > > > > initializeApplicationTracker();
> > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > Profile.logTime("EclipseStarter.run(Object)()",
"applicaton
> > > > tracker
> > > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > > (ParameterizedRunnable)
> > > > > > > > applicationTracker.getService();
> > > > > > > >
> > > > > > > >
> > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
message
> > > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
> application
> > > will
> > > > > not
> > > > > > > run
> > > > > > > > > as a standalone application (but works fine as a launch
> > > > > configuration
> > > > > > > from
> > > > > > > > > the IDE).
> > > > > > > > > I'm guessing this is something obvious but I can't seem to
> > find
> > > > it.
> > > > > > > This
> > > > > > > > > occurs
> > > > > > > > > whether I try to point to an existing workspace or not.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > > !MESSAGE Application error
> > > > > > > > > !STACK 1
> > > > > > > > > java.lang.IllegalStateException: Unable to acquire
> application
> > > > > > service.
> > > > > > > > > at
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > > at
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > Source)
> > > > > > > > > at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > > Source)
> > > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > > at
> > > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > > at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #52047 is a reply to message #51817] |
Tue, 01 November 2005 17:50 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Thanks Jeff, I'll take a look.
Also, it sounds like you're saying that an RCP application need only define
osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start
provided eclipse.product and eclipse.application are defined and that the
remaining configuration is "correct"?
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:djpd4e$8qk$1@news.eclipse.org...
> Paul,
> The structure looks good. I can't think of anything that changed after
M6.
> The error you were getting in the orginal post is very low-level and is
> indicating to me that the runtime plugin is not starting. Try the
following
> to investigate further.
> - put -console -noexit on the command line. This should give you an OSGi
> console and stop Equionx from exiting
> - at the osgi> prompt, type ss (short status)
> - you should see a list of bundles.
> - look at the list carefully. You want everything to be in RESOLVED or
> ACTIVE state. plugins that are in INSTALLED state are potential problems.
> - for any bundle that is listed as INSTALLED, get its number and type diag
> NN where NN is the bundle id number.
> - this should report the reasons why it is not RESOLVED or ACTIVE.
> - if you find some problems, try to fix them.
>
> The only other thing I can think of is that the product definition should
> specify the application. Please ensure that hte product extension has the
> correct application id.
>
> For now that is all I can think of.
>
> Jeff
>
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:djo6ed$oab$1@news.eclipse.org...
> > Jeff,
> > I thought this had resolved my build issues but I had forgotten that
> during
> > the troubleshooting process I had copied all of the Eclipse plugins into
> the
> > build area that is used as the source for building an installable image.
> > Anyway, upon realization of that, I removed all but the required plugins
> > (the same list of plugins used in my dev environment and specified in my
> > launch configuration). This broke my build and the platform could not
> find
> > my application as specified in the config.ini file. Anyway, now I'm
> > confused and clearly do not understand the configuration requirements
for
> > RCP applications in 3.1.1. Do I need to specify additional bundles in
the
> > config.ini for RCP applications (i.e. plugin which represents the
primary
> > feature, all of them, etc.)??
> >
> > As a reminder, all of this was functional in 3.01 and through 3.1 M6.
> >
> > Here is how the application directory is structured:
> >
> > INSTALL_LOC/
> > startup.jar
> > eclipse.ini
> > eclipse.exe
> > .eclipseproduct
> > /workspace
> > /plugins
> > ...
> > /features
> > feature1(required eclipse plugins)
> > feature.xml
> > feature2(our plugins)
> > feature.xml
> > /configuration
> > config.ini
> >
> > The config.ini contains:
> >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > on
> > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > osgi.bundles=org.eclipse.core.runtime@2:start,
> > org.eclipse.update.configurator@3:start
> >
> > This is the list of required eclipse plugins that our RCP application
> > depends on:
> >
> > id="org.apache.ant"
> > id="org.apache.lucene"
> > id="org.eclipse.compare"
> > id="org.eclipse.core.commands"
> > id="org.eclipse.core.expressions"
> > id="org.eclipse.core.filebuffers"
> > id="org.eclipse.core.resources"
> > id="org.eclipse.core.resources.compatibility"
> > id="org.eclipse.core.resources.win32"
> > id="org.eclipse.core.runtime"
> > id="org.eclipse.core.runtime.compatibility"
> > id="org.eclipse.draw2d"
> > id="org.eclipse.emf"
> > id="org.eclipse.emf.common"
> > id="org.eclipse.emf.common.ui"
> > id="org.eclipse.emf.ecore"
> > id="org.eclipse.emf.ecore.xmi"
> > id="org.eclipse.emf.edit"
> > id="org.eclipse.emf.edit.ui"
> > id="org.eclipse.gef"
> > id="org.eclipse.help"
> > id="org.eclipse.help.appserver"
> > id="org.eclipse.help.base"
> > id="org.eclipse.help.ui"
> > id="org.eclipse.help.webapp"
> > id="org.eclipse.jface"
> > id="org.eclipse.jface.text"
> > id="org.eclipse.osgi"
> > id="org.eclipse.pde.runtime"
> > id="org.eclipse.swt"
> > id="org.eclipse.swt.win32.win32.x86"
> > id="org.eclipse.team.core"
> > id="org.eclipse.team.ui"
> > id="org.eclipse.text"
> > id="org.eclipse.tomcat"
> > id="org.eclipse.ui"
> > id="org.eclipse.ui.cheatsheets"
> > id="org.eclipse.ui.editors"
> > id="org.eclipse.ui.forms"
> > id="org.eclipse.ui.ide"
> > id="org.eclipse.ui.intro"
> > id="org.eclipse.ui.views"
> > id="org.eclipse.ui.win32"
> > id="org.eclipse.ui.workbench"
> > id="org.eclipse.ui.workbench.compatibility"
> > id="org.eclipse.ui.workbench.texteditor"
> > id="org.eclipse.update.configurator"
> > id="org.eclipse.update.core"
> > id="org.eclipse.update.core.win32"
> > id="org.eclipse.update.scheduler"
> > id="org.eclipse.update.ui"
> > id="org.junit"
> >
> > thanks in advance
> >
> > Paul
> >
> > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > news:djc1ju$lk2$1@news.eclipse.org...
> > > yes. That is the standard osgi.bundles list for Eclipse. The runtime
> > gives
> > > you the registry etc and the update.configurator installs all the rest
> of
> > > the bundles.
> > >
> > > Jeff
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:dj97vt$8a9$1@news.eclipse.org...
> > > > This worked however...
> > > >
> > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > org.eclipse.update.configurator@3:start
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dj8foc$7j1$1@news.eclipse.org...
> > > > > I tried add the following to config.ini but still got the same
> error:
> > > > >
> > > > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > > > org.eclipse.core.runtime
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > > > Thanks Jeff,
> > > > > > I usually assume user error or configuration rather than a bug.
> For
> > > > this
> > > > > > particular issue, I assumed something configuration related as
> this
> > > > worked
> > > > > > fine for our 3.0x and 3.1M builds. This problem arose with the
> > > > migration
> > > > > > from 3.1M6 to 3.1.1.
> > > > > >
> > > > > > We do have a product and application defined and our
> > > > > > INSTALL/configuration/config.ini contains the following entries
> (we
> > > have
> > > > > > never specified the osgi.bundles parameter):
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > > > on
> > > > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > > >
> > > > > > The INSTALL/features directory contains two features both of
which
> > > have
> > > > a
> > > > > > feature.xml:
> > > > > >
> > > > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > > > >
> > > > > > The INSTALL/plugins directory now contains all IDE and
proprietary
> > > > plugins
> > > > > > (a result of trying to debug the problem)
> > > > > >
> > > > > > As for the launcher, the INSTALL directory contains what we've
> used
> > > > > > previously:
> > > > > >
> > > > > > eclipse.exe
> > > > > > startup.jar
> > > > > > .eclipseproduct
> > > > > >
> > > > > > And our startup parameters are also how they've been previously:
> > > > > >
> > > > > > "C:\Program
> > > > > Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > > > >
> > > > > > So it sounds like we need to update the config.ini with at least
> one
> > > > > bundle,
> > > > > > which one(s)?
> > > > > >
> > > > > > osgi.bundles =??
> > > > > >
> > > > > > Paul
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > > > A couple things.
> > > > > > >
> > > > > > > - Bugzilla is more effective for this kind of issue
> > > > > > > - The application service is registered by the runtime plugin.
> I
> > > > > suspect
> > > > > > > that you are not installing/starting the runtime. It should
be
> > > listed
> > > > > on
> > > > > > > the osgi.bundles list in the config.ini or on the command as
> a -D
> > vm
> > > > > arg.
> > > > > > > - when you export the features, what are you doing for a
> launcher,
> > > > > > > startup.jar, config.ini etc. You should consider defining a
> > PRODUCT
> > > > and
> > > > > > > exporting the product and then packaging that up.
> > > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > > > Can anyone shed any light on this?
> > > > > > > >
> > > > > > > > thx
> > > > > > > >
> > > > > > > >
> > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
message
> > > > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > > > FYI, I use the feature export functionality of eclipse so
> that
> > > all
> > > > > > > > plugins,
> > > > > > > > > both eclipse and ours, are moved into a staging area for
the
> > > > > > application
> > > > > > > > > packaging step whereby I run a script which builds a
> > > > self-extracting
> > > > > > > > > executable. So I'm using the same plugins that are used
in
> my
> > > > > > > functional
> > > > > > > > > development environment. I've been hoping that something
is
> > > > > "shoddy"
> > > > > > > > > somewhere but I still don't understand what the source of
> this
> > > > error
> > > > > > is.
> > > > > > > > > I've stepped through the code in the dev environment but
I'm
> > not
> > > > > > > > connecting
> > > > > > > > > the dots as to what circumstances will cause this to fail
> > > > > > > > > (ParameterizedRunnable returns null):
> > > > > > > > >
> > > > > > > > > EclipseStarter.java
> > > > > > > > >
> > > > > > > > > public static Object run(Object argument) throws
Exception
> {
> > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > Profile.logEnter("EclipseStarter.run(Object)()", null);
> > > > > > //$NON-NLS-1$
> > > > > > > > > if (!running)
> > > > > > > > > throw new
> > > > > > > > >
> > > > >
> IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > > > // if we are just initializing, do not run the
application
> > > just
> > > > > > > return.
> > > > > > > > > if (initialize)
> > > > > > > > > return new Integer(0);
> > > > > > > > > initializeApplicationTracker();
> > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > Profile.logTime("EclipseStarter.run(Object)()",
> "applicaton
> > > > > tracker
> > > > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > > > (ParameterizedRunnable)
> > > > > > > > > applicationTracker.getService();
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> message
> > > > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
> > application
> > > > will
> > > > > > not
> > > > > > > > run
> > > > > > > > > > as a standalone application (but works fine as a launch
> > > > > > configuration
> > > > > > > > from
> > > > > > > > > > the IDE).
> > > > > > > > > > I'm guessing this is something obvious but I can't seem
to
> > > find
> > > > > it.
> > > > > > > > This
> > > > > > > > > > occurs
> > > > > > > > > > whether I try to point to an existing workspace or not.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > > > !MESSAGE Application error
> > > > > > > > > > !STACK 1
> > > > > > > > > > java.lang.IllegalStateException: Unable to acquire
> > application
> > > > > > > service.
> > > > > > > > > > at
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > > > at
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > Method)
> > > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > > Source)
> > > > > > > > > > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > > > Source)
> > > > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > > > at
> > > > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > > > at
org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #52126 is a reply to message #52047] |
Wed, 02 November 2005 03:24 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Paul, what I am suggesting is a config.ini that looks like
eclipse.product=<your product id here>
osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start
The product extension should then identify the application to use when
running that product.
Jeff
"Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
news:dk89t0$6fl$1@news.eclipse.org...
> Thanks Jeff, I'll take a look.
>
> Also, it sounds like you're saying that an RCP application need only
define
> osgi.bundles=org.eclipse.core.runtime@2:start,
> org.eclipse.update.configurator@3:start
> provided eclipse.product and eclipse.application are defined and that the
> remaining configuration is "correct"?
>
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> news:djpd4e$8qk$1@news.eclipse.org...
> > Paul,
> > The structure looks good. I can't think of anything that changed after
> M6.
> > The error you were getting in the orginal post is very low-level and is
> > indicating to me that the runtime plugin is not starting. Try the
> following
> > to investigate further.
> > - put -console -noexit on the command line. This should give you an
OSGi
> > console and stop Equionx from exiting
> > - at the osgi> prompt, type ss (short status)
> > - you should see a list of bundles.
> > - look at the list carefully. You want everything to be in RESOLVED or
> > ACTIVE state. plugins that are in INSTALLED state are potential
problems.
> > - for any bundle that is listed as INSTALLED, get its number and type
diag
> > NN where NN is the bundle id number.
> > - this should report the reasons why it is not RESOLVED or ACTIVE.
> > - if you find some problems, try to fix them.
> >
> > The only other thing I can think of is that the product definition
should
> > specify the application. Please ensure that hte product extension has
the
> > correct application id.
> >
> > For now that is all I can think of.
> >
> > Jeff
> >
> >
> > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > news:djo6ed$oab$1@news.eclipse.org...
> > > Jeff,
> > > I thought this had resolved my build issues but I had forgotten that
> > during
> > > the troubleshooting process I had copied all of the Eclipse plugins
into
> > the
> > > build area that is used as the source for building an installable
image.
> > > Anyway, upon realization of that, I removed all but the required
plugins
> > > (the same list of plugins used in my dev environment and specified in
my
> > > launch configuration). This broke my build and the platform could not
> > find
> > > my application as specified in the config.ini file. Anyway, now I'm
> > > confused and clearly do not understand the configuration requirements
> for
> > > RCP applications in 3.1.1. Do I need to specify additional bundles in
> the
> > > config.ini for RCP applications (i.e. plugin which represents the
> primary
> > > feature, all of them, etc.)??
> > >
> > > As a reminder, all of this was functional in 3.01 and through 3.1 M6.
> > >
> > > Here is how the application directory is structured:
> > >
> > > INSTALL_LOC/
> > > startup.jar
> > > eclipse.ini
> > > eclipse.exe
> > > .eclipseproduct
> > > /workspace
> > > /plugins
> > > ...
> > > /features
> > > feature1(required eclipse plugins)
> > > feature.xml
> > > feature2(our plugins)
> > > feature.xml
> > > /configuration
> > > config.ini
> > >
> > > The config.ini contains:
> > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > on
> > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > org.eclipse.update.configurator@3:start
> > >
> > > This is the list of required eclipse plugins that our RCP application
> > > depends on:
> > >
> > > id="org.apache.ant"
> > > id="org.apache.lucene"
> > > id="org.eclipse.compare"
> > > id="org.eclipse.core.commands"
> > > id="org.eclipse.core.expressions"
> > > id="org.eclipse.core.filebuffers"
> > > id="org.eclipse.core.resources"
> > > id="org.eclipse.core.resources.compatibility"
> > > id="org.eclipse.core.resources.win32"
> > > id="org.eclipse.core.runtime"
> > > id="org.eclipse.core.runtime.compatibility"
> > > id="org.eclipse.draw2d"
> > > id="org.eclipse.emf"
> > > id="org.eclipse.emf.common"
> > > id="org.eclipse.emf.common.ui"
> > > id="org.eclipse.emf.ecore"
> > > id="org.eclipse.emf.ecore.xmi"
> > > id="org.eclipse.emf.edit"
> > > id="org.eclipse.emf.edit.ui"
> > > id="org.eclipse.gef"
> > > id="org.eclipse.help"
> > > id="org.eclipse.help.appserver"
> > > id="org.eclipse.help.base"
> > > id="org.eclipse.help.ui"
> > > id="org.eclipse.help.webapp"
> > > id="org.eclipse.jface"
> > > id="org.eclipse.jface.text"
> > > id="org.eclipse.osgi"
> > > id="org.eclipse.pde.runtime"
> > > id="org.eclipse.swt"
> > > id="org.eclipse.swt.win32.win32.x86"
> > > id="org.eclipse.team.core"
> > > id="org.eclipse.team.ui"
> > > id="org.eclipse.text"
> > > id="org.eclipse.tomcat"
> > > id="org.eclipse.ui"
> > > id="org.eclipse.ui.cheatsheets"
> > > id="org.eclipse.ui.editors"
> > > id="org.eclipse.ui.forms"
> > > id="org.eclipse.ui.ide"
> > > id="org.eclipse.ui.intro"
> > > id="org.eclipse.ui.views"
> > > id="org.eclipse.ui.win32"
> > > id="org.eclipse.ui.workbench"
> > > id="org.eclipse.ui.workbench.compatibility"
> > > id="org.eclipse.ui.workbench.texteditor"
> > > id="org.eclipse.update.configurator"
> > > id="org.eclipse.update.core"
> > > id="org.eclipse.update.core.win32"
> > > id="org.eclipse.update.scheduler"
> > > id="org.eclipse.update.ui"
> > > id="org.junit"
> > >
> > > thanks in advance
> > >
> > > Paul
> > >
> > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > news:djc1ju$lk2$1@news.eclipse.org...
> > > > yes. That is the standard osgi.bundles list for Eclipse. The
runtime
> > > gives
> > > > you the registry etc and the update.configurator installs all the
rest
> > of
> > > > the bundles.
> > > >
> > > > Jeff
> > > >
> > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > news:dj97vt$8a9$1@news.eclipse.org...
> > > > > This worked however...
> > > > >
> > > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > > org.eclipse.update.configurator@3:start
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj8foc$7j1$1@news.eclipse.org...
> > > > > > I tried add the following to config.ini but still got the same
> > error:
> > > > > >
> > > > > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > > > > org.eclipse.core.runtime
> > > > > >
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > > > > Thanks Jeff,
> > > > > > > I usually assume user error or configuration rather than a
bug.
> > For
> > > > > this
> > > > > > > particular issue, I assumed something configuration related as
> > this
> > > > > worked
> > > > > > > fine for our 3.0x and 3.1M builds. This problem arose with
the
> > > > > migration
> > > > > > > from 3.1M6 to 3.1.1.
> > > > > > >
> > > > > > > We do have a product and application defined and our
> > > > > > > INSTALL/configuration/config.ini contains the following
entries
> > (we
> > > > have
> > > > > > > never specified the osgi.bundles parameter):
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > > > > on
> > > > > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > > > >
> > > > > > > The INSTALL/features directory contains two features both of
> which
> > > > have
> > > > > a
> > > > > > > feature.xml:
> > > > > > >
> > > > > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > > > > >
> > > > > > > The INSTALL/plugins directory now contains all IDE and
> proprietary
> > > > > plugins
> > > > > > > (a result of trying to debug the problem)
> > > > > > >
> > > > > > > As for the launcher, the INSTALL directory contains what we've
> > used
> > > > > > > previously:
> > > > > > >
> > > > > > > eclipse.exe
> > > > > > > startup.jar
> > > > > > > .eclipseproduct
> > > > > > >
> > > > > > > And our startup parameters are also how they've been
previously:
> > > > > > >
> > > > > > > "C:\Program
> > > > > > Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > > > > >
> > > > > > > So it sounds like we need to update the config.ini with at
least
> > one
> > > > > > bundle,
> > > > > > > which one(s)?
> > > > > > >
> > > > > > > osgi.bundles =??
> > > > > > >
> > > > > > > Paul
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in
message
> > > > > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > > > > A couple things.
> > > > > > > >
> > > > > > > > - Bugzilla is more effective for this kind of issue
> > > > > > > > - The application service is registered by the runtime
plugin.
> > I
> > > > > > suspect
> > > > > > > > that you are not installing/starting the runtime. It should
> be
> > > > listed
> > > > > > on
> > > > > > > > the osgi.bundles list in the config.ini or on the command as
> > a -D
> > > vm
> > > > > > arg.
> > > > > > > > - when you export the features, what are you doing for a
> > launcher,
> > > > > > > > startup.jar, config.ini etc. You should consider defining a
> > > PRODUCT
> > > > > and
> > > > > > > > exporting the product and then packaging that up.
> > > > > > > >
> > > > > > > > Jeff
> > > > > > > >
> > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
message
> > > > > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > > > > Can anyone shed any light on this?
> > > > > > > > >
> > > > > > > > > thx
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> message
> > > > > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > > > > FYI, I use the feature export functionality of eclipse
so
> > that
> > > > all
> > > > > > > > > plugins,
> > > > > > > > > > both eclipse and ours, are moved into a staging area for
> the
> > > > > > > application
> > > > > > > > > > packaging step whereby I run a script which builds a
> > > > > self-extracting
> > > > > > > > > > executable. So I'm using the same plugins that are used
> in
> > my
> > > > > > > > functional
> > > > > > > > > > development environment. I've been hoping that
something
> is
> > > > > > "shoddy"
> > > > > > > > > > somewhere but I still don't understand what the source
of
> > this
> > > > > error
> > > > > > > is.
> > > > > > > > > > I've stepped through the code in the dev environment but
> I'm
> > > not
> > > > > > > > > connecting
> > > > > > > > > > the dots as to what circumstances will cause this to
fail
> > > > > > > > > > (ParameterizedRunnable returns null):
> > > > > > > > > >
> > > > > > > > > > EclipseStarter.java
> > > > > > > > > >
> > > > > > > > > > public static Object run(Object argument) throws
> Exception
> > {
> > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > Profile.logEnter("EclipseStarter.run(Object)()",
null);
> > > > > > > //$NON-NLS-1$
> > > > > > > > > > if (!running)
> > > > > > > > > > throw new
> > > > > > > > > >
> > > > > >
> > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > > > > // if we are just initializing, do not run the
> application
> > > > just
> > > > > > > > return.
> > > > > > > > > > if (initialize)
> > > > > > > > > > return new Integer(0);
> > > > > > > > > > initializeApplicationTracker();
> > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > Profile.logTime("EclipseStarter.run(Object)()",
> > "applicaton
> > > > > > tracker
> > > > > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > > > > (ParameterizedRunnable)
> > > > > > > > > > applicationTracker.getService();
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> > message
> > > > > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
> > > application
> > > > > will
> > > > > > > not
> > > > > > > > > run
> > > > > > > > > > > as a standalone application (but works fine as a
launch
> > > > > > > configuration
> > > > > > > > > from
> > > > > > > > > > > the IDE).
> > > > > > > > > > > I'm guessing this is something obvious but I can't
seem
> to
> > > > find
> > > > > > it.
> > > > > > > > > This
> > > > > > > > > > > occurs
> > > > > > > > > > > whether I try to point to an existing workspace or
not.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > > > > !MESSAGE Application error
> > > > > > > > > > > !STACK 1
> > > > > > > > > > > java.lang.IllegalStateException: Unable to acquire
> > > application
> > > > > > > > service.
> > > > > > > > > > > at
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > > > > at
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > > > > at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > > Method)
> > > > > > > > > > > at
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > > > Source)
> > > > > > > > > > > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > > > > Source)
> > > > > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > > > > at
> > > > > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > > > > at
> org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > > > > at org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > > > > at org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #52313 is a reply to message #52126] |
Wed, 02 November 2005 18:02 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Thanks, I just wanted to make sure that I was clear on that-it's got to be
something in my environment.
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:dk9bgo$fqr$1@news.eclipse.org...
> Paul, what I am suggesting is a config.ini that looks like
>
> eclipse.product=<your product id here>
> osgi.bundles=org.eclipse.core.runtime@2:start,
> org.eclipse.update.configurator@3:start
>
> The product extension should then identify the application to use when
> running that product.
>
> Jeff
>
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dk89t0$6fl$1@news.eclipse.org...
> > Thanks Jeff, I'll take a look.
> >
> > Also, it sounds like you're saying that an RCP application need only
> define
> > osgi.bundles=org.eclipse.core.runtime@2:start,
> > org.eclipse.update.configurator@3:start
> > provided eclipse.product and eclipse.application are defined and that
the
> > remaining configuration is "correct"?
> >
> > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > news:djpd4e$8qk$1@news.eclipse.org...
> > > Paul,
> > > The structure looks good. I can't think of anything that changed
after
> > M6.
> > > The error you were getting in the orginal post is very low-level and
is
> > > indicating to me that the runtime plugin is not starting. Try the
> > following
> > > to investigate further.
> > > - put -console -noexit on the command line. This should give you an
> OSGi
> > > console and stop Equionx from exiting
> > > - at the osgi> prompt, type ss (short status)
> > > - you should see a list of bundles.
> > > - look at the list carefully. You want everything to be in RESOLVED
or
> > > ACTIVE state. plugins that are in INSTALLED state are potential
> problems.
> > > - for any bundle that is listed as INSTALLED, get its number and type
> diag
> > > NN where NN is the bundle id number.
> > > - this should report the reasons why it is not RESOLVED or ACTIVE.
> > > - if you find some problems, try to fix them.
> > >
> > > The only other thing I can think of is that the product definition
> should
> > > specify the application. Please ensure that hte product extension has
> the
> > > correct application id.
> > >
> > > For now that is all I can think of.
> > >
> > > Jeff
> > >
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:djo6ed$oab$1@news.eclipse.org...
> > > > Jeff,
> > > > I thought this had resolved my build issues but I had forgotten that
> > > during
> > > > the troubleshooting process I had copied all of the Eclipse plugins
> into
> > > the
> > > > build area that is used as the source for building an installable
> image.
> > > > Anyway, upon realization of that, I removed all but the required
> plugins
> > > > (the same list of plugins used in my dev environment and specified
in
> my
> > > > launch configuration). This broke my build and the platform could
not
> > > find
> > > > my application as specified in the config.ini file. Anyway, now I'm
> > > > confused and clearly do not understand the configuration
requirements
> > for
> > > > RCP applications in 3.1.1. Do I need to specify additional bundles
in
> > the
> > > > config.ini for RCP applications (i.e. plugin which represents the
> > primary
> > > > feature, all of them, etc.)??
> > > >
> > > > As a reminder, all of this was functional in 3.01 and through 3.1
M6.
> > > >
> > > > Here is how the application directory is structured:
> > > >
> > > > INSTALL_LOC/
> > > > startup.jar
> > > > eclipse.ini
> > > > eclipse.exe
> > > > .eclipseproduct
> > > > /workspace
> > > > /plugins
> > > > ...
> > > > /features
> > > > feature1(required eclipse plugins)
> > > > feature.xml
> > > > feature2(our plugins)
> > > > feature.xml
> > > > /configuration
> > > > config.ini
> > > >
> > > > The config.ini contains:
> > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > on
> > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > org.eclipse.update.configurator@3:start
> > > >
> > > > This is the list of required eclipse plugins that our RCP
application
> > > > depends on:
> > > >
> > > > id="org.apache.ant"
> > > > id="org.apache.lucene"
> > > > id="org.eclipse.compare"
> > > > id="org.eclipse.core.commands"
> > > > id="org.eclipse.core.expressions"
> > > > id="org.eclipse.core.filebuffers"
> > > > id="org.eclipse.core.resources"
> > > > id="org.eclipse.core.resources.compatibility"
> > > > id="org.eclipse.core.resources.win32"
> > > > id="org.eclipse.core.runtime"
> > > > id="org.eclipse.core.runtime.compatibility"
> > > > id="org.eclipse.draw2d"
> > > > id="org.eclipse.emf"
> > > > id="org.eclipse.emf.common"
> > > > id="org.eclipse.emf.common.ui"
> > > > id="org.eclipse.emf.ecore"
> > > > id="org.eclipse.emf.ecore.xmi"
> > > > id="org.eclipse.emf.edit"
> > > > id="org.eclipse.emf.edit.ui"
> > > > id="org.eclipse.gef"
> > > > id="org.eclipse.help"
> > > > id="org.eclipse.help.appserver"
> > > > id="org.eclipse.help.base"
> > > > id="org.eclipse.help.ui"
> > > > id="org.eclipse.help.webapp"
> > > > id="org.eclipse.jface"
> > > > id="org.eclipse.jface.text"
> > > > id="org.eclipse.osgi"
> > > > id="org.eclipse.pde.runtime"
> > > > id="org.eclipse.swt"
> > > > id="org.eclipse.swt.win32.win32.x86"
> > > > id="org.eclipse.team.core"
> > > > id="org.eclipse.team.ui"
> > > > id="org.eclipse.text"
> > > > id="org.eclipse.tomcat"
> > > > id="org.eclipse.ui"
> > > > id="org.eclipse.ui.cheatsheets"
> > > > id="org.eclipse.ui.editors"
> > > > id="org.eclipse.ui.forms"
> > > > id="org.eclipse.ui.ide"
> > > > id="org.eclipse.ui.intro"
> > > > id="org.eclipse.ui.views"
> > > > id="org.eclipse.ui.win32"
> > > > id="org.eclipse.ui.workbench"
> > > > id="org.eclipse.ui.workbench.compatibility"
> > > > id="org.eclipse.ui.workbench.texteditor"
> > > > id="org.eclipse.update.configurator"
> > > > id="org.eclipse.update.core"
> > > > id="org.eclipse.update.core.win32"
> > > > id="org.eclipse.update.scheduler"
> > > > id="org.eclipse.update.ui"
> > > > id="org.junit"
> > > >
> > > > thanks in advance
> > > >
> > > > Paul
> > > >
> > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > > news:djc1ju$lk2$1@news.eclipse.org...
> > > > > yes. That is the standard osgi.bundles list for Eclipse. The
> runtime
> > > > gives
> > > > > you the registry etc and the update.configurator installs all the
> rest
> > > of
> > > > > the bundles.
> > > > >
> > > > > Jeff
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj97vt$8a9$1@news.eclipse.org...
> > > > > > This worked however...
> > > > > >
> > > > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > > > org.eclipse.update.configurator@3:start
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dj8foc$7j1$1@news.eclipse.org...
> > > > > > > I tried add the following to config.ini but still got the same
> > > error:
> > > > > > >
> > > > > > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > > > > > org.eclipse.core.runtime
> > > > > > >
> > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > > > > > Thanks Jeff,
> > > > > > > > I usually assume user error or configuration rather than a
> bug.
> > > For
> > > > > > this
> > > > > > > > particular issue, I assumed something configuration related
as
> > > this
> > > > > > worked
> > > > > > > > fine for our 3.0x and 3.1M builds. This problem arose with
> the
> > > > > > migration
> > > > > > > > from 3.1M6 to 3.1.1.
> > > > > > > >
> > > > > > > > We do have a product and application defined and our
> > > > > > > > INSTALL/configuration/config.ini contains the following
> entries
> > > (we
> > > > > have
> > > > > > > > never specified the osgi.bundles parameter):
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > > > > > on
> > > > > > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > > > > >
> > > > > > > > The INSTALL/features directory contains two features both of
> > which
> > > > > have
> > > > > > a
> > > > > > > > feature.xml:
> > > > > > > >
> > > > > > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > > > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > > > > > >
> > > > > > > > The INSTALL/plugins directory now contains all IDE and
> > proprietary
> > > > > > plugins
> > > > > > > > (a result of trying to debug the problem)
> > > > > > > >
> > > > > > > > As for the launcher, the INSTALL directory contains what
we've
> > > used
> > > > > > > > previously:
> > > > > > > >
> > > > > > > > eclipse.exe
> > > > > > > > startup.jar
> > > > > > > > .eclipseproduct
> > > > > > > >
> > > > > > > > And our startup parameters are also how they've been
> previously:
> > > > > > > >
> > > > > > > > "C:\Program
> > > > > > >
Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > > > > > >
> > > > > > > > So it sounds like we need to update the config.ini with at
> least
> > > one
> > > > > > > bundle,
> > > > > > > > which one(s)?
> > > > > > > >
> > > > > > > > osgi.bundles =??
> > > > > > > >
> > > > > > > > Paul
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in
> message
> > > > > > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > > > > > A couple things.
> > > > > > > > >
> > > > > > > > > - Bugzilla is more effective for this kind of issue
> > > > > > > > > - The application service is registered by the runtime
> plugin.
> > > I
> > > > > > > suspect
> > > > > > > > > that you are not installing/starting the runtime. It
should
> > be
> > > > > listed
> > > > > > > on
> > > > > > > > > the osgi.bundles list in the config.ini or on the command
as
> > > a -D
> > > > vm
> > > > > > > arg.
> > > > > > > > > - when you export the features, what are you doing for a
> > > launcher,
> > > > > > > > > startup.jar, config.ini etc. You should consider defining
a
> > > > PRODUCT
> > > > > > and
> > > > > > > > > exporting the product and then packaging that up.
> > > > > > > > >
> > > > > > > > > Jeff
> > > > > > > > >
> > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> message
> > > > > > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > > > > > Can anyone shed any light on this?
> > > > > > > > > >
> > > > > > > > > > thx
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> > message
> > > > > > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > > > > > FYI, I use the feature export functionality of eclipse
> so
> > > that
> > > > > all
> > > > > > > > > > plugins,
> > > > > > > > > > > both eclipse and ours, are moved into a staging area
for
> > the
> > > > > > > > application
> > > > > > > > > > > packaging step whereby I run a script which builds a
> > > > > > self-extracting
> > > > > > > > > > > executable. So I'm using the same plugins that are
used
> > in
> > > my
> > > > > > > > > functional
> > > > > > > > > > > development environment. I've been hoping that
> something
> > is
> > > > > > > "shoddy"
> > > > > > > > > > > somewhere but I still don't understand what the source
> of
> > > this
> > > > > > error
> > > > > > > > is.
> > > > > > > > > > > I've stepped through the code in the dev environment
but
> > I'm
> > > > not
> > > > > > > > > > connecting
> > > > > > > > > > > the dots as to what circumstances will cause this to
> fail
> > > > > > > > > > > (ParameterizedRunnable returns null):
> > > > > > > > > > >
> > > > > > > > > > > EclipseStarter.java
> > > > > > > > > > >
> > > > > > > > > > > public static Object run(Object argument) throws
> > Exception
> > > {
> > > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > > Profile.logEnter("EclipseStarter.run(Object)()",
> null);
> > > > > > > > //$NON-NLS-1$
> > > > > > > > > > > if (!running)
> > > > > > > > > > > throw new
> > > > > > > > > > >
> > > > > > >
> > > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > > > > > // if we are just initializing, do not run the
> > application
> > > > > just
> > > > > > > > > return.
> > > > > > > > > > > if (initialize)
> > > > > > > > > > > return new Integer(0);
> > > > > > > > > > > initializeApplicationTracker();
> > > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > > Profile.logTime("EclipseStarter.run(Object)()",
> > > "applicaton
> > > > > > > tracker
> > > > > > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > > > > > (ParameterizedRunnable)
> > > > > > > > > > > applicationTracker.getService();
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> > > message
> > > > > > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
> > > > application
> > > > > > will
> > > > > > > > not
> > > > > > > > > > run
> > > > > > > > > > > > as a standalone application (but works fine as a
> launch
> > > > > > > > configuration
> > > > > > > > > > from
> > > > > > > > > > > > the IDE).
> > > > > > > > > > > > I'm guessing this is something obvious but I can't
> seem
> > to
> > > > > find
> > > > > > > it.
> > > > > > > > > > This
> > > > > > > > > > > > occurs
> > > > > > > > > > > > whether I try to point to an existing workspace or
> not.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > > > > > !MESSAGE Application error
> > > > > > > > > > > > !STACK 1
> > > > > > > > > > > > java.lang.IllegalStateException: Unable to acquire
> > > > application
> > > > > > > > > service.
> > > > > > > > > > > > at
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > > > > > at
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > > > > > at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > > > Method)
> > > > > > > > > > > > at
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > > > > Source)
> > > > > > > > > > > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > > > > > Source)
> > > > > > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > > > > > at
> > > > > > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > > > > > at
> > org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > > > > > at
org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > > > > > at
org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: RCP App Fails on startup: IllegalStateException [message #52392 is a reply to message #52126] |
Thu, 03 November 2005 21:44 |
paul wuethrich
Messages: 128
Registered: July 2009 |
Senior Member |
|
|
Resolved!
As expected, it was configuration. A dependent emf plugin wasn't getting
exported the build location. The confusing part was that the error messages
referred to a bogus plugin version "0.0.0":
!ENTRY org.eclipse.osgi 2005-11-03 12:06:28.579
!MESSAGE Bundle
update@plugins/com.eyeris.eyeprofit.ui.core.model.editor_1.0.9/ [13] was not
resolved.
!SUBENTRY 1 org.eclipse.osgi 2005-11-03 12:06:28.579
!MESSAGE Missing required bundle
com.eyeris.eyeprofit.ui.project.validator_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2005-11-03 12:06:28.579
!MESSAGE Missing required bundle
com.eyeris.eyeprofit.ui.datasource.model.editor_0.0.0.
Thanks alot for your help.
p
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:dk9bgo$fqr$1@news.eclipse.org...
> Paul, what I am suggesting is a config.ini that looks like
>
> eclipse.product=<your product id here>
> osgi.bundles=org.eclipse.core.runtime@2:start,
> org.eclipse.update.configurator@3:start
>
> The product extension should then identify the application to use when
> running that product.
>
> Jeff
>
>
> "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> news:dk89t0$6fl$1@news.eclipse.org...
> > Thanks Jeff, I'll take a look.
> >
> > Also, it sounds like you're saying that an RCP application need only
> define
> > osgi.bundles=org.eclipse.core.runtime@2:start,
> > org.eclipse.update.configurator@3:start
> > provided eclipse.product and eclipse.application are defined and that
the
> > remaining configuration is "correct"?
> >
> > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > news:djpd4e$8qk$1@news.eclipse.org...
> > > Paul,
> > > The structure looks good. I can't think of anything that changed
after
> > M6.
> > > The error you were getting in the orginal post is very low-level and
is
> > > indicating to me that the runtime plugin is not starting. Try the
> > following
> > > to investigate further.
> > > - put -console -noexit on the command line. This should give you an
> OSGi
> > > console and stop Equionx from exiting
> > > - at the osgi> prompt, type ss (short status)
> > > - you should see a list of bundles.
> > > - look at the list carefully. You want everything to be in RESOLVED
or
> > > ACTIVE state. plugins that are in INSTALLED state are potential
> problems.
> > > - for any bundle that is listed as INSTALLED, get its number and type
> diag
> > > NN where NN is the bundle id number.
> > > - this should report the reasons why it is not RESOLVED or ACTIVE.
> > > - if you find some problems, try to fix them.
> > >
> > > The only other thing I can think of is that the product definition
> should
> > > specify the application. Please ensure that hte product extension has
> the
> > > correct application id.
> > >
> > > For now that is all I can think of.
> > >
> > > Jeff
> > >
> > >
> > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > news:djo6ed$oab$1@news.eclipse.org...
> > > > Jeff,
> > > > I thought this had resolved my build issues but I had forgotten that
> > > during
> > > > the troubleshooting process I had copied all of the Eclipse plugins
> into
> > > the
> > > > build area that is used as the source for building an installable
> image.
> > > > Anyway, upon realization of that, I removed all but the required
> plugins
> > > > (the same list of plugins used in my dev environment and specified
in
> my
> > > > launch configuration). This broke my build and the platform could
not
> > > find
> > > > my application as specified in the config.ini file. Anyway, now I'm
> > > > confused and clearly do not understand the configuration
requirements
> > for
> > > > RCP applications in 3.1.1. Do I need to specify additional bundles
in
> > the
> > > > config.ini for RCP applications (i.e. plugin which represents the
> > primary
> > > > feature, all of them, etc.)??
> > > >
> > > > As a reminder, all of this was functional in 3.01 and through 3.1
M6.
> > > >
> > > > Here is how the application directory is structured:
> > > >
> > > > INSTALL_LOC/
> > > > startup.jar
> > > > eclipse.ini
> > > > eclipse.exe
> > > > .eclipseproduct
> > > > /workspace
> > > > /plugins
> > > > ...
> > > > /features
> > > > feature1(required eclipse plugins)
> > > > feature.xml
> > > > feature2(our plugins)
> > > > feature.xml
> > > > /configuration
> > > > config.ini
> > > >
> > > > The config.ini contains:
> > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > on
> > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > org.eclipse.update.configurator@3:start
> > > >
> > > > This is the list of required eclipse plugins that our RCP
application
> > > > depends on:
> > > >
> > > > id="org.apache.ant"
> > > > id="org.apache.lucene"
> > > > id="org.eclipse.compare"
> > > > id="org.eclipse.core.commands"
> > > > id="org.eclipse.core.expressions"
> > > > id="org.eclipse.core.filebuffers"
> > > > id="org.eclipse.core.resources"
> > > > id="org.eclipse.core.resources.compatibility"
> > > > id="org.eclipse.core.resources.win32"
> > > > id="org.eclipse.core.runtime"
> > > > id="org.eclipse.core.runtime.compatibility"
> > > > id="org.eclipse.draw2d"
> > > > id="org.eclipse.emf"
> > > > id="org.eclipse.emf.common"
> > > > id="org.eclipse.emf.common.ui"
> > > > id="org.eclipse.emf.ecore"
> > > > id="org.eclipse.emf.ecore.xmi"
> > > > id="org.eclipse.emf.edit"
> > > > id="org.eclipse.emf.edit.ui"
> > > > id="org.eclipse.gef"
> > > > id="org.eclipse.help"
> > > > id="org.eclipse.help.appserver"
> > > > id="org.eclipse.help.base"
> > > > id="org.eclipse.help.ui"
> > > > id="org.eclipse.help.webapp"
> > > > id="org.eclipse.jface"
> > > > id="org.eclipse.jface.text"
> > > > id="org.eclipse.osgi"
> > > > id="org.eclipse.pde.runtime"
> > > > id="org.eclipse.swt"
> > > > id="org.eclipse.swt.win32.win32.x86"
> > > > id="org.eclipse.team.core"
> > > > id="org.eclipse.team.ui"
> > > > id="org.eclipse.text"
> > > > id="org.eclipse.tomcat"
> > > > id="org.eclipse.ui"
> > > > id="org.eclipse.ui.cheatsheets"
> > > > id="org.eclipse.ui.editors"
> > > > id="org.eclipse.ui.forms"
> > > > id="org.eclipse.ui.ide"
> > > > id="org.eclipse.ui.intro"
> > > > id="org.eclipse.ui.views"
> > > > id="org.eclipse.ui.win32"
> > > > id="org.eclipse.ui.workbench"
> > > > id="org.eclipse.ui.workbench.compatibility"
> > > > id="org.eclipse.ui.workbench.texteditor"
> > > > id="org.eclipse.update.configurator"
> > > > id="org.eclipse.update.core"
> > > > id="org.eclipse.update.core.win32"
> > > > id="org.eclipse.update.scheduler"
> > > > id="org.eclipse.update.ui"
> > > > id="org.junit"
> > > >
> > > > thanks in advance
> > > >
> > > > Paul
> > > >
> > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> > > > news:djc1ju$lk2$1@news.eclipse.org...
> > > > > yes. That is the standard osgi.bundles list for Eclipse. The
> runtime
> > > > gives
> > > > > you the registry etc and the update.configurator installs all the
> rest
> > > of
> > > > > the bundles.
> > > > >
> > > > > Jeff
> > > > >
> > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > news:dj97vt$8a9$1@news.eclipse.org...
> > > > > > This worked however...
> > > > > >
> > > > > > osgi.bundles=org.eclipse.core.runtime@2:start,
> > > > > > org.eclipse.update.configurator@3:start
> > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > news:dj8foc$7j1$1@news.eclipse.org...
> > > > > > > I tried add the following to config.ini but still got the same
> > > error:
> > > > > > >
> > > > > > > osgi.bundles=org.eclipse.osgi.services, org.eclipse.osgi.util,
> > > > > > > org.eclipse.core.runtime
> > > > > > >
> > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in message
> > > > > > > news:dj8cj9$2rr$1@news.eclipse.org...
> > > > > > > > Thanks Jeff,
> > > > > > > > I usually assume user error or configuration rather than a
> bug.
> > > For
> > > > > > this
> > > > > > > > particular issue, I assumed something configuration related
as
> > > this
> > > > > > worked
> > > > > > > > fine for our 3.0x and 3.1M builds. This problem arose with
> the
> > > > > > migration
> > > > > > > > from 3.1M6 to 3.1.1.
> > > > > > > >
> > > > > > > > We do have a product and application defined and our
> > > > > > > > INSTALL/configuration/config.ini contains the following
> entries
> > > (we
> > > > > have
> > > > > > > > never specified the osgi.bundles parameter):
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
eclipse.application=com.eyeris.eyeprofit.modelconfig.ui.Mode lConfigApplicati
> > > > > > > > on
> > > > > > > > eclipse.product=com.eyeris.eyeprofit.modelconfig.ui.console
> > > > > > > >
> > > > > > > > The INSTALL/features directory contains two features both of
> > which
> > > > > have
> > > > > > a
> > > > > > > > feature.xml:
> > > > > > > >
> > > > > > > > com.eyeris.eyeprofit.eclipse.base.plugins_1.0.0
> > > > > > > > com.eyeris.eyeprofit.ui.plugins_1.0.0
> > > > > > > >
> > > > > > > > The INSTALL/plugins directory now contains all IDE and
> > proprietary
> > > > > > plugins
> > > > > > > > (a result of trying to debug the problem)
> > > > > > > >
> > > > > > > > As for the launcher, the INSTALL directory contains what
we've
> > > used
> > > > > > > > previously:
> > > > > > > >
> > > > > > > > eclipse.exe
> > > > > > > > startup.jar
> > > > > > > > .eclipseproduct
> > > > > > > >
> > > > > > > > And our startup parameters are also how they've been
> previously:
> > > > > > > >
> > > > > > > > "C:\Program
> > > > > > >
Files\Eyeris\EyeProfit\Integration\eclipse.exe" -vmargs -Xmx480M
> > > > > > > >
> > > > > > > > So it sounds like we need to update the config.ini with at
> least
> > > one
> > > > > > > bundle,
> > > > > > > > which one(s)?
> > > > > > > >
> > > > > > > > osgi.bundles =??
> > > > > > > >
> > > > > > > > Paul
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in
> message
> > > > > > > > news:dj6qii$vm7$1@news.eclipse.org...
> > > > > > > > > A couple things.
> > > > > > > > >
> > > > > > > > > - Bugzilla is more effective for this kind of issue
> > > > > > > > > - The application service is registered by the runtime
> plugin.
> > > I
> > > > > > > suspect
> > > > > > > > > that you are not installing/starting the runtime. It
should
> > be
> > > > > listed
> > > > > > > on
> > > > > > > > > the osgi.bundles list in the config.ini or on the command
as
> > > a -D
> > > > vm
> > > > > > > arg.
> > > > > > > > > - when you export the features, what are you doing for a
> > > launcher,
> > > > > > > > > startup.jar, config.ini etc. You should consider defining
a
> > > > PRODUCT
> > > > > > and
> > > > > > > > > exporting the product and then packaging that up.
> > > > > > > > >
> > > > > > > > > Jeff
> > > > > > > > >
> > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> message
> > > > > > > > > news:dj5lut$g94$1@news.eclipse.org...
> > > > > > > > > > Can anyone shed any light on this?
> > > > > > > > > >
> > > > > > > > > > thx
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> > message
> > > > > > > > > > news:dj0td9$fb2$1@news.eclipse.org...
> > > > > > > > > > > FYI, I use the feature export functionality of eclipse
> so
> > > that
> > > > > all
> > > > > > > > > > plugins,
> > > > > > > > > > > both eclipse and ours, are moved into a staging area
for
> > the
> > > > > > > > application
> > > > > > > > > > > packaging step whereby I run a script which builds a
> > > > > > self-extracting
> > > > > > > > > > > executable. So I'm using the same plugins that are
used
> > in
> > > my
> > > > > > > > > functional
> > > > > > > > > > > development environment. I've been hoping that
> something
> > is
> > > > > > > "shoddy"
> > > > > > > > > > > somewhere but I still don't understand what the source
> of
> > > this
> > > > > > error
> > > > > > > > is.
> > > > > > > > > > > I've stepped through the code in the dev environment
but
> > I'm
> > > > not
> > > > > > > > > > connecting
> > > > > > > > > > > the dots as to what circumstances will cause this to
> fail
> > > > > > > > > > > (ParameterizedRunnable returns null):
> > > > > > > > > > >
> > > > > > > > > > > EclipseStarter.java
> > > > > > > > > > >
> > > > > > > > > > > public static Object run(Object argument) throws
> > Exception
> > > {
> > > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > > Profile.logEnter("EclipseStarter.run(Object)()",
> null);
> > > > > > > > //$NON-NLS-1$
> > > > > > > > > > > if (!running)
> > > > > > > > > > > throw new
> > > > > > > > > > >
> > > > > > >
> > > IllegalStateException(EclipseAdaptorMsg.ECLIPSE_STARTUP_NOT_ RUNNING);
> > > > > > > > > > > // if we are just initializing, do not run the
> > application
> > > > > just
> > > > > > > > > return.
> > > > > > > > > > > if (initialize)
> > > > > > > > > > > return new Integer(0);
> > > > > > > > > > > initializeApplicationTracker();
> > > > > > > > > > > if (Profile.PROFILE && Profile.STARTUP)
> > > > > > > > > > > Profile.logTime("EclipseStarter.run(Object)()",
> > > "applicaton
> > > > > > > tracker
> > > > > > > > > > > initialized"); //$NON-NLS-1$ //$NON-NLS-2$
> > > > > > > > > > > LINE 364>>>>ParameterizedRunnable application =
> > > > > > > > > (ParameterizedRunnable)
> > > > > > > > > > > applicationTracker.getService();
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Paul Wuethrich" <paul.wuethrich@eye-ris.com> wrote in
> > > message
> > > > > > > > > > > news:dioesh$ceb$1@news.eclipse.org...
> > > > > > > > > > > > We just migrated from 3.1 M6 to 3.1.1 and our RCP
> > > > application
> > > > > > will
> > > > > > > > not
> > > > > > > > > > run
> > > > > > > > > > > > as a standalone application (but works fine as a
> launch
> > > > > > > > configuration
> > > > > > > > > > from
> > > > > > > > > > > > the IDE).
> > > > > > > > > > > > I'm guessing this is something obvious but I can't
> seem
> > to
> > > > > find
> > > > > > > it.
> > > > > > > > > > This
> > > > > > > > > > > > occurs
> > > > > > > > > > > > whether I try to point to an existing workspace or
> not.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > !ENTRY org.eclipse.osgi 2005-10-13 09:42:50.753
> > > > > > > > > > > > !MESSAGE Application error
> > > > > > > > > > > > !STACK 1
> > > > > > > > > > > > java.lang.IllegalStateException: Unable to acquire
> > > > application
> > > > > > > > > service.
> > > > > > > > > > > > at
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:367)
> > > > > > > > > > > > at
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
> > > > > > > > > > > > at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > > > > Method)
> > > > > > > > > > > > at
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> > > > > Source)
> > > > > > > > > > > > at
> > > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> > > > > > > Source)
> > > > > > > > > > > > at java.lang.reflect.Method.invoke(Unknown Source)
> > > > > > > > > > > > at
> > > > > > org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
> > > > > > > > > > > > at
> > org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> > > > > > > > > > > > at
org.eclipse.core.launcher.Main.run(Main.java:973)
> > > > > > > > > > > > at
org.eclipse.core.launcher.Main.main(Main.java:948)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 20:07:40 GMT 2024
Powered by FUDForum. Page generated in 0.06569 seconds |
] 
Search
Help
Register
Login
Home
