Release Notes 1.1.3.4 LTS
Metadata
This release documentation version 1.0.
| Release | 1.1.3.4 LTS |
|---|---|
| Release date | 2024-05-24 |
| Release type | Full release |
| Future | LTS (Long Term Support) |
| Server version | 1.1.3.4+1.1.3.4-LTS-11730aab |
| Log Server version | 1.1.3.4+1.1.3.4-LTS-18e68458 |
| HostScreen Server version | 1.1.3.4+1.1.3.4-LTS-d78bf7ee |
| Web Terminal Hub version | 1.1.3.4+1.1.3.4-LTS-cb356113 |
| Web Terminal Client version | 1.1.3.4+1.1.3.4-LTS-6693d7bc |
| Management Console | 1.1.3.4+1.1.3.4-LTS-faa9c25d |
| Log Viewer | 1.1.3.4+1.1.3.4-LTS-dd17df53 |
.NET Platform
| .NET Release | 8.0.5 |
|---|---|
| .NET Runtime | 8.0.5 |
| ASP.NET Core Runtime | 8.0.5 |
| Notable changes | Link |
Web Terminal Client Renderer File Names (checksum)
Location: Program Files\Flynet\Jubilant\WebTerminal\web
| renderer.2b40fffc4614a3bfab13.js | renderer.4b7269853ded7ff1a8af.js |
| renderer.4e675a3d02e2602145fe.js | renderer.7b60e0ba28d5470bdbc8.js |
| renderer.8e1c52fae1486d84b902.js | renderer.52ea93465c33f02eaad9.js |
| renderer.52ea93465c33f02eaad9.js.LICENSE.txt | renderer.854e846020ff37bd1c2d.js |
| renderer.854e846020ff37bd1c2d.js.LICENSE.txt | renderer.978ba985dba414cac7f7.js |
| renderer.b6e91dce7ab74396b284.js | renderer.e222fed8fcb653af1aac.js |
Upgrade Recommendations
This upgrade for LTS is recommended for security and high priority fix reasons.
Security Notes
This upgrade for LTS is recommended for security reasons.
.NET Security
An upgrade to .NET 8.0.5 in this release of Jubilant includes security updates. Maximum severity: Important. Please see these notable changes.
Node Packages Security
An upgrade to Node Package react-scripts (web development) includes security updates. Maximum severity: High. See WTC.101.
High Importance Fix Notes
This upgrade to LTS is recommended for high importance fix reasons.
Several improvements have been made to a core technology used in Jubilant. This is around shared memory and mutex. In previous versions of Jubilant, in rare cases, it was possible that the IIS worker process and/or Jubilant HostScreen Server could consume high CPU which could result in loss of Jubilant service.
Please see HSB.9, HSB.10 and HSB.10.
In this Release
New
There are never any new features in LTS releases.
Fixes
| Source ID | LTS ID | Protocols | Description |
|---|---|---|---|
| HSB.8, HSB.9, HSB.10 | HSB.12 | All | Shared memory and mutex fixes to resolve rare high cpu usage for LTS. |
| HSS.45 | HSS.46 | 3270 | HostScreen Server integration into shared memory and mutex fixes for LTS. |
| WTH.13 | WTH.15 | 3270, 5250 | A session could become locked due to unavailability of shared memory objects under extremely rare conditions fix for LTS. |
| HSS.30 | HSS.47 | All | The HostScreen Server Session Manager could fail controlling and reporting on session state fix for LTS. |
| HSS.33 | HSS.48 | All | TLS connections failed with valid server certificate fix for LTS. |
| HSS.41 | HSS.49 | All | The Management Console incorrectly offered the TNVT connection type fix for LTS. |
| HSS.44 | HSS.50 | 5250 | Read Screen operation failed when screen is 27 x 132 fix for LTS. |
| WTC.98 | WTC.100 | All | Font scaling of larger screens could have resulted in squashed text fix for LTS. |
Security
| ID | LTS ID | Protocols | Description |
|---|---|---|---|
| WTC.101 | WTC.104 | All | Update to node packages to remove high vulnerabilities fix for LTS. |
| .Net 8.0.5 | All | See .Net Security Notes. |
Change Notes
Fixes
HSB.8 - Server and session recovery from crashed and abandoned shared memory threads
When a server or session process encounters abandoned mutex, Jubilant takes steps to remedy the issue to allow the server or session to continue functioning.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSB.9 - Shared memory allocation could fail when IIS or sessions failed unexpectedly
Shared memory allocation could fail because of a crashed session, dead server process or unexpectedly lengthy logging events. Jubilant now takes steps to remedy this issue, allowing the server or session to continue functioning.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSB.10 - Shared memory flags could end up in bad state causing high CPU
Shared memory flag control and release could end up invalid, causing server or session processes to crash which could ultimately bring the server down. This fix removes the scenarios where this can happen. HSB.8 and HSB.9 take steps that if does still happen, the server is able to recover.
In previous versions of Jubilant, failure would often manifest itself has high CPU usage in the IIS worker of HostScreen Server processes.
HSS.45 - Updated 3270 Adapter to use new shared memory ownership model
Updated the HostScreen Server 3270 Adapter to use fixed shared memory model. See HSB.8, HSB.9 and HSB.10 for more details.
HSS.30 - The HostScreen Server Session Manager could fail controlling and reporting on session state
The Session Manager in the HostScreen Server could fail to start or report the state of running sessions correctly under high load.
In previous version of Jubilant, failure would often manifest itself as failed attempts to connect a session and the Management Console being unable to list active sessions.
HSS.33 - TLS connections failed with valid server certificate
Telnet over TLS connections could fail if configured to only accept valid server certificates.
In the previous version of Jubilant, failure would often manifest itself with the logged error: Server validation SSL policy errors: RemoteCertificateNameMismatch.
HSS.41 - The Management Console incorrectly offered the TNVT connection type
In the previous version of Jubilant, it was possible to select TNVT as a the connection type for a Host Definition. This is not a valid connection type.
A new version of Jubilant will offer TNVT in the near future.
HSS.44 - Read Screen operation failed when screen is 27 x 132
In previous versions of Jubilant, a 5250 Read Screen operation on a 27 x 132 screen could result in an exception:
"Exception": {
"Message": "Index was outside the bounds of the array.",
"StackTrace": " at Flynet.Jubilant.HostScreen.Server.ScreenBufferAdapter.TN5250ScreenBufferAdapter.HandleReadScreenOperation(ReadScreenOperation operation)"
}
This is resolved in this version of Jubilant.
WTC.98 - Font scaling of larger screens could have resulted in squashed text
In previous versions of Jubilant, it was possible that fonts on screens larger than 24 x 80 could appear squashed.
This fix ensures that fonts are scaled and spaced appropriately for the screen dimensions.
WTH.13 - A session could become locked due to unavailability of shared memory objects under extremely rare conditions
Under very rapid update conditions, or when an update was taking a very long time, there was an extremely small chance that a session could become stuck with no reason reported in logs or sent to the front-end.
This rare locking can now occur in even less situations, with a proper log entry and client messages created if it does.
The client facing message error would be along the lines of:
"Unable to obtain control of session"
"The Web Terminal has been unable to take control of the session. Your session may be lost."
"MergeScreenUpdate has been unable to take control of the ScreenBuffer Mutex."
The logged error would be along the lines of:
"ScreenBuffer Control Failure"
"Unable to gain control of the shared ScreenBuffer."
Security
WTC.101 - Update to node packages to remove high vulnerabilities
Removed reference to node package react-pdf ^6.2.1 as it is no longer used.
Upgraded node package react-scripts from ^3.0.1 to ^5.0.1.
LTS Merge Notes
Fixes
HSB.12 - Shared memory and mutex fixes to resolve rare high cpu usage for LTS
This is a set of fixes relating to shared memory, mutex and signalling. This fix resolves issues where under rare circumstances, the IIS web worker process and/or the HostScreen Server could consume considerable CPU and Jubilant would be unreliable.
See HSB.8, HSB.9 and HSB.10 above.
HSS.46 - HostScreen Server integration into shared memory and mutex fixes for LTS
This is the LTS implementation of HSS.45.
WTH.15 - A session could become locked due to unavailability of shared memory objects under extremely rare conditions fix for LTS
The LTS implementation of WTH.13.
HSS.47 - The HostScreen Server Session Manager could fail controlling and reporting on session state fix for LTS
The LTS implementation of HSS.30.
HSS.48 - TLS connections failed with valid server certificate fix for LTS
The LTS implementation of HSS.33.
HSS.49 - The Management Console incorrectly offered the TNVT connection type fix for LTS
The LTS implementation of HSS.41.
HSS.50 - Read Screen operation failed when screen is 27 x 132 fix for LTS
The LTS implementation of HSS.44.
WTC.100 - Font scaling of larger screens could have resulted in squashed text fix for LTS
The LTS implementation of WTC.98.
Security
WTC.104 - Update to node packages to remove high vulnerabilities fix for LTS
The LTS implementation of WTC.101. Also see Node Package Security notes.
Installation
Fresh Install
Please see the Jubilant Admin Manual for Fresh Install Instructions.
Upgrade
Note
Please note the specials steps below if upgrading from a 1.0.x build to a 1.1.x or later build.
If upgrading from Jubilant 1.0.x to 1.1.x extra steps must be carried out before and after the install steps below.
Upgrade is carried out using Jubilant scripts.
- Unzip the installer into a folder.
- Close any web browsers.
- Close any Services windows.
- Open PowerShell ISE as Administrator.
- In the PowerShell ISE open the Jubilant PowerShell script: "JubilantUpdate.ps1".
- Run the required script by pressing the green play / run script button on the toolbar.
- The upgrade of Jubilant is complete.
If this is an upgrade from Jubilant 1.0.x to 1.1.x, make sure the after install steps are also completed.
Version Validation
Find out how to validate the installed version.