Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse SmartHome » Launch configuration for Smarthome Designer for Windows missing
Launch configuration for Smarthome Designer for Windows missing [message #1736095] Sat, 25 June 2016 16:57 Go to next message
Martin Herbst is currently offline Martin HerbstFriend
Messages: 4
Registered: August 2014
Junior Member
I have installed an Smarthome development environment (with the help of Eclipse Installer) on Windows 10 with JDK 8 64 Bit. Build after installation was fine.
But when I try to execute the Smarthome Designer I have some problems. The targetplatform project contains only a launch configuration for Mac. I modified it by adding the correct SWT plugin for Windows 64 Bit, but I am not able to start the designer.
The console shows the following error messages. The last message about the invalid thread access is probably caused by the other errors. Need some help to get a working launch configuration.

!SESSION 2016-06-25 18:46:52.352 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_92
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.smarthome.designer.core.product
Command-line arguments: -product org.eclipse.smarthome.designer.core.product -data E:\Develop\smarthome-master\ws/../smarthome-designer -dev file:E:/Develop/smarthome-master/ws/.metadata/.plugins/org.eclipse.pde.core/SmartHome Designer (Mac)/dev.properties -os win32 -ws win32 -consoleLog

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.021
!MESSAGE Could not bind a reference of component ConfigDescriptionRegistry. The reference is: Reference[name = ConfigOptionProvider, interface = org.eclipse.smarthome.config.core.ConfigOptionProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addConfigOptionProvider, unbind = removeConfigOptionProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.022
!MESSAGE Could not bind a reference of component ConfigDescriptionRegistry. The reference is: Reference[name = ConfigDescriptionProvider, interface = org.eclipse.smarthome.config.core.ConfigDescriptionProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addConfigDescriptionProvider, unbind = removeConfigDescriptionProvider]
18:46:53.520 [Start Level: Equinox Container: 10fd476b-f43a-0016-1715-baae0aad52d3] DEBUG o.e.s.core.internal.PortableBase64 - PortableBase64 class is running on JavaSE >=8
18:46:53.522 [Start Level: Equinox Container: 10fd476b-f43a-0016-1715-baae0aad52d3] DEBUG o.e.s.core.internal.CoreActivator - Core bundle has been started.

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.527
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.binding.BindingInfoRegistry. The reference is: Reference[name = BindingInfoProvider, interface = org.eclipse.smarthome.core.binding.BindingInfoProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addBindingInfoProvider, unbind = removeBindingInfoProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.546
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.itemregistry. The reference is: Reference[name = ItemProvider, interface = org.eclipse.smarthome.core.items.ItemProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addProvider, unbind = removeProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.547
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.itemregistry. The reference is: Reference[name = ManagedItemProvider, interface = org.eclipse.smarthome.core.items.ManagedItemProvider, policy = dynamic, cardinality = 0..1, target = null, bind = setManagedProvider, unbind = removeManagedProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.547
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.itemregistry. The reference is: Reference[name = EventPublisher, interface = org.eclipse.smarthome.core.events.EventPublisher, policy = dynamic, cardinality = 0..1, target = null, bind = setEventPublisher, unbind = unsetEventPublisher]
18:46:53.556 [Component Resolve Thread] DEBUG o.e.s.c.i.i18n.LocaleProviderImpl - No language set, fallback to default system locale
18:46:53.918 [Component Resolve Thread] DEBUG o.e.s.core.common.ThreadPoolManager - Created thread pool 'ConfigStatusService' with size 5-10

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.918
!MESSAGE Could not bind a reference of component ConfigStatusService. The reference is: Reference[name = ConfigStatusProvider, interface = org.eclipse.smarthome.config.core.status.ConfigStatusProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addConfigStatusProvider, unbind = removeConfigStatusProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.929
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.type.ChannelTypeRegistry. The reference is: Reference[name = ChannelTypeProvider, interface = org.eclipse.smarthome.core.thing.type.ChannelTypeProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addChannelTypeProvider, unbind = removeChannelTypeProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.939
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.firmware.FirmwareRegistry. The reference is: Reference[name = FirmwareProvider, interface = org.eclipse.smarthome.core.thing.firmware.FirmwareProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addFirmwareProvider, unbind = removeFirmwareProvider]
18:46:53.942 [Component Resolve Thread] DEBUG o.e.s.core.common.ThreadPoolManager - Created scheduled thread pool 'FirmwareUpdateService' of size 5

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.944
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.firmware.FirmwareUpdateService. The reference is: Reference[name = FirmwareUpdateHandler, interface = org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler, policy = dynamic, cardinality = 0..n, target = null, bind = addFirmwareUpdateHandler, unbind = removeFirmwareUpdateHandler]
18:46:53.945 [ESH-FirmwareUpdateService-1] DEBUG o.e.s.c.t.f.FirmwareUpdateService - Running firmware status check.

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.948
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.internal.console.FirmwareUpdateConsoleCommandExtension. The reference is: Reference[name = FirmwareUpdateHandler, interface = org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler, policy = dynamic, cardinality = 0..n, target = null, bind = addFirmwareUpdateHandler, unbind = removeFirmwareUpdateHandler]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.959
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.ThingRegistry. The reference is: Reference[name = ThingProvider, interface = org.eclipse.smarthome.core.thing.ThingProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addProvider, unbind = removeProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.960
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.ThingRegistry. The reference is: Reference[name = ManagedThingProvider, interface = org.eclipse.smarthome.core.thing.ManagedThingProvider, policy = dynamic, cardinality = 0..1, target = null, bind = setManagedProvider, unbind = removeManagedProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.966
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.ThingRegistry. The reference is: Reference[name = ThingHandlerFactory, interface = org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory, policy = dynamic, cardinality = 0..n, target = null, bind = addThingHandlerFactory, unbind = removeThingHandlerFactory]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.970
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.link.ItemChannelLinkRegistry. The reference is: Reference[name = ItemChannelLinkProvider, interface = org.eclipse.smarthome.core.thing.link.ItemChannelLinkProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addProvider, unbind = removeProvider]

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.971
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.link.ItemChannelLinkRegistry. The reference is: Reference[name = ManagedItemChannelLinkProvider, interface = org.eclipse.smarthome.core.thing.link.ManagedItemChannelLinkProvider, policy = dynamic, cardinality = 0..1, target = null, bind = setManagedProvider, unbind = removeManagedProvider]
18:46:53.975 [Component Resolve Thread] DEBUG o.e.s.c.c.registry.AbstractRegistry - Provider 'org.eclipse.smarthome.core.thing.internal.ChannelItemProvider' has been added.

!ENTRY org.eclipse.equinox.ds 1 0 2016-06-25 18:46:53.977
!MESSAGE Could not bind a reference of component org.eclipse.smarthome.core.thing.type.ThingTypeRegistry. The reference is: Reference[name = ThingTypeProvider, interface = org.eclipse.smarthome.core.thing.binding.ThingTypeProvider, policy = dynamic, cardinality = 0..n, target = null, bind = addThingTypeProvider, unbind = removeThingTypeProvider]

!ENTRY org.eclipse.osgi 4 0 2016-06-25 18:46:54.809
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:4441)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Display.error(Display.java:1258)
at org.eclipse.swt.widgets.Display.checkDevice(Display.java:764)
at org.eclipse.swt.widgets.Display.getHighContrast(Display.java:1864)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application.setCSSContextVariables(E4Application.java:327)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:305)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:601)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.smarthome.designer.ui.internal.application.Application.start(Application.java:32)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
18:46:54.835 [Framework stop] DEBUG o.e.s.c.c.registry.AbstractRegistry - Provider 'ChannelItemProvider' has been removed.
18:46:54.853 [Framework stop] DEBUG o.e.s.core.internal.CoreActivator - Core bundle has been stopped.
An error has occurred. See the log file
E:\Develop\smarthome-master\smarthome-designer\.metadata\.log.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Re: Launch configuration for Smarthome Designer for Windows missing [message #1736117 is a reply to message #1736095] Sun, 26 June 2016 18:22 Go to previous messageGo to next message
Kai Kreuzer is currently offline Kai KreuzerFriend
Messages: 648
Registered: December 2011
Senior Member
You can ignore the "Could not bind" messages, so the only one that is left is the "Invalid thread access", but this often is only a side effect of something else - usually some bindings that are missing some dependencies.
Is there anything more helpful logged in E:\Develop\smarthome-master\smarthome-designer\.metadata\.log?

Re: Launch configuration for Smarthome Designer for Windows missing [message #1736118 is a reply to message #1736117] Sun, 26 June 2016 18:43 Go to previous messageGo to next message
Martin Herbst is currently offline Martin HerbstFriend
Messages: 4
Registered: August 2014
Junior Member
That was my guess too. Unfortunately the .log file contains no additional information. I have another idea: I have downloaded the last release package (runs without problems on my system) and I will compare the ini file settings of the release with the launch configuration. So it should be possible to create a working configuration.

I have some ideas to improve the usability and partially it should be quite easy to implement them.

Kai Kreuzer wrote on Sun, 26 June 2016 14:22
You can ignore the "Could not bind" messages, so the only one that is left is the "Invalid thread access", but this often is only a side effect of something else - usually some bindings that are missing some dependencies.
Is there anything more helpful logged in E:\Develop\smarthome-master\smarthome-designer\.metadata\.log?


Re: Launch configuration for Smarthome Designer for Windows missing [message #1749571 is a reply to message #1736118] Thu, 08 December 2016 09:14 Go to previous messageGo to next message
Yuv Mendel is currently offline Yuv MendelFriend
Messages: 2
Registered: December 2016
Junior Member
Hello,

This thread is about 6 months old but I am having the exact same issue, did you find a solution to this problem? If you could share it I would be great.

Thank you!
Re: Launch configuration for Smarthome Designer for Windows missing [message #1749632 is a reply to message #1749571] Thu, 08 December 2016 18:47 Go to previous messageGo to next message
Martin Herbst is currently offline Martin HerbstFriend
Messages: 4
Registered: August 2014
Junior Member
Hi,

no, I did not find a solution. I did not have the time to try it in the last months. As soon as I find some time to work on it and find a solution I will post it here.

Martin
Re: Launch configuration for Smarthome Designer for Windows missing [message #1749740 is a reply to message #1749632] Sat, 10 December 2016 16:57 Go to previous message
Martin Herbst is currently offline Martin HerbstFriend
Messages: 4
Registered: August 2014
Junior Member
Hi,

I was not able to execute it within Eclipse via the .product file, but I was able to build it with maven and then run it.

This is what I did:
I executed maven package for the pom.xml in org.eclipse.smarthome.designer.product

After the build finishes you will find executables for the different operating systems under
<Main Dir>\git\smarthome\products\org.eclipse.smarthome.designer.product\target\products\org.eclipse.smarthome.designer.product

Previous Topic:Developing binding: how to get all item values?
Next Topic:How can I run ESH outside of eclipse?
Goto Forum:
  


Current Time: Wed Jun 20 15:35:53 GMT 2018

Powered by FUDForum. Page generated in 0.02318 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top