Currently MetatypePropertiesFunction restarts CamelContext when SCR properties are updated. We should not do it, as it interrupts messages flow.

All other packages are built ok, except org.eclipse.kura.protocol.can. de.entropia.can.* is not available.

As can be seen in attachments, the downloading of the package did not start but the UI reports 100% for the download status value. (Refer to the event happened at 2:50:26 PM)

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=477275.

Original Message:

there can be many reasons for a component to fail to load, leading to it being 'unresolved'. in two examples:

1. I had a 'default' access level method named 'activate' which was not defined within the Component.xml
2. I had a private constructor

.. I had no idea at the time why the component was not loading, only after commenting out line by line did I find my mistakes.

If you are just watching the logs, it appears the platform silently ignores the componeont. Using OSGI console command 'ls' the component will appear 'unresolved' but still no detail as to what failed.

Therefore, if the component is defined via the manifest.mf or indeed, if it has a Component.xml or @component annotation, any reason for it to fail to load should be thrown as an exception.

Hi Paul,

Sorry for the slow reply, I am trying to go through and clean up the list of bugs. For reference, this was also mentioned in this forum post [1].

I am not sure how much Kura can do in these situations, if you have suggestions I am happy to discuss. The intent of the Kura ConfigurationService and Kura ConfigurableComponent was to assist in managing bundle configurations. The framework does not get involved in managing the life cycles of the bundles, leaving this instead to the OSGi container. Since ConfigurationService is tracking all Components within the OSGi container, it is plausible to set up a listener for different events, but this system may become rather complex.

I think to do this correctly, we would need a new service which would use EventAdmin to track OSGi bundle messages. It wouldn't make since to throw exceptions from here, but you could certainly log useful messages.

Let me know what you think.

[1] https://www.eclipse.org/forums/index.php/t/1070255/

Thanks,
--Dave

thanks for getting back david.

since posting this i have learnt to use the 'comp' command within the osgi terminal which gives some further information regarding why a component might be 'unresolved'.

maybe an easier solution with less re-architecting would be just to interrogate the deployment package's components via osgi after the load and log their details?

i'm assuming there is an easy way to do the equivalent of the following from within kura?

osgi> ss mydeployment
[bid] active mybundle
osgi> ls [bid]
[cid] unresolved mycomponent
osgo> comp [cid]

failing something simple like this, maybe just another developer guide document? the above has more or less resolved this issue for me, i just keep two terminals open when testing now.

let me know what you think.

Equinox doesn't export OSGi services defined in MANIFEST file. It means that Camel can't resolve components and languages by name without prior manual registration of those.

So apparently equinox ignores [1] exports defined in manifest, as declarative services are supposed to be used to register services.

We could created a dedicated declarative service responsible for registering the components and languages. However such code is hardly testable, as it requires an OSGi environment with SCR support to verify it works. I would prefer to add manual registration of components and languages in KuraRouter.

[1] https://dev.eclipse.org/mhonarc/lists/equinox-dev/msg01090.html

Throws ClassCastExceptions if you are on a network with IPv6 capabilities - see example below. Even worse - can never work on IPv6 only network. :(

java.lang.ClassCastException: org.eclipse.kura.net.IP6Address cannot be cast to org.eclipse.kura.net.IP4Address at org.eclipse.kura.linux.net.ConnectionInfoImpl.getDnsServers(ConnectionInfoImpl.java:123) at org.eclipse.kura.linux.net.NetworkServiceImpl.getNetInterfaceAddresses(NetworkServiceImpl.java:872) at org.eclipse.kura.linux.net.NetworkServiceImpl.getNetworkInterface(NetworkServiceImpl.java:518) at org.eclipse.kura.linux.net.NetworkServiceImpl.getNetworkInterfaces(NetworkServiceImpl.java:370) at org.eclipse.kura.net.admin.NetworkConfigurationServiceImpl.getNetworkConfiguration(NetworkConfigurationServiceImpl.java:277) at org.eclipse.kura.net.admin.NetworkAdminServiceImpl.getNetworkInterfaceConfigs(NetworkAdminServiceImpl.java:192) at org.eclipse.kura.web.server.GwtNetworkServiceImpl.privateFindNetInterfaceConfigurations(GwtNetworkServiceImpl.java:150) at org.eclipse.kura.web.server.GwtNetworkServiceImpl.findNetInterfaceConfigurations(GwtNetworkServiceImpl.java:107)

If I set the value of a service property to an empty string in the web UI and hit Apply the empty string is accepted and the corresponding service gets the empty string. When KURA gets restarted the value reverts to the default value from the metatype file. If I change the value to a non empty string the value is preserved across a KURA restart.
I'm changing command.working.directory but see the same behaviour on other properties.

Kura built from commit 983da0e.
Kura installed and running on RaspberryPi. When accessing the web admin interface the Network tabs shows no network interfaces and this stacktrace shows up in kura.log:

java.lang.NoClassDefFoundError: org/eclipse/kura/usb/UsbDevice
at org.eclipse.kura.web.server.GwtNetworkServiceImpl.findNetInterfaceConfigurations(GwtNetworkServiceImpl.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at org.eclipse.kura.web.server.OsgiRemoteServiceServlet.service(OsgiRemoteServiceServlet.java:43)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:384)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:486)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
at org.eclipse.jetty.server.Server.handle(Server.java:350)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)
at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:606)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
at java.lang.Thread.run(Thread.java:724)

