Resolved and known issues

The following table provides a summary of issues that were fixed in release 10.4.0:

#	Module	Topic/ keyword	Issue and resolution	Affect Version
1	Azure IoT 1.3.0	Security, missing permission	Local permissions were missing in bundle com.prosyst.mbs.azure.iot.adapter. Now this is fixed.	10.3.0
2	BACnet 1.3.1000	BACnetDiscovery, whoIsInterval	The discovery parameter whoIsInterval was ignored when BACnet discovery was started with parameters. Now it is fixed.	10.2.0
3	Bluetooth LE 1.9.0	Unknown descriptor UUIDs	BtleGattDescriptor fails to initialize for unknown descriptor UUIDs. This is now fixed.	9.3.0
4	Bluetooth LE 1.9.0	Descriptor writeValue	Descriptor.writeValue was cutting the value up to 3 bytes. This is now fixed.	9.3.0
5	Cameras 4.5.3000	Backup and restore	An error was returned when trying to remove device which is registered with wrong address, host or port. This issue was affecting the restore operation. Now it is fixed.	10.0.0
6	Cameras 4.5.3000	Device offline behavior	Fixed functional items not unregistered when device goes into offline state. Added exceptional case for the Configuration functional item. The fix will not affect the HDM usage.	10.0.0
7	Cameras 4.5.3000	RTSP proxy	Stream not opened using RTSP Proxy when device supports both Digest and Basic authentication caused by Authentication sequential problem. This is now fixed.	9.0.0
8	Device Access 3.7.2000	Log	The Device Access logs message with text 'null' instead of the protocol adapter name. Now it is fixed.	10.0.0
9	External 1.8.0	Memory leak	There was a potential memory leak in the org.eclipse.equinox.http.servlet bundle. That was due to an incorrect AccessControlContext usage. Now it is fixed.	10.3.0
10	Framework 8.6.4002	Framework factory, framework launcher	There was an error when trying to launch framework through an external application programatically, without using the server script. Now this is fixed and framework can be launched using both setups.	10.3.0
11	Framework 8.6.4002	Framework startup	There was a problem loading some prs files, when mbs.props.base system property value did not end with a '/' character. This has now been fixed and such formats are handled too.	10.3.0
12	Framework 8.6.4002	Backup Admin	There is a minor fix in Backup Admin in order not to ignore EOF exceptions, but propagate them to the caller.	10.3.0
13	Framework 8.6.4002	Resource lookup, framework launcher	There was a problem accessing resources through a bundle class loader, when a framework is started via framework launcher API. This has now been fixed.	10.3.0
14	Framework 8.6.4002	Resource lookup	There was a problem accessing inner class resources through Bundle Wiring API BundleWiring#listResources(...). This has now been fixed.	10.3.0
15	Framework 8.6.4002	Framework storage, corrupted files	Framework was unable to start with ready storage when framework state, bundle state or startlevel state files were corrupted, unless that storage was explicitly deleted. Now it is possible to enable self-cleaning behavior by setting system property mbs.storage.cleanIfCorrupted to true. Enabling this functionality means, that framework will clean its storage, if a corrupted storage file is detected, and then retry initialization.	10.3.0
16	Framework 8.6.4002	Framework, Java 16	Framework scripts adapted for Java 16.	10.3.0
17	mDNS 1.3.3000	Security, missing permission	Missing local permissions in bundle com.prosyst.mbs.mdns.jmdns.jar. Now this is fixed.	10.3.0
18	ONVIF 1.7.0	Complex type of notifications	Complex Types events containing the ElementItems data in raw are not processed correctly. Now this is fixed.	10.3.0
19	ONVIF 1.7.0	Events handling Pull messages	Fixed PullMessages were failing due to ElementItems bean conversion problem. Now this is fixed.	10.3.0
20	ONVIF 1.7.0	Device services	When device was registered as not trusted and then restored as trusted, the services were not read, due to element to item bean conversion problem. This is now fixed.	10.1.0
21	ONVIF 1.7.0	Device status	When device was registered as trusted and then disconnected while restoring, the device status mechanism was not started, causing the device to stay in offline mode even if device became available later. This is now fixed.	10.3.0
22	OSGi Things Agent 1.2.1	Remove feature, unregister device item	When Device with several device items was registered, OSGi Things Agent mapped the Device to Thing and the device items were mapped to features of the thing. When any device item was unregistered then the corresponding feature was not removed and the feature removed event was not sent. Now this problem is fixed. When any device item is unregistered, OSGi Things Agent removes the corresponding feature of the thing and sends notification for feature removed to subscribe listeners.	10.2.0
23	OSGi Things Agent 1.2.1	Configuration not created	It was not possible to create configuration via ConfigurationFactory when there was no metatype provider. Now it is fixed and configuration can be created without metatype provider.	10.2.0
24	OSGi Things Agent 1.2.1	Update thing	If the reload of the provisioning.json file was successful, a new edge/thing/response MQTT message was published with the updated information. The MQTT connector accepted the updated edge thing information and stored the new data internally. The problem was that the MQTT connector did not notify the Thing Admin service that something has changed. Now this is fixed and if there are some changes, the MQTT connector and Thing Admin service are reinitialized.	10.2.0
25	OSGi Things Agent 1.2.1	Device item UID	OSGi Things Agent produced the wrong feature UID for device items, which contained '/' or '%' in their device item UID. Now this is fixed.	10.2.0
26	OSGi Things Agent 1.2.1	BundleFactory filter property	When trying to set the filter property value to null, an error would occur. This is fixed, and null value is supported. Now, when a null value is set, all registered features as part of the edge:services:bundles thing get unregistered.	10.3.0
27	OSGi Things Agent 1.2.1	FrameworkManagement	OSGi Things Agent created and sent two events when framework start level was changed. Now it is fixed and only one event is created.	10.3.0
28	OSGi Things Agent 1.2.1	Security, ConfigurationFactory	Everyone using ConfigurationFactory needed specific configuration permission. That was not correct. Now the OGSi Things Agent is fixed and such permission is not required.	10.3.0
29	OSGi Things Agent 1.2.1	Invoke operation	The Bosch IoT Things service uses x-things-parameter-order header for operation request. OSGi Things Agent handled single-parameter operations incorrectly , when the whole payload was a single argument. Now this is fixed.	10.2.0
30	Policy Admin 1.2.5000	Security	There was a security issue, when invoking PolicyAdmin.updatePolicy method, requiring the caller to have java.io.SerializablePermission. This has now been fixed and such permission is no longer required.	10.2.0
31	REST 2.1.4001	Publisher config start	Race condition in Publisher Config bundle prevented it from starting properly, when the bundle was stopped/started in quick succession. This issue is now fixed.	10.2.0
32	REST 2.1.4001	Collection pages	When multiple Timer services were available, a bug in Core bundle caused collection pages to disappear when one of the services disappeared. This issue is now fixed.	10.2.0
33	WebSockets 1.3.3000	Upgrade request, security mode	Missing socket resolve permissions in JavaX Websocket bundle caused upgrade requests to fail in security mode. This issue is now fixed.	10.2.0
34	Zigbee 4.12.0	Security permissions	Missing local permissions in bundles: com.prosyst.mbs.zigbee.simulator.sample.jar com.prosyst.mbs.zigbee.simulator.zcl.ha.jar com.prosyst.mbs.zigbee.simulator.zcl.hvac.jar com.prosyst.mbs.zigbee.simulator.zcl.lighting.jar com.prosyst.mbs.zigbee.simulator.zcl.general.jar com.prosyst.mbs.zigbee.zcl.metadata.service.jar Now this is fixed.	10.0.0

