|
|
|
|
|
Released: August 7, 2020
End of life: April 1, 2021
This micro release improves logging and performance, resolves several issues, and includes a couple of changes described below.
Resolved issues
# |
Module version |
Topic/keyword |
Issue and resolution |
Affect version |
|---|---|---|---|---|
1 |
Core 1.3.8 |
Log |
The log level of a com.prosyst.util.ref.Log instance was not correctly set if a system property, as <bundle_symbolic_name>.level or <bundle_symbolic_name>.printLevel was defined. Now this is fixed and such properties are considered. |
9.3.3 |
2 |
Core 1.3.8 |
Log |
Sometimes there was an error when closing a Log instance. This has now been fixed. |
9.3.3 |
3 |
Core 1.3.8 |
DB read error |
There was an error reading corrupted data base, preventing the remaining content to be retrieved. This is now fixed and correctly written content is read successfully. |
9.3.3 |
4 |
Config Tree 2.3.3004 |
Configuration Admin |
There was a rare race condition with configuration becoming bound to configtree.cm when not bound previously. Now it is fixed in Config Tree CM. |
9.3.0 |
5 |
Framework 8.5.5 |
Resolving |
There was a problem getting the correct bundle wiring, when dynamic imports are used. Now this is fixed. |
9.3.3 |
6 |
Framework 8.5.5 |
Framework services, |
There was a possible deadlock when concurrently stopping a bundle and unregistering service(s). Now this has been fixed. |
9.3.3 |
7 |
Home Connect 1.2.1003 |
Wrong device status |
In certain cases, especially after restart of the OSGi framework, it was observed that the Home Connect device was reported by the adapter with the wrong NOT_INITIALIZED status instead of the correct ONLINE one. This is now fixed and status report should be correct. |
9.3.0 |
8 |
OSGi 1.5.3 |
Subsystems |
Bundles from subsystems were started upon subsystem bundle startup, which altered the correct order when the image is started. This is now fixed and bundles are started in the order defined in boot files. |
9.3.3 |
9 |
OSGi 1.5.3 |
Event Admin |
There were synchronization issues, causing some events not to be dispatched. Synchronization is now fixed and events are properly dispatched. |
9.3.3 |
10 |
OSGi 1.5.3 |
Declarative Services |
Sometimes service.pid property of a SCR component had a wrong value – the component name. This has now been fixed and its value is derived by the component configuration. |
9.3.3 |
11 |
OSGi 1.5.3 |
code 401 Unauthorized on |
There was a race condition in HTTP bundle startup, which resulted in status code 401 Unauthorized to be returned for resource requests while the bundle had not been yet fully started. The race condition is now fixed. |
9.3.3 |
12 |
OSGi 1.5.3 |
NullPointerException in |
There was a NullPointerException thrown in HTTP Whiteboard Service, when a servlet was registered while there were no HTTP Services available. The issue is now fixed. |
9.3.3 |
13 |
Z-Wave 5.0.11 |
Door Lock Operation |
Unsolicited Door Lock Operation and Door Lock Configuration reports were not handled properly in the DoorLock device class instance. As a result, both corresponding properties were not updated as expected. This is now fixed. |
9.0.0 |
14 |
WebSockets 1.1.9 |
Message loss at |
There was a race condition on connection opening. It could cause a message loss, when the message was sent right after the connection was opened. Now this is fixed. |
9.3.3 |
Known issue
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).
Other changes
Database 3.1.1001
The Database module now includes the SQLite database with version, updated to 3.31.1.
Home Connect 1.2.1003
As a result of the improved logging and implementation, any HTTP responses with codes 4xx/5xx are logged as ERROR messages. All HTTP requests as well as the other HTTP responses are logged as DEBUG messages.