Home » Archived » B3 » Problems with DS on startup
Problems with DS on startup [message #517462] |
Sun, 28 February 2010 11:42 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
Hi all,
I have a strange problem with launching our headless b3 application. Btw., headless buckminster suffers from the same error which is not fatal but puts an ugly error message in the error log.
The error is:
!ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
It happens only the first time after installation. Following starts are ok.
I googled out some discussions about this but to be frank, it did not help me.
Some more details:
- even though this error appears in the log, all bundles finally resolve/start successfully
- I can't find any broken constraints in the runtime, all required bundles/packages are available
If I edit the config.ini file and replace
"osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
with
"osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
everything works fine from the very beginning (even after fresh installation).
Does anyone know how to fix this problem without a need to provide customized config.ini?
Thanks
Filip
|
|
|
Re: Problems with DS on startup [message #517467 is a reply to message #517462] |
Sun, 28 February 2010 12:31 |
|
Hi Filip,
I suggest you start a discussion about this in a bugzilla (rt/equinox).
- thomas
On 02/28/2010 12:42 PM, Filip Hrbek wrote:
> Hi all,
>
> I have a strange problem with launching our headless b3 application.
> Btw., headless buckminster suffers from the same error which is not
> fatal but puts an ugly error message in the error log.
>
> The error is:
>
> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
> !MESSAGE
> !STACK 0
> org.osgi.framework.BundleException: The bundle could not be resolved.
> Reason: Missing Constraint: Import-Package:
> org.eclipse.equinox.internal.util.event; version="1.0.0"
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>
>
>
> It happens only the first time after installation. Following starts are ok.
>
> I googled out some discussions about this but to be frank, it did not
> help me.
>
> Some more details:
>
> - even though this error appears in the log, all bundles finally
> resolve/start successfully
> - I can't find any broken constraints in the runtime, all required
> bundles/packages are available
>
> If I edit the config.ini file and replace
>
> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>
>
> with
>
> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>
>
> everything works fine from the very beginning (even after fresh
> installation).
>
>
> Does anyone know how to fix this problem without a need to provide
> customized config.ini?
>
> Thanks
>
> Filip
|
|
|
Re: Problems with DS on startup [message #517758 is a reply to message #517467] |
Mon, 01 March 2010 23:04 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
I found a solution - I put following bundles in the product configuration table:
org.eclipse.equinox.ds, level 1, autostart
org.eclipse.equinox.util, level 1, autostart
org.eclipse.osgi.services, level 1, autostart
This table generates org.eclipse.equinox.simpleconfigurator/bundles.info upon product installation with proper bundle startup settings.
I suggest the same is done for buckminster.
Filip
Thomas Hallgren wrote:
> Hi Filip,
> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>
> - thomas
>
> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>> Hi all,
>>
>> I have a strange problem with launching our headless b3 application.
>> Btw., headless buckminster suffers from the same error which is not
>> fatal but puts an ugly error message in the error log.
>>
>> The error is:
>>
>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>> !MESSAGE
>> !STACK 0
>> org.osgi.framework.BundleException: The bundle could not be resolved.
>> Reason: Missing Constraint: Import-Package:
>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>
>>
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>
>>
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>
>>
>>
>>
>> It happens only the first time after installation. Following starts
>> are ok.
>>
>> I googled out some discussions about this but to be frank, it did not
>> help me.
>>
>> Some more details:
>>
>> - even though this error appears in the log, all bundles finally
>> resolve/start successfully
>> - I can't find any broken constraints in the runtime, all required
>> bundles/packages are available
>>
>> If I edit the config.ini file and replace
>>
>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>
>>
>>
>> with
>>
>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>
>>
>>
>> everything works fine from the very beginning (even after fresh
>> installation).
>>
>>
>> Does anyone know how to fix this problem without a need to provide
>> customized config.ini?
>>
>> Thanks
>>
>> Filip
>
|
|
|
Re: Problems with DS on startup [message #517766 is a reply to message #517758] |
Mon, 01 March 2010 23:36 |
|
Ok, good workaround, but the real problem seems to be that the equinox publisher doesn't generate the correct default
start-levels. You shouldn't need to add things like that just to make it work.
- thomas
On 03/02/2010 12:04 AM, Filip Hrbek wrote:
> I found a solution - I put following bundles in the product
> configuration table:
>
> org.eclipse.equinox.ds, level 1, autostart
> org.eclipse.equinox.util, level 1, autostart
> org.eclipse.osgi.services, level 1, autostart
>
> This table generates org.eclipse.equinox.simpleconfigurator/bundles.info
> upon product installation with proper bundle startup settings.
>
> I suggest the same is done for buckminster.
>
> Filip
>
> Thomas Hallgren wrote:
>> Hi Filip,
>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>
>> - thomas
>>
>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>> Hi all,
>>>
>>> I have a strange problem with launching our headless b3 application.
>>> Btw., headless buckminster suffers from the same error which is not
>>> fatal but puts an ugly error message in the error log.
>>>
>>> The error is:
>>>
>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>> Reason: Missing Constraint: Import-Package:
>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>
>>>
>>>
>>>
>>> It happens only the first time after installation. Following starts
>>> are ok.
>>>
>>> I googled out some discussions about this but to be frank, it did not
>>> help me.
>>>
>>> Some more details:
>>>
>>> - even though this error appears in the log, all bundles finally
>>> resolve/start successfully
>>> - I can't find any broken constraints in the runtime, all required
>>> bundles/packages are available
>>>
>>> If I edit the config.ini file and replace
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> with
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> everything works fine from the very beginning (even after fresh
>>> installation).
>>>
>>>
>>> Does anyone know how to fix this problem without a need to provide
>>> customized config.ini?
>>>
>>> Thanks
>>>
>>> Filip
>>
|
|
|
Re: Problems with DS on startup [message #517844 is a reply to message #517758] |
Tue, 02 March 2010 10:10 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
Sorry, it does not work (my fault, bad testing).
Even though the bundles.info looks good, it does not solve the problem.
I am going to report this at equinox.
Filip
Filip Hrbek wrote:
> I found a solution - I put following bundles in the product
> configuration table:
>
> org.eclipse.equinox.ds, level 1, autostart
> org.eclipse.equinox.util, level 1, autostart
> org.eclipse.osgi.services, level 1, autostart
>
> This table generates org.eclipse.equinox.simpleconfigurator/bundles.info
> upon product installation with proper bundle startup settings.
>
> I suggest the same is done for buckminster.
>
> Filip
>
> Thomas Hallgren wrote:
>> Hi Filip,
>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>
>> - thomas
>>
>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>> Hi all,
>>>
>>> I have a strange problem with launching our headless b3 application.
>>> Btw., headless buckminster suffers from the same error which is not
>>> fatal but puts an ugly error message in the error log.
>>>
>>> The error is:
>>>
>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>> Reason: Missing Constraint: Import-Package:
>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>
>>>
>>>
>>>
>>> It happens only the first time after installation. Following starts
>>> are ok.
>>>
>>> I googled out some discussions about this but to be frank, it did not
>>> help me.
>>>
>>> Some more details:
>>>
>>> - even though this error appears in the log, all bundles finally
>>> resolve/start successfully
>>> - I can't find any broken constraints in the runtime, all required
>>> bundles/packages are available
>>>
>>> If I edit the config.ini file and replace
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> with
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> everything works fine from the very beginning (even after fresh
>>> installation).
>>>
>>>
>>> Does anyone know how to fix this problem without a need to provide
>>> customized config.ini?
>>>
>>> Thanks
>>>
>>> Filip
>>
|
|
|
Re: Problems with DS on startup [message #517868 is a reply to message #517844] |
Tue, 02 March 2010 11:50 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
Logged an issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304340
Filip Hrbek wrote:
> Sorry, it does not work (my fault, bad testing).
>
> Even though the bundles.info looks good, it does not solve the problem.
>
> I am going to report this at equinox.
>
> Filip
>
>
> Filip Hrbek wrote:
>> I found a solution - I put following bundles in the product
>> configuration table:
>>
>> org.eclipse.equinox.ds, level 1, autostart
>> org.eclipse.equinox.util, level 1, autostart
>> org.eclipse.osgi.services, level 1, autostart
>>
>> This table generates
>> org.eclipse.equinox.simpleconfigurator/bundles.info upon product
>> installation with proper bundle startup settings.
>>
>> I suggest the same is done for buckminster.
>>
>> Filip
>>
>> Thomas Hallgren wrote:
>>> Hi Filip,
>>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>>
>>> - thomas
>>>
>>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>>> Hi all,
>>>>
>>>> I have a strange problem with launching our headless b3 application.
>>>> Btw., headless buckminster suffers from the same error which is not
>>>> fatal but puts an ugly error message in the error log.
>>>>
>>>> The error is:
>>>>
>>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>>> !MESSAGE
>>>> !STACK 0
>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>> Reason: Missing Constraint: Import-Package:
>>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>>
>>>>
>>>>
>>>>
>>>> It happens only the first time after installation. Following starts
>>>> are ok.
>>>>
>>>> I googled out some discussions about this but to be frank, it did not
>>>> help me.
>>>>
>>>> Some more details:
>>>>
>>>> - even though this error appears in the log, all bundles finally
>>>> resolve/start successfully
>>>> - I can't find any broken constraints in the runtime, all required
>>>> bundles/packages are available
>>>>
>>>> If I edit the config.ini file and replace
>>>>
>>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>>
>>>>
>>>>
>>>> with
>>>>
>>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>>
>>>>
>>>>
>>>> everything works fine from the very beginning (even after fresh
>>>> installation).
>>>>
>>>>
>>>> Does anyone know how to fix this problem without a need to provide
>>>> customized config.ini?
>>>>
>>>> Thanks
>>>>
>>>> Filip
>>>
|
|
|
Re: Problems with DS on startup [message #600293 is a reply to message #517462] |
Sun, 28 February 2010 12:31 |
|
Hi Filip,
I suggest you start a discussion about this in a bugzilla (rt/equinox).
- thomas
On 02/28/2010 12:42 PM, Filip Hrbek wrote:
> Hi all,
>
> I have a strange problem with launching our headless b3 application.
> Btw., headless buckminster suffers from the same error which is not
> fatal but puts an ugly error message in the error log.
>
> The error is:
>
> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
> !MESSAGE
> !STACK 0
> org.osgi.framework.BundleException: The bundle could not be resolved.
> Reason: Missing Constraint: Import-Package:
> org.eclipse.equinox.internal.util.event; version="1.0.0"
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>
>
>
> It happens only the first time after installation. Following starts are ok.
>
> I googled out some discussions about this but to be frank, it did not
> help me.
>
> Some more details:
>
> - even though this error appears in the log, all bundles finally
> resolve/start successfully
> - I can't find any broken constraints in the runtime, all required
> bundles/packages are available
>
> If I edit the config.ini file and replace
>
> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>
>
> with
>
> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>
>
> everything works fine from the very beginning (even after fresh
> installation).
>
>
> Does anyone know how to fix this problem without a need to provide
> customized config.ini?
>
> Thanks
>
> Filip
|
|
|
Re: Problems with DS on startup [message #600306 is a reply to message #517467] |
Mon, 01 March 2010 23:04 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
I found a solution - I put following bundles in the product configuration table:
org.eclipse.equinox.ds, level 1, autostart
org.eclipse.equinox.util, level 1, autostart
org.eclipse.osgi.services, level 1, autostart
This table generates org.eclipse.equinox.simpleconfigurator/bundles.info upon product installation with proper bundle startup settings.
I suggest the same is done for buckminster.
Filip
Thomas Hallgren wrote:
> Hi Filip,
> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>
> - thomas
>
> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>> Hi all,
>>
>> I have a strange problem with launching our headless b3 application.
>> Btw., headless buckminster suffers from the same error which is not
>> fatal but puts an ugly error message in the error log.
>>
>> The error is:
>>
>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>> !MESSAGE
>> !STACK 0
>> org.osgi.framework.BundleException: The bundle could not be resolved.
>> Reason: Missing Constraint: Import-Package:
>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>
>>
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>
>>
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>
>>
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>
>>
>>
>>
>> It happens only the first time after installation. Following starts
>> are ok.
>>
>> I googled out some discussions about this but to be frank, it did not
>> help me.
>>
>> Some more details:
>>
>> - even though this error appears in the log, all bundles finally
>> resolve/start successfully
>> - I can't find any broken constraints in the runtime, all required
>> bundles/packages are available
>>
>> If I edit the config.ini file and replace
>>
>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>
>>
>>
>> with
>>
>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>
>>
>>
>> everything works fine from the very beginning (even after fresh
>> installation).
>>
>>
>> Does anyone know how to fix this problem without a need to provide
>> customized config.ini?
>>
>> Thanks
>>
>> Filip
>
|
|
|
Re: Problems with DS on startup [message #602089 is a reply to message #517758] |
Mon, 01 March 2010 23:36 |
|
Ok, good workaround, but the real problem seems to be that the equinox publisher doesn't generate the correct default
start-levels. You shouldn't need to add things like that just to make it work.
- thomas
On 03/02/2010 12:04 AM, Filip Hrbek wrote:
> I found a solution - I put following bundles in the product
> configuration table:
>
> org.eclipse.equinox.ds, level 1, autostart
> org.eclipse.equinox.util, level 1, autostart
> org.eclipse.osgi.services, level 1, autostart
>
> This table generates org.eclipse.equinox.simpleconfigurator/bundles.info
> upon product installation with proper bundle startup settings.
>
> I suggest the same is done for buckminster.
>
> Filip
>
> Thomas Hallgren wrote:
>> Hi Filip,
>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>
>> - thomas
>>
>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>> Hi all,
>>>
>>> I have a strange problem with launching our headless b3 application.
>>> Btw., headless buckminster suffers from the same error which is not
>>> fatal but puts an ugly error message in the error log.
>>>
>>> The error is:
>>>
>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>> Reason: Missing Constraint: Import-Package:
>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>
>>>
>>>
>>>
>>> It happens only the first time after installation. Following starts
>>> are ok.
>>>
>>> I googled out some discussions about this but to be frank, it did not
>>> help me.
>>>
>>> Some more details:
>>>
>>> - even though this error appears in the log, all bundles finally
>>> resolve/start successfully
>>> - I can't find any broken constraints in the runtime, all required
>>> bundles/packages are available
>>>
>>> If I edit the config.ini file and replace
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> with
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> everything works fine from the very beginning (even after fresh
>>> installation).
>>>
>>>
>>> Does anyone know how to fix this problem without a need to provide
>>> customized config.ini?
>>>
>>> Thanks
>>>
>>> Filip
>>
|
|
|
Re: Problems with DS on startup [message #602110 is a reply to message #517758] |
Tue, 02 March 2010 10:10 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
Sorry, it does not work (my fault, bad testing).
Even though the bundles.info looks good, it does not solve the problem.
I am going to report this at equinox.
Filip
Filip Hrbek wrote:
> I found a solution - I put following bundles in the product
> configuration table:
>
> org.eclipse.equinox.ds, level 1, autostart
> org.eclipse.equinox.util, level 1, autostart
> org.eclipse.osgi.services, level 1, autostart
>
> This table generates org.eclipse.equinox.simpleconfigurator/bundles.info
> upon product installation with proper bundle startup settings.
>
> I suggest the same is done for buckminster.
>
> Filip
>
> Thomas Hallgren wrote:
>> Hi Filip,
>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>
>> - thomas
>>
>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>> Hi all,
>>>
>>> I have a strange problem with launching our headless b3 application.
>>> Btw., headless buckminster suffers from the same error which is not
>>> fatal but puts an ugly error message in the error log.
>>>
>>> The error is:
>>>
>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>> !MESSAGE
>>> !STACK 0
>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>> Reason: Missing Constraint: Import-Package:
>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>
>>>
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>
>>>
>>>
>>>
>>> It happens only the first time after installation. Following starts
>>> are ok.
>>>
>>> I googled out some discussions about this but to be frank, it did not
>>> help me.
>>>
>>> Some more details:
>>>
>>> - even though this error appears in the log, all bundles finally
>>> resolve/start successfully
>>> - I can't find any broken constraints in the runtime, all required
>>> bundles/packages are available
>>>
>>> If I edit the config.ini file and replace
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> with
>>>
>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>
>>>
>>>
>>> everything works fine from the very beginning (even after fresh
>>> installation).
>>>
>>>
>>> Does anyone know how to fix this problem without a need to provide
>>> customized config.ini?
>>>
>>> Thanks
>>>
>>> Filip
>>
|
|
|
Re: Problems with DS on startup [message #602117 is a reply to message #517844] |
Tue, 02 March 2010 11:50 |
Filip Hrbek Messages: 233 Registered: July 2009 |
Senior Member |
|
|
Logged an issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304340
Filip Hrbek wrote:
> Sorry, it does not work (my fault, bad testing).
>
> Even though the bundles.info looks good, it does not solve the problem.
>
> I am going to report this at equinox.
>
> Filip
>
>
> Filip Hrbek wrote:
>> I found a solution - I put following bundles in the product
>> configuration table:
>>
>> org.eclipse.equinox.ds, level 1, autostart
>> org.eclipse.equinox.util, level 1, autostart
>> org.eclipse.osgi.services, level 1, autostart
>>
>> This table generates
>> org.eclipse.equinox.simpleconfigurator/bundles.info upon product
>> installation with proper bundle startup settings.
>>
>> I suggest the same is done for buckminster.
>>
>> Filip
>>
>> Thomas Hallgren wrote:
>>> Hi Filip,
>>> I suggest you start a discussion about this in a bugzilla (rt/equinox).
>>>
>>> - thomas
>>>
>>> On 02/28/2010 12:42 PM, Filip Hrbek wrote:
>>>> Hi all,
>>>>
>>>> I have a strange problem with launching our headless b3 application.
>>>> Btw., headless buckminster suffers from the same error which is not
>>>> fatal but puts an ugly error message in the error log.
>>>>
>>>> The error is:
>>>>
>>>> !ENTRY org.eclipse.equinox.ds 4 0 2010-02-28 12:27:37.724
>>>> !MESSAGE
>>>> !STACK 0
>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>> Reason: Missing Constraint: Import-Package:
>>>> org.eclipse.equinox.internal.util.event; version="1.0.0"
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolverError(AbstractBundle.java:1312)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureException(AbstractBundle.java:1296)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:319)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:369)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1069)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:554)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:461)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:246)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:442)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
>>>>
>>>>
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)
>>>>
>>>>
>>>>
>>>>
>>>> It happens only the first time after installation. Following starts
>>>> are ok.
>>>>
>>>> I googled out some discussions about this but to be frank, it did not
>>>> help me.
>>>>
>>>> Some more details:
>>>>
>>>> - even though this error appears in the log, all bundles finally
>>>> resolve/start successfully
>>>> - I can't find any broken constraints in the runtime, all required
>>>> bundles/packages are available
>>>>
>>>> If I edit the config.ini file and replace
>>>>
>>>> "osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>>
>>>>
>>>>
>>>> with
>>>>
>>>> "osgi.bundles=reference\:file\:org.eclipse.osgi.services_3.2.100.v20100108.jar@1\:start,reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@1\:start,reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100125.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-101 9.jar @1\:start"
>>>>
>>>>
>>>>
>>>> everything works fine from the very beginning (even after fresh
>>>> installation).
>>>>
>>>>
>>>> Does anyone know how to fix this problem without a need to provide
>>>> customized config.ini?
>>>>
>>>> Thanks
>>>>
>>>> Filip
>>>
|
|
|
Goto Forum:
Current Time: Mon Sep 23 14:23:11 GMT 2024
Powered by FUDForum. Page generated in 0.08467 seconds
|