Known issues

The following section provides a summary of known issues in the current release:

System Integrity Protection (SIP) in macOS: Affecting Gateway Software version 9.3.X, when System Integrity Protection on Mac OS X is turned on, bundles with native libraries may throw an Error, when libraries are loaded and it may lead to malfunctioning of the bundles. System Integrity Protection has to be disabled in order to use the functionality provided by the native libraries from the bundles on macOS/OS X since version 10.11 (OS X El Capitan).

#	Module	Search keyword	Known Issue
1	ONVIF 1.7.0	Target Image EJDK compact1	Apache xerces library is used for ONVIF Discovery and it is not included in the Target Images. The bundle org.apache.xerces.jar needs to be installed manually when using EJDK compact1 profile.
2	ONVIF 1.7.0	TLS resumption	Java is introducing the Extended Master Secret Extension enabled by default after the 8u161 update. Some Cameras which do not support the extension will cause the TLS resumption to fail during the SSL handshake. Without resumption, the delay for each ONVIF request will be increased. Disabling the Extended Master Secret Extension will allow the TLS resumption to work for those devices. This could be achieved by setting the system property jdk.tls.useExtendedMasterSecret to false.
3	ONVIF 1.7.0	compact1 profile	ONVIF driver is using javax.xml.transform to process the complex type of notifications events. This packages are not part of the ejdk 8 compact1 profile. The library containing the implementation is not in bundle and must be provided manually for the complex type of events to work.
4	OSGi Things Agent 1.2.1	BackupAndRestore	Currently if fim.core bundle is added in the list with providers to restore, it causes instability issues. The latter can be resolved through a restart of things.agent.core bundle.
5	OSGi Things Agent 1.2.1	Invoke operation, set property, security	It is not possible to invoke operation or set property of a feature through the cloud when the security is activated.