The following table provides a summary of issues that were fixed in Release 10.2.0:
# |
Module |
Topic/keyword |
Issue and resolution |
Affects version |
|---|---|---|---|---|
1 |
BACnet 1.2.0 |
Discovery |
The BACnet auto discovery process was not started when the BACnet adapter configuration is updated with property flag discoveryAutoStart enabled. The adapter runtime behaviour was not affected by the configuration changes. Now, it is fixed and the auto discovery process is dynamically started or stopped when the configuration is updated. |
10.1.0 |
2 |
Core 1.4.2000 |
DB Restore Failure, |
Upon a DB restore failure, the DB files were not closed properly. This has been fixed. |
10.1.0 |
3 |
Core 1.4.2000 |
DB Restore with corrupted DB files, |
Restore of corrupt Z-Wave DB files led to a failure and a loss of Z-Wave data. This has been fixed and there is no loss of data. |
10.1.0 |
4 |
Core 1.4.2000 |
Error in ref.Log |
A NullPointerException in com.prosyst.util.ref.Log.setLogLevelConfig() was reported. This was due to some missing checks for the logger's availability when the Configuration Admin is used by the logger. This has been fixed. |
10.1.0 |
5 |
Core 1.4.2000 OSGi 1.8.0 |
Unused java.util.Timer threads remain active |
Some leftover timer threads were noticed after the usage of Configuration Admin and Metatype. This was fixed. |
10.1.0 |
6 |
DECT 2.3.3000 |
RPC server executable not found |
Bundle com.prosyst.mbs.dect.driver.cmbs could not be started on Windows. It was not able to find tcpjsonrpc.exe executable and start the RPC server. As a result the whole DECT module was not functional on Windows. Now the problem is fixed and tcpjsonrpc.exe is found when bundle starts. |
10.0.0 |
7 |
Device Access 3.7.0 |
Log |
Device Access logged error when service HomeZoneConfigAdmin is unrgistered when it has been already unregistered before that. Now this is fixed and error is not logged. |
9.0.0 |
8 |
Device Access 3.7.0 |
Core |
Sometime exception was possible to occur when device was added and the bundle providing the device class is uninstalled at the same time. Now the exception is fixed to not occur anymore. |
9.0.0 |
9 |
Device Access 3.7.0 |
OSS |
Device Access provided license for incorrect library version (bootstrap). The license is fixed to be according the used library version. |
9.0.0 |
10 |
Device Access 3.7.0 |
DB restore |
Device Access marked already configured devices as Not Configured after DB Restore. Now this is fixed and devices remain configured. |
7.4.1 |
11 |
External 1.6.1 |
Unnecessary checkShutdown() calls in org.eclipse.equinox.http.servlet |
There were situations where java.lang.IllegalStateException: Context is already shutdown while uninstalling bundles" would be thrown unnecessarily. This was due to a bug in the org.eclipse.equinox.http.servlet bundle and has been patched. |
9.2.0 |
12 |
External 1.6.1 |
Weaving hooks called twice in org.apache.aries.spifly |
The org.apache.aries.spifly bundle would call weaving hooks twice when activated. This has been patched. |
10.2.0 |
13 |
FIM 2.4.0 |
FIM Metadata remote support |
FIM metadata beans remote support was broken because of outdated restrictions for TypeMetadata representation as map in FIM Util package. The IllegalArgumentException creation is removed in order to allow the metadata string representation. |
9.0.0 |
14 |
Framework 8.6.2001 |
Bundle events |
There was an issue, triggered by a bundle that registers SynchronousBundleListener and resolving the bundle from the bundle event, where some other bundle listeners received bundle events in wrong order. The most common case was receiving RESOLVED event before INSTALLED for the same bundle. The order of dispatching events has now been fixed. |
10.1.0 |
15 |
Framework 8.6.2001 |
Bundle events |
There was a problem, when dispatching bundle events to listeners from already uninstalled bundles, which resulted in NoClassDefFound errors. This has now been fixed. |
10.1.0 |
16 |
Framework 8.6.2001 |
Server script, |
Server scripts for CEE JVM are fixed to include the required jars in bootclasspath. |
10.1.0 |
17 |
Framework 8.6.2001 |
Services, |
There was a problem with getting a service, registered with service factory, from multiple bundles using multiple threads in parallel. This used to break the internal synchronization of service factory invocations in Framework Core and different service instances were returned for the same bundle. This issue has now been fixed. |
10.1.0 |
18 |
Framework 8.6.2000 |
Bundles |
Race condition when refreshing bundle packages, causing the operation to fail, was fixed. |
10.1.0 |
19 |
Framework 8.6.2000 |
Framework storage |
There were references to unsuccessfully installed bundles, left in framework storage, which caused errors and warnings when restarting the server. This is now fixed. |
10.1.0 |
20 |
Framework 8.6.2000 |
Framework security |
Sometimes there was a problem getting stream to resource from a bundle, when server is launched with security. This is now fixed. |
10.1.0 |
21 |
Framework 8.6.2000 |
Resolving, |
Sometimes there was a problem resolving bundles, which import a package with multiple providers and an "uses" clause. This caused subsystem container to not function properly. Resolving is now fixed. |
10.1.0 |
22 |
Framework 8.6.2000 |
URL handler, |
There was a problem handling URLs, associated with framework storage on CEEJ JVM, when a framework instance is launched programmatically via FrameworkLauncher. This is now fixed. |
10.1.0 |
23 |
HAM 5.0.5000 |
Deleting Scene in HAM |
Deleting a Scene Command was breaking HAM Web Console till HAM bundle restart. Now this is fixed. |
9.0.0 |
24 |
History 1.5.0 |
History entries selection with null values |
SQLite read of history entries containing null values has resulted in entries selection failure. Now this is fixed. |
10.0.0 |
25 |
Home Connect 1.3.1000 |
Home Connect OAuth2 Access Token |
A problem in the Home Connect driver implementation prevented extracting the correct authorization code during Home Connect OAuth2 Authorization Code Grant Flow. The process ended with a HTTP 400 (Bad Request) response from the Home Connect server and it was impossible to get an access token for the Home Connect appliances. Parsing of the authorization code is now fixed and the driver can successfully obtain an access token. |
10.1.0 |
26 |
Modbus 1.2.2000 |
Error in restoring |
In some specific client setup a race condition occurred causing a NullPointerException. This was happening only when restoring the Modbus devices during startup. Now if a restore happens before the ModbusManager is completely registered, the restore proceeds without an error. |
9.2.0 |
27 |
Modbus 1.2.2000 |
Character cutoff in |
The last character was missing when reading a String value from registers with odd length of the string. This was due to reversed check for null character in lower/higher bytes of the register. Now this is fixed. |
9.2.0 |
28 |
ONVIF 1.5.0 |
Set Preset operation |
Setting preset without name and preset token fails. The name and the preset token are optional parameters and they are not required. This is now fixed. |
9.0.0 |
29 |
ONVIF 1.5.0 |
Bosch verification plugin |
The Bosch specific verification plugin is used for serial number verification from camera certificate and it is needed only for Bosch cameras. The plugin was checking non-Bosch cameras as well and skips the verification if the serial number is not included. This is now fixed. |
10.1.0 |
30 |
ONVIF 1.5.0 |
GetCapabilities |
GetCapabilities fails when the Network tag is empty in the response. This is now fixed. |
10.0.0 |
31 |
ONVIF 1.5.0 |
ONVIF Firmware Upgrade support |
For Firmware Update support, the FirmwareUpgrade Capability is used, but this refers to the MTOM Deprecated mechanism. The Capability which must be used is HttpFirmwareUpgrade. This is now fixed. |
10.1.0 |
32 |
ONVIF 1.5.0 |
RCP+ Firmware Update |
Device stays with FIRMWARE UPDATING status after canceling the firmware update process for both HDM and FIM for RCP+. This is now fixed. |
10.1.0 |
33 |
ONVIF 1.5.0 |
ONVIF Firmware Upgrade status |
Device stays with FIRMWARE UPDATING status after the firmware upgrade complete until the subscription fails. This is now fixed. |
10.1.0 |
34 |
ONVIF 1.5.0 |
ONVIF Device Access |
Functional Items info such are tags which are cached by Device Access are not saved and default values are used after restore/restart. This is because the ONVIF Device Functional Item was removed on logout, or at re-initialization. The Device Functional Item is no longer removed on logout or re-initialization. |
10.0.0 |
35 |
ONVIF 1.5.0 |
ONVIF WS-Base Notification |
The received events from the device are not processed due to new line characters. This is now fixed. |
10.0.0 |
36 |
OSGi 1.8.1 |
HTTP on CEEJ JVM and Perc VM |
Fixed several issues that prevented HTTP server to start on CEEJ JVM and Perc virtual machines |
10.1.0 |
37 |
OSGi 1.8.1 |
HTTP/2 with Conscrypt on Windows |
Missing permissions prevented the proper starting of HTTP/2 server with Conscrypt ALPN provider under Windows on certain JVM versions. The issue is now fixed. |
10.1.0 |
38 |
OSGi 1.8.1 |
HTTP Session Invalidation |
HTTP Sessions holding authorization objects created by User Admin service were not invalidated when the service disappeared. When using the legacy HTTP service, this resulted in error during the next login attempt. This issue is now fixed and HTTP sessions are correctly invalidated. |
10.1.0 |
39 |
OSGi 1.8.1 |
Logging, SLF4J |
There was issue in SL4J logger, which prevented logs with null message to be recorded correctly. This issue is now fixed. |
10.1.0 |
40 |
OSGi 1.8.1 |
Logging, Restore |
There was an error setting a log level through log service upon/after restore, which happened rarely. This has now been fixed. |
10.1.0 |
41 |
OSGi 1.8.1 |
Subsystem, |
Sometimes there was an error when stopping a subsystem on CEEJ and operation failed. This has now been fixed. |
10.1.0 |
42 |
OSGi 1.8.1 |
Declarative services, |
Sometimes there was a deadlock inside SCR, when multiple components are registered simultaneously, triggered by configuration creation or update. This caused a timeout in component creation thread and component(s) were not enabled. The issue now seems to be fixed. |
10.1.0 |
43 |
OSGi 1.8.1 |
Subsystem demo, |
Sometimes there were bundles left in a transition state(STARTING/STOPPING) right after subsystem demo is installed/uninstalled. This has been fixed and demo behavior is now determined. |
10.1.0 |
44 |
OSGi 1.8.1 |
Event Admin, |
There were some race conditions in Event Admin implementation, which caused some events not to be dispatched. This has now been fixed. |
10.1.0 |
45 |
OSGi 1.8.1 |
Configuration Admin, |
Duplicate factory configurations were created upon Configuration Admin bundle restart. The issue was valid for metadata factory configurations, referring object class definition from another bundle. This has now been fixed and no extra configurations are created. |
10.1.0 |
46 |
OSGi 1.8.1 |
Subsystem |
Sometimes there was a problem reading a signed bundle's manifest, when bundle is packed inside a subsystem archive. This has been observed on OpenJDK 11 and is now fixed. |
10.1.0 |
47 |
OSGi 1.8.1 |
Config Loader, |
Factory configurations are not bound when described via configuration property file used by configuration loader. This is now fixed. |
10.1.0 |
48 |
REST 2.1.2000 |
Error while stopping Rest Publisher bundle |
NoClassDefFoundError was thrown when com.prosyst.mbs.webservices.rest.publisher bundle was stopped while its configuration was being updated. This is now fixed. |
10.1.0 |
49 |
REST 2.1.2000 |
Subscription URL |
Additional "/utf-8" segment was added to subscription URLs, when not encoding the URL. This is now fixed. |
10.1.0 |
50 |
Units 1.2.5000 |
Quantity Web Console editor |
Quantity Web Console editor layout was broken and some of the data was not visible on selecting Units system different than SI. Now this is fixed. |
10.0.0 |
51 |
Util 1.2.2000 |
Error in PackagesManager |
There was a rare NullPointerException which appeared due to a faulty check when analyzing optional package resolution. It is fixed. |
10.1.0 |
52 |
Util 1.2.2000 |
Beans' fields with single character names get capitalized on serialization |
There was some unneeded capitalization of beans' fields with names which were strings with one character upon serialization. This was fixed. |
10.1.0 |
53 |
Util 1.2.2000 |
Beans' null fields disappear on serialization |
If a bean with one or more fields with null values was serialized with com.prosyst.util.json.MappingUtil#serialize, these fields were not present inside the serialized JSONObject. This was fixed. |
10.1.0 |
54 |
WebSockets 1.3.1000 |
Error when stopping |
Missing synchronization sometimes caused NullPointerException to be thrown when stopping WebSockets Push Events Endpoint bundle com.prosyst.mbs.websockets.events.endpoint. This is now fixed. |
10.1.0 |
55 |
Z-Wave 6.2.0 |
Smart Start |
There was a NullPointerException thrown when calling setProvisioningEntry NodeProvisioning Device Item operation. Now the handling of invalid arguments when creating or updating Smart Start Provisioning Entries is improved. |
10.0.0 |
56 |
Z-Wave 6.2.0 |
Smart Start |
The Name and Location information types were not parsed correctly while reading the Z/IP Gateway Smart Start cache, resulting in ArrayIndexOutOfBoundsException. This is now fixed. |
10.0.0 |
57 |
Zigbee 4.10.0 |
OTAU Upgrade End Request status |
During Over the Air Upgrade(OTAU), when an Upgrade End Request was received with status different from SUCCESS the OTAU failed without logging the reason. Now a warning log entry is added to point out the reason for OTAU failure. |
9.0.0 |
Known Issues
The following section provides a summary of issues known in the current release.
System Integrity Protection (SIP) in macOS: Affecting Edge Services version 10.2.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 |
Known Issue |
|---|---|---|
1 |
Automation ESH 5.0.5000 |
FIM Web Console support for Automation ESH functional items – The IoT/FIM support for the deprecated Automation ESH functional items is temporary unstable so the items with UIDs automation:rule:admin, automation:moduletype:admin and automation:ruletemplate:admin could not be opened. However the IoT/Automation ESH is still working so the Web Admin support is available. |
2 |
BACnet 1.2.0 |
Some uncommon and rare BACnet engineering units are not fully integrated within the Units of Measurements module of the Bosch IoT Edge Services. If a BACnet device uses an unsupported BACnet engineering unit, its values will be reported as dimensionless quantities, but the original BACnet engineering unit will still be present as device item attribute. |
3 |
BACnet 1.2.0 |
The module does not provide a BACnet Driver API. The BACnet devices are exposed solely at Device Access level. |
4 |
mBProfiler 6.4.7000 |
Due to bugs 564205 and 562645 found in Eclipse version 4.14 and 4.15: Automatic open of various profiling views like Classes, Objects, Memory Call Tree and etc. causes duplication of session management buttons and also some NullPointerException-s to pop-up. |
5 |
ONVIF 1.3.0 |
ONVIF Discovery is not detecting devices if the local network IP is changed during runtime or by DHCP, therefore the discovery is no longer working, until the ONVIF Core bundle or the framework is restarted. |
6 |
ONVIF 1.5.0 |
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. |
7 |
ONVIF 1.5.0 |
Java is introducing the Extended Master Secret Extension enabled by default after the 8u161 update. Some Cameras which is not supporting 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 setting the system property jdk.tls.useExtendedMasterSecret to false. |
8 |
ONVIF 1.5.0 |
The UID of the functional item for RCP+ firmware update is changed.
This change is backward incompatible. |
9 |
Scripting 1.0.3000 |
As of JDK 15 Nashorn JavaScript engine is no longer available. |