"Copyright © 2011-2014 [...]" certainly give people a bad impression by making them believe the code project may be old/outdated (I can tell I had the remark more often than not!)

This bug was originally reported at https://bugs.eclipse.org/bugs/show_bug.cgi?id=480606.

Original message:

The nn version will throw out an exception when booting up, caused by not able to get EthernetDriver which is used to get eth0 MAC address for default MQTT client-id (if leave empty in UI setting).

Suggest to add ethtool dependency if possible.

We should migrate this [1] page from Rhiot documentation to Kura Wiki.

[1] https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_kura_router.html

I would be nice to have a dedicated wrapper around DataService.

I'm trying to use the "org.eclipse.kura.linux.bluetooth" module inside a Linux x86 environment (Debian Jessie).

Debian Jessie comes with bluez 5.23 per default and incidentally I'm obliged to stick to the 5.* version because of specific project's requirements.

Using the methods offered by the org.eclipse.kura.linux.bluetooth.le.BluetoothGattImpl class I have noticed that the it tries to parse the output of the "gatttool" interactive shell, but it uses regular expressions that are not compliant with the lines returned by the gatttool shell.

Making a comparison with an installation of bluez4.101 on a different machine I have figured out that Kura's implementation expects that output, thus resulting to be compliant with bluez4.101 and not with bluez5.x (at least for what concerns the BLE layer).

I'd like to know if someone else out there have encountered this same kind of problem and if they have worked it around (and how, possibly :-) ).
At the same time, I'm wondering if a migration (or fork) towards Bluez5.x is planned at all or not.

Any hint will be greatly appreciated, thanks in advance.

I just tried using CloudCallServiceImpl to send CONF-V1 requests to a Kura device. It seems to me that there is a bug in that implementation.

On line 122 it sets the requester.client.id to the topic placeholder #client-id. This in turn is send to the remote Kura device which then replaces it with its own client-id when sending the response. Not the intended outcome. This prevents the response from ever being picked up by the sender - it subscribes to the correct topic beforehand (using the same placeholder on line 110.

Before looking into a fix for this - am I missing something here? The problem with fixing this is that the client-id isn't available inside that implementation.

I've tested with manually providing the correct client-id on line 122 and that works properly.

Hints?

Quickstart example [1] seems to be hanging when uninstalling/redeploying bundle. I suspect that thread executor may not be properly closed.

[1] https://rhiot.gitbooks.io/rhiotdocumentation/content/quickstarts/kura_camel_quickstart.html

This bug was filed as: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480530.

Original message:

As of Kura 1.3, the $EDC prefix is not set in stone anymore, so it would be great to update the doc so as to make it clear that the prefix is customizable.

When starting the emulator in eclipse on OSX, the emulator says "Framework is not running in emulation mode".
Emulator.java:30 reads the wrong property
String mode=props.getProperty("eurotech.framework.mode");
but the Kura_Emulator_OSX.launch file specifies the correct flag
-Dorg.eclipse.kura.mode=emulator.
Kura_Emulator_Linux.launch has the old eurotech flag.
Kura_Core_Test.launch has the old eurotech flag.
Also the pom.xml of the org.eclipse.kura.core.test project has the old eurotech property specified.

After building Kura from commit 467ee53 and deploying it to Raspberry, accessing the web interface on the device gives

HTTP ERROR: 404

Problem accessing /kura. Reason:

    ProxyServlet: /kura
Powered by Jetty://

I'm using Eclipse Kepler 4.3, Google Web Toolkit SDK 2.6.0 and can't recognize the web project. Is this configuration supported or is GWT 2.4.0 a strict requirement?

edit
using a higher log level for jetty bundle, this is what I see in kura.log

2014-06-04 13:38:01,715 [qtp30188208-24 Selector0] DEBUG o.e.j.i.nio - created SCEP@1156782{l(/10.13.1.58:55240)<->r(/10.13.2.4:80),d=false,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0}-{AsyncHttpConnection@3e8c76,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}
2014-06-04 13:38:01,766 [qtp30188208-21] DEBUG o.e.j.h.HttpParser - filled 452/452
2014-06-04 13:38:01,887 [qtp30188208-21 - /kura] DEBUG o.e.j.s.Server - REQUEST /kura on AsyncHttpConnection@3e8c76,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-5,l=37,c=0},r=1
2014-06-04 13:38:01,900 [qtp30188208-21 - /kura] DEBUG o.e.j.s.h.ContextHandler - scope null||/kura @ o.e.j.s.ServletContextHandler{/,null}
2014-06-04 13:38:01,914 [qtp30188208-21 - /kura] DEBUG o.e.j.s.h.ContextHandler - context=||/kura @ o.e.j.s.ServletContextHandler{/,null}
2014-06-04 13:38:01,973 [qtp30188208-21 - /kura] DEBUG o.e.j.s.session - Got Session ID 1lw9vectvn62c106l3lw70jb4v from cookie
2014-06-04 13:38:01,984 [qtp30188208-21 - /kura] DEBUG o.e.j.s.session - sessionManager=org.eclipse.jetty.server.session.HashSessionManager@7b6c50
2014-06-04 13:38:01,986 [qtp30188208-21 - /kura] DEBUG o.e.j.s.session - session=null
2014-06-04 13:38:02,006 [qtp30188208-21 - /kura] DEBUG o.e.j.s.ServletHandler - servlet ||/kura -> org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-31403932
2014-06-04 13:38:02,008 [qtp30188208-21 - /kura] DEBUG o.e.j.s.ServletHandler - chain=null
2014-06-04 13:38:02,167 [qtp30188208-21 - /kura] DEBUG o.e.j.s.Server - RESPONSE /kura  404
2014-06-04 13:38:02,190 [qtp30188208-21] DEBUG o.e.j.s.AsyncHttpConnection - Enabled read interest SCEP@1156782{l(/10.13.1.58:55240)<->r(/10.13.2.4:80),d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0r}-{AsyncHttpConnection@3e8c76,g=HttpGenerator{s=4,h=0,b=0,c=-1},p=HttpParser{s=0,l=37,c=0},r=1}
2014-06-04 13:38:02,244 [qtp30188208-21] DEBUG o.e.j.h.HttpParser - filled 0/0

To ease the setup of Development Environment, an Oomph Catalogue can be provided. Many eclipse projects, for instance, E4 Tools, EMF provide Oomph Catalogues for a hassle free development environment setup.

Another solution could be to create an Yatta Profile to package an Eclipse Installation which abstracts all the required steps for Development Environment setup.

This was originally filed as bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=461555.

Original comments from bug:

Modem addons for USB and serial devices
Huawei USB Exxx E220, E620, E173
Telit serial GE865
Serial modem communication for Raspberry

Commitet at Fork https://github.com/devNbis/kura.git

Tried to build heater example using Maven. Also, try to build my own project using Maven. All encounter error, cannot resolve target platform specification. Tried to access the maven-metadata.xml and target-definition-0.0.1-SNAPSHOT-kura-equinox_3.8.1.target, but the raw,guthub.com URL is not working. Does the URL should be changed?

Log: https://gist.github.com/bontorhumala/f0037980fccf0d5cac7a.

See https://www.eclipse.org/forums/index.php?t=rview&goto=1728853#msg_1728853
The documentation of the WatchdogService should probably be moved (or duplicated? but meh...) to Kura? See https://esf.eurotech.com/docs/how-to-use-watchdog

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=456781.

Original Message:

The new "Solution Showcases" section is very cool!
It would be great if the images were clickable in addition to the text, since I believe many people are trying to click on them as a first intent.

A related suggestion would be to put the labels below the images rather than next to them, and center the text. It would probably give more white space and make it clearer which "button" goes with which label.

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=481526.

Original Message:

Some users of Kura have found the static settings of the CloudService to restrictive. This bug is to track the proposal to expose more internal settings of the CloudService. Below is a listing of options to expose. Please use this bug to suggest additional options to expose or options to remove from the list.

• TOPIC_CONTROL_PREFIX - Already added via pull request: #64
• LIFECYCLE_RETAIN - Allow lifecycle messages to be retained for applications not using persistent storage.
• LIFECYCLE_PRIORITY - Specify priority of lifecycle messages.
• LIFECYCLE_QOS - Specify QOS of lifecycle messages.

Thanks,
--Dave

• LIFECYCLE_RETAIN - Allow lifecycle messages to be retained for applications not using persistent storage.

I'm not sure this is a good idea because the broker will store the last message for each of the lifecycle messages. They are published on different topics so a connecting subscriber will receive the last birth and disconnect message in no particular order and won't be able to derive if the device is connected or not.

Also, it's difficult to reset the retain behavior because the device will have to publish an empty payload on the retained topic.

• LIFECYCLE_PRIORITY - Specify priority of lifecycle messages.

In order to work correctly, the lifecycle messages need to be published immediately, overtaking the outstanding messages stored by the DataService.

• LIFECYCLE_QOS - Specify QOS of lifecycle messages.
  You want the lifecycle message to be published in the current MQTT session or never. If they were published with QoS > 0 and the connection is lost before they are acknowledged by the broker, either Kura or Paho will republish them on reconnect. However on reconnect a new lifecycle message, the birth certificate, will be published. For this reason we use QoS == 0 for lifecycle messages.

This bug was originally filed at: https://bugs.eclipse.org/bugs/show_bug.cgi?id=463915.

Message from original bug:

The data service will not start up/connect once you have a non-english locale defined, since it searches for the keyword „"metric" within the output of ifconfig . Unfortunately if you have another locale configured, for example german, ifconfig returns "metrik" (german word for metric) and kura fails to parse the output and throws a runtime exception (StringIndexOutOfBoundsException) so that the data service is not available. After changing the locale with raspi-config everything worked fine.

Happened to me on a raspberry pi with raspbian installed.

Also see my blog: http://icanseedeadcats.com/2015/03/24/eclipse-iot-challenge-mqtt-communication-for-hot-desks-featuring-kura-mosquitto-and-paho-and-project-wrapup/

Below is a snippet of the stacktrace:

2015-03-21 20:39:28,330 [Component Resolve Thread (Bundle 6)] ERROR o.e.k.c.d.t.
m.MqttDataTransport - Invalid client configuration. Service will not be able to connect until the configuration is updated
java.lang.StringIndexOutOfBoundsException: String index out of range: -49
at java.lang.String.substring(String.java:1911)
at org.eclipse.kura.linux.net.util.LinuxNetworkUtil.getCurrentMtu(LinuxNetworkUtil.java:294)
at org.eclipse.kura.linux.net.NetworkServiceImpl.getNetworkInterface(NetworkServiceImpl.java:439)
at org.eclipse.kura.linux.net.NetworkServiceImpl.getNetworkInterfaces(NetworkServiceImpl.java:314)
at org.eclipse.kura.core.system.SystemServiceImpl.getPrimaryMacAddress(SystemServiceImpl.java:377)
at org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport.buildConfiguration(MqttDataTransport.java:633)

We have some nice unit tests for CamelRouter which should be migrated from Rhiot to Kura. That would give us some safety net against regressions.

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=476616.

Original Message:

Unless I'm missing something, I believe the "no network" .deb package should not be depending on any networking tool, right?

Agree.
However, just one exception, it seems that ethtool is still needed for LinuxNetworkUtil bundle to get ethernet MAC address for kura MQTT default client-id.

I am going to use this bug to track bug fixes for the NN installation packages. At present, not only are the networking system dependencies required, but the networking bundles are also being installed and started. This is not the correct behavior and should be corrected.

Thanks,
--Dave

I build Kura according to instruction (clone git, mvn clean install), copy the resulting kura-raspberry-pi-jars_0.2.0-SNAPSHOT.zip to my RPi, then unzip the content to /opt/eclipse. But when I run Kura (sudo sh /opt/eclipse/kura/bin/start_kura_background.sh), I cannot connect to the OSGi console (connection refused). In the log file, I see that there is problem with jetty server and port 5002:

!MESSAGE Bundle org.eclipse.equinox.http.jetty_3.0.0.v20120522-1841 [20] is not active. Cannot start telnet. Reason: Port 5002 already in use. java.lang.Exception: Port 5002 already in use

Seems like there is problem with resulting build package for raspberry pi?

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=440544.

Original message:

I don't know what are the plans regarding a possible contribution of PDE plug-ins that would ease the creation of new Kura bundles from the Eclipse IDE, but it would be really great to have some basic tools helping in bootstrapping a Kura bundle. Maybe a Maven archetype would be even better than PDE tooling since it would virtually allow to rely on command-line only for building one's first Hello World.

I'm thinking of things like:

• setup the bundle so as it has one dummy component already configurable over ConfigAdmin (xml file in OSGI-INF/metatype/xxx is already there, component has a service.pid, etc.)
• setup the pom.xml so as the Maven project is by default belonging to a parent POM already bringing the Tycho settings, dependency to Kura target platform, etc...
• setup the bundle so as it's properly hooked up to an sl4j logger

Icing on the cake would be other archetypes (or archetype parameters) to automatically generate the plumbing for having e.g. a component hooked up to the DataService, or CloudService, etc.

ping :)
I wonder if someone in the community as done something similar already, maybe?

Hi Benjamin,

I think this is a very useful idea. Is there useful documentation on how to create these types of PDE plugins? I will to try and gauge the effort behind doing this.

Thanks,
--Dave

This bug was originally posted at https://bugs.eclipse.org/bugs/show_bug.cgi?id=459361.

Original message:

I use kura on debian (PI) and I try to open port 514 in the firewall config page for both udp and tcp.

After I add entry 514 / udp/ eth0, save, apply, all ok, I try to do the same for 514 / tcp / eth 0.

On Submit I get the error Duplicate Entry - Not adding to the list of Open Port.

Looks like primary key is wrong.

Ilya,

Can you check on this behavior?

Thanks,
--Dave

Hi there,

I could maven build Kura successfully on my computer. But after imported into Eclipse,
lots of errors showed up. I couldn't find files listed below.

org.eclipse.kura.web.client.messages.Messages;
org.eclipse.kura.web.shared.service.GwtComponentServiceAsync;
org.eclipse.kura.web.shared.service.GwtDeviceServiceAsync;
org.eclipse.kura.web.shared.service.GwtNetworkServiceAsync;
org.eclipse.kura.web.shared.service.GwtPackageServiceAsync;
org.eclipse.kura.web.shared.service.GwtSettingServiceAsync;
org.eclipse.kura.web.shared.service.GwtSnapshotServiceAsync;
org.eclipse.kura.web.shared.service.GwtStatusServiceAsync;

I did follow the guide on the main page. Thank you!

This bug was original reported at https://bugs.eclipse.org/bugs/show_bug.cgi?id=480434.

Original messages:

In the release version 1.2.2 or version 1.3.0 RC1, one bluetooth le device (e.g. TI SensorTag) works well, but if you try to connect 2 or more bluetooth le devices, the second one couldn't connect. However, due to bluetooth specs, it should be OK to connect several bluetooth le devices at the same time.

GitHub Pull Request 66 created by [gavinying]
#66

I'm running "mvn -e -Dmaven.test.skip=true -f manifest_pom.xml clean install && mvn -f manifest_pom.xml" in the kura folder. My java version is

java version "1.7.0_65"

[INFO] --- tycho-compiler-plugin:0.20.0:compile (default-compile) @ org.eclipse.kura.core ---
[INFO] Compiling 27 source files to /Users/kread/git/kura/kura/org.eclipse.kura.core/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] kura .............................................. SUCCESS [19.499s]
[INFO] Kura Target Definition ............................ SUCCESS [0.213s]
[INFO] org.eclipse.kura.api .............................. SUCCESS [6.986s]
[INFO] org.eclipse.kura.test ............................. SUCCESS [0.480s]
[INFO] org.eclipse.kura.core ............................. FAILURE [0.353s]
[INFO] org.eclipse.kura.core.cloud ....................... SKIPPED
[INFO] org.eclipse.kura.core.comm ........................ SKIPPED
[INFO] org.eclipse.kura.core.configuration ............... SKIPPED
[INFO] org.eclipse.kura.core.crypto ...................... SKIPPED
[INFO] org.eclipse.kura.deployment.agent ................. SKIPPED
[INFO] org.eclipse.kura.core.deployment .................. SKIPPED
[INFO] org.eclipse.kura.core.net ......................... SKIPPED
[INFO] org.eclipse.kura.emulator ......................... SKIPPED
[INFO] org.eclipse.kura.core.test ........................ SKIPPED
[INFO] org.eclipse.kura.deployment.customizer ............ SKIPPED
[INFO] org.eclipse.kura.deployment.update ................ SKIPPED
[INFO] org.eclipse.kura.linux.clock ...................... SKIPPED
[INFO] org.eclipse.kura.linux.command .................... SKIPPED
[INFO] org.eclipse.kura.linux.net ........................ SKIPPED
[INFO] org.eclipse.kura.linux.net.test ................... SKIPPED
[INFO] org.eclipse.kura.linux.position ................... SKIPPED
[INFO] org.eclipse.kura.linux.usb ........................ SKIPPED
[INFO] org.eclipse.kura.linux.watchdog ................... SKIPPED
[INFO] org.eclipse.kura.net.admin ........................ SKIPPED
[INFO] org.eclipse.kura.protocol.modbus .................. SKIPPED
[INFO] org.eclipse.kura.protocol.modbus.test ............. SKIPPED
[INFO] examples .......................................... SKIPPED
[INFO] org.eclipse.kura.demo.heater ...................... SKIPPED
[INFO] org.eclipse.kura.demo.modbus ...................... SKIPPED
[INFO] org.eclipse.kura.example.project .................. SKIPPED
[INFO] org.eclipse.kura.example.publisher ................ SKIPPED
[INFO] org.eclipse.kura.example.serial.publisher ......... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 37.295s
[INFO] Finished at: Thu Jul 17 10:02:40 CEST 2014
[INFO] Final Memory: 28M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.eclipse.kura.core: Compilation failure: Compilation failure:
[ERROR] /Users/kread/git/kura/kura/org.eclipse.kura.core/src/main/java/org/eclipse/kura/core/ssl/SSLSocketFactoryWrapper.java:[141]
[ERROR] sslParams.setEndpointIdentificationAlgorithm("HTTPS");
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The method setEndpointIdentificationAlgorithm(String) is undefined for the type SSLParameters
[ERROR] 1 problem (1 error)
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.eclipse.kura.core: Compilation failure

In order to ease the installation of Kura in a Karaf container, it would be great to add a Karaf feature definition to the repo and Maven build.
Hopefully, it's not too difficult, see eg https://github.com/eclipse/smarthome/blob/master/features/karaf/pom.xml

Having Kura available in the form of a Karaf feature would make it much easier to install it in the same OSGi container as e.g Eclipse SmartHome, or OpenDaylight

Kura with networking support does not work properly with the latest Intel Edison image. Two issues identified thus far:

1. The installation uses the single WiFi interface to set the Edison up as a WiFi Access Point. If a client connects to the access point, the web UI (172.16.1.1:8080/kura) is not operating correctly. The services are not available to configure Kura.
2. The DataTransportService is not being activated correctly. This is likely related to item 1.

Kura: v1.3.0
Intel Edison: Linux edison 3.10.17-poky-edison+

--Dave

This bug was originally filed as: https://bugs.eclipse.org/bugs/show_bug.cgi?id=474906.

Original message:

The WifiAccessPoint interface says for getStrenght() method: "The current signal quality of the access point, in percent."

http://download.eclipse.org/kura/releases/1.2.0/docs/apidocs/org/eclipse/kura/net/wifi/WifiAccessPoint.html#getStrength()

This does not match when using iwScanTool to look for WifiAccessPoint, since the implementation of "iwScantool.java" around line 362
else if(line.contains("signal:")) {
try {
//signal: -56.00 dBm
StringTokenizer st = new StringTokenizer(line, " ");
st.nextToken(); //eat signal:
final String strengthRaw = st.nextToken();
if (strengthRaw.contains("/")) {
// Could also be of format 39/100
final String[] parts = strengthRaw.split("/");
strength = (int) Float.parseFloat(parts[0]);
} else {
strength = Math.abs((int)Float.parseFloat(strengthRaw));
}
} catch (RuntimeException e) {
s_logger.debug("Cannot parse signal strength " + line);
}
}

sets a better strenght to worse signal.
-56 dBm (good) --> 56 percent (bad)
-80 dBm (bad) --> 80 percent (good)
This could potentially go over 100.

We need to migrate those [1] two [2] modules from Rhiot to Kura.

[1] https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/kura_cloud.html
[2] https://rhiot.gitbooks.io/rhiotdocumentation/content/gateway/camel_components/camel_kura_cloud_service_bridge.html

We should support certain welcome message for Camel SCR XML routes. For example "...Insert XML Camel route...". This message should be displayed in the Kura web UI, but should not be parsed by Camel module.

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=480484.

Original Message:

Hi guys !

We faced of a serious problem with the Deployment Agent service (in all version)

Sometimes this service is blocked and don't deploy our ".dp". Last log we have from the service is :

2015-10-23 12:59:23,389 [Component Resolve Thread (Bundle 6)] INFO o.e.k.d.a.i.DeploymentAgent - Deploying package name io.stemys.kura.application.shopfloor at URL file:/opt/eclipse/kura/kura/packages/io.stemys.kura.application.shopfloor-0.2.0.dp

And nothing else.

When it's works we have the next log message :

2015-10-23 12:59:23,392 [DeploymentAgent] INFO o.e.k.d.a.i.DeploymentAgent - About to install package at URL file:/opt/eclipse/kura/kura/packages/io.stemys.kura.application.shopfloor-0.2.0.dp

It's really random. We look at the code to see what is between these two log messages and we think the problem come from the synchronized part on "m_instPackageUrls"

The synchronized part on a ConcurrentLinkedQueue is really necessary ? We remove it and the problem was resolved for us.

We never saw this problem before but now that we installed Kura on a powerfull device (core i7 / 16 Gb ram / SSD / ...) we have the problem.

Thanks in advance for your job !

Hello,

It is hard to comment on this without knowing your application. I believe the synchronization block is necessary when attempting to install the deployment package. A couple of questions:

1. When you see this issue, are you also getting error in the log files (/var/log/kura.log and /var/log/kura-console.log)?
2. Do you have any potential long running processes in your bundle activate methods? This can often cause issues when activating bundles.

Thanks,
--Dave

This bug was originally reported at https://bugs.eclipse.org/bugs/show_bug.cgi?id=450214.

Original message:

At present, when stopping Kura, the init.d script telnets into the OSGi container and stops the framework. If Monit is being used to control Kura, it will restart the framework when it detects the missing process. The init.d script should be enhanced to correctly shutdown Kura even if controlled by Monit.

--Dave

org.eclipse.soda.dk.comm library doesn't start on 64bit OSX emulator, giving this error in console.

!SESSION 2014-06-04 11:02:14.567 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Command-line arguments:  -dev file:/Users/ale/dev/workspaces/ws-kura-snapshot/.metadata/.plugins/org.eclipse.pde.core/Kura_Emulator_OSX/dev.properties -os macosx -ws cocoa -arch x86_64 -consoleLog -console

!ENTRY org.eclipse.osgi 2 0 2014-06-04 11:02:22.138
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2014-06-04 11:02:22.139
!MESSAGE Bundle initial@reference:file:org.eclipse.soda.dk.comm_1.2.0.jar was not resolved.
!SUBENTRY 2 org.eclipse.soda.dk.comm 2 0 2014-06-04 11:02:22.139
!MESSAGE Missing native code match lib/linux/x86/libdkcomm.so; processor=x86; osname=Linux, lib/linux/x86_64/libdkcomm.so; processor=x86-64; osname=Linux, lib/linux/armv6_hf/libdkcomm.so; processor=ARM; osname=Linux; selection-filter="(&(kura.arch=armv7_hf))", lib/linux/armv5_sf/libdkcomm.so; processor=ARM; osname=Linux; selection-filter="(&(kura.arch=armv7_sf))", lib/linux/armv6_hf/libdkcomm.so; processor=ARM; osname=Linux; selection-filter="(&(kura.arch=armv6_hf))", lib/linux/armv5_sf/libdkcomm.so; processor=ARM; osname=Linux; selection-filter="(&(kura.arch=armv6_sf))", lib/linux/armv5_sf/libdkcomm.so; processor=ARM; osname=Linux; selection-filter="(&(kura.arch=armv5_sf))", lib/mac/x86/libdkcomm.jnilib; processor=x86; osname=MacOSX.

I have some troubles instantiating a serial connection to a modbus device using the emulator. The hardware is a Serial-to-USB FTDI cable with a modbus device attached.
This works on the raspberry (I see the FTDI cable as /dev/ttyUSB0) and the modbus data connection is fine.

However if I try to use the same FTDI cable on my development machine things don't work.
In my "Run configuration" I specified the VM argument: -Dkura.ext.dir=/Users/ale/dev/tmp/ to a directory containing javax.comm.rxtx.properties file declaring the serial port (/dev/tty.usbserial-FTWDSO8Z).
When I try to access the port Kura says it doesn't exist:

16:00:55,119 [Component Resolve Thread (Bundle 47)] WARN  ModbusProtocolException:236  - Could not load Exception Messages Bundle for Locale en_US
org.eclipse.kura.protocol.modbus.ModbusProtocolException: Generic Error - CONNECTION_FAILURE: {1} {2} {3} {4} {5} null
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice$SerialCommunicate.<init>(ModbusProtocolDevice.java:425)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice.configureConnection(ModbusProtocolDevice.java:263)
at my.bundle.serial.AbstractModbusSerialReader.<init>(AbstractModbusSerialReader.java:63)
at my.bundle.serial.Sdm630SerialReader.<init>(Sdm630SerialReader.java:39)
at my.bundle.serial.SerialReaderFactory.createSerialReader(SerialReaderFactory.java:61)
at my.bundle.Dispatcher.doUpdate(Dispatcher.java:210)
at my.bundle.Dispatcher.activate(Dispatcher.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:386)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:225)
at org.eclipse.equinox.internal.ds.InstanceProcess.disposeInstances(InstanceProcess.java:356)
at org.eclipse.equinox.internal.ds.InstanceProcess.disposeInstances(InstanceProcess.java:306)
at org.eclipse.equinox.internal.ds.Resolver.disposeComponentConfigs(Resolver.java:717)
at org.eclipse.equinox.internal.ds.Resolver.disableComponents(Resolver.java:693)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:359)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:303)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:91)
at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Caused by: java.io.IOException: javax.comm.NoSuchPortException
at org.eclipse.kura.core.comm.CommConnectionFactory.createConnection(CommConnectionFactory.java:62)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice$SerialCommunicate.<init>(ModbusProtocolDevice.java:423)
... 45 more
Caused by: javax.comm.NoSuchPortException
at javax.comm.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:106)
at org.eclipse.kura.core.comm.CommConnectionImpl.<init>(CommConnectionImpl.java:85)
at org.eclipse.kura.core.comm.CommConnectionFactory.createConnection(CommConnectionFactory.java:59)
... 46 more

Manually adding the port causes a different error. In Emulator project MANIFEST.MF I added to Import-Package section the following: javax.microedition.io, javax.comm;version="1.2.0"
and in Emulator.java I added the following line at the end of activate() method: CommPortIdentifier.addPortName("/dev/tty.usbserial-FTWDSO8Z", CommPortIdentifier.PORT_SERIAL, null);

javax.comm.UnsupportedCommOperationException
at org.eclipse.soda.dk.comm.NSSerialPort.setSerialPortParams(NSSerialPort.java:1288)
at org.eclipse.kura.core.comm.CommConnectionImpl.<init>(CommConnectionImpl.java:92)
at org.eclipse.kura.core.comm.CommConnectionFactory.createConnection(CommConnectionFactory.java:59)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice$SerialCommunicate.<init>(ModbusProtocolDevice.java:423)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice.configureConnection(ModbusProtocolDevice.java:263)
at my.bundle.serial.AbstractModbusSerialReader.<init>(AbstractModbusSerialReader.java:63)
at my.bundle.serial.Sdm630SerialReader.<init>(Sdm630SerialReader.java:39)
at my.bundle.serial.SerialReaderFactory.createSerialReader(SerialReaderFactory.java:61)
at my.bundle.Dispatcher.doUpdate(Dispatcher.java:210)
at my.bundle.Dispatcher.activate(Dispatcher.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:363)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:303)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:91)
at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)

Trying to use the port gives

org.eclipse.kura.protocol.modbus.ModbusProtocolException: Generic Error - CONNECTION_FAILURE: {1} {2} {3} {4} {5} null
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice$SerialCommunicate.<init>(ModbusProtocolDevice.java:436)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice.configureConnection(ModbusProtocolDevice.java:263)
at my.bundle.serial.AbstractModbusSerialReader.<init>(AbstractModbusSerialReader.java:63)
at my.bundle.serial.Sdm630SerialReader.<init>(Sdm630SerialReader.java:39)
at my.bundle.serial.SerialReaderFactory.createSerialReader(SerialReaderFactory.java:61)
at my.bundle.Dispatcher.doUpdate(Dispatcher.java:210)
at my.bundle.Dispatcher.activate(Dispatcher.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:363)
at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:303)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:91)
at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Caused by: java.lang.NullPointerException
at org.eclipse.soda.dk.comm.NSSerialPort.getInputStream(NSSerialPort.java:604)
at org.eclipse.kura.core.comm.CommConnectionImpl.openInputStream(CommConnectionImpl.java:115)
at org.eclipse.kura.protocol.modbus.ModbusProtocolDevice$SerialCommunicate.<init>(ModbusProtocolDevice.java:433)
... 47 more 

My Java:
$> java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

My Eclipse:
$> file Eclipse.app/Contents/MacOS/eclipse
Eclipse.app/Contents/MacOS/eclipse: Mach-O 64-bit executable x86_64

My machine (OSX 10.9.3):
$> uname -a
Darwin Alessandros-MacBook-Pro.local 13.2.0 Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64 x86_64

Am I missing something? What else can I do to help resolve the issue?

Thank you.

We should avoid throwing unchecked Exceptions (like RuntimeException or UnsupportedOperationException) from methods already throwing a KuraException.

There is a demand for Camel wrapper around Kura modbus support.

When trying Kura for the first time, people might be confused to see the SslManagerService configured with two settings (keystore and truststore location) defaulting to /opt/eurotech/...

This bug was originally filed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=481529.

Original Message:

This bug will track a feature request to create a minimal version of Kura with no native code dependencies. At present, the SystemService in Kura depends on native libraries to start. This dependency restricts the possibility of running Kura on very resource constrained devices. This request will remove native library dependency on core Kura bundles.

Thanks,
--Dave

Does "Pure Java Kura" mean that it must be OS independent? This would also require removing references to OS system files (e.g. /etc/) or spawning external processes via Runtime.exec() or similar.