Summary LLS in Linux/Windows listening to the 8080 port as well as the configured port. This lets LLS respond on both the configured port and the 8080 port.  Symptoms LLS also listens to the 8080 Port along with the configured port. The 8080 port is opened by Springboot/undertow. This also blocks running multiple instances of LLS on a single machine. Steps to Reproduce Install LLS on the Linux/Unix operating system. Start LLS and check for the open port for the LLS process ID.  netstat -anp | grep PID Workaround No Workaround as of now. Fix Version and Resolution The fix will be released in the 2024.09 LLS release.  ... View more

Summary LLS set up in HTTPS mode is unable to start when an obfuscated keystore password is used in local-configuration.yaml configuration file.  The issue is being observed in LLS 2024.06 version onwards. Symptoms When LLS is configured to run in HTTPS mode with a certificate , the keystore password needs to be passed on to the local configuration.yaml config file. The keystore password can be obfuscated/hashed using the below  java -jar flexnetls.jar -password <password> If the obfuscated keystone password is used on the local-configuration.yaml , the LLS is unable to start or install as a service. The issue occurs in both console mode and running as a service.  Below error is thrown by LLS :  2024-08-06T07:54:55,974Z WARN  - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'undertowServletWebServerFactory' defined in com.flexnet.glservice.UllsConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate Steps to Reproduce Produce producer-settings.xml and configure local-configuration.yaml to run LLS in HTTPs mode. Obfuscate the keystore password using java -jar flexnetls.jar -password <password> Use the obfuscated password as the keystore password in the local-configuration.yaml HTTPS in section. Attaching a screenshot of the configuration.   local-configuration.yaml HTTPS-in configuration  Start LLS in console mode or install it as a service. LLS will throw an error of "Unable to start web server"     Workaround Currently workaround for running LLS in HTTPS mode is to use the keystore-password as plaintext and not obfuscated in the local-configuration.yaml config file. example :  keystore-password: keystorepassword start the LLS in console mode or installs as a service.  Otherwise, LLS 2024.05 can be used. Fix Version and Resolution The bug is fixed in the 2024.08 release of LLS.  ... View more

Summary After installing the 2023 R1 and upgrading the FNO, CLS, and UAS databases from an older FNO version, attempting to preview available features for a device from an FNE.NET KIT results in a "Back Office Server Error". The error code is [1,7E6,9,0[7000001C,7100002E,250137]]. Symptoms When trying to use the FNE .NET Toolkit for Capability Request Previews the error below screenshot is thrown. The error describes an issue with an un-supported datatype on the table gls_feature. The DB used here is AWS RDS SQL Server Standard Edition. Steps to Reproduce 1. Prepare the Environment: Import a customer database that has not been upgraded to the latest version. 2. Upgrade CLS Database: Access the FNO setup page:  "http://localhost:4321/flexnetsetup" Use the "Manage Schema" option for the CLS database. 3. Deploy and Start Services: Deploy the FNO, UAS, and LFS services. Start the FNO service, ensuring it points to the recently upgraded customer database (not the original, non-upgraded one). 4. Trigger the Error: Use the .NET FNE KIT to send a "Preview Capability Request".  Expected Result: The .NET FNE KIT should show the available features Results we are getting: The .NET FNE KIT is throwing an error.   Workaround The FNO upgrade scripts fail to upgrade the data types of a few columns on the table "gls_feature". TEXT datatype of a column is deprecated in the SQL server and some of the versions of SQL server don't support having distinct TEXT fields. Changing the columns with TEXT datatype to Varchar(Max) is recommended.  The below steps are performed on the DB. Check if ALLOW_SNAPSHOT_ISOLATION is on for clsdb or not The below query can be used to check the same :  SELECT snapshot_isolation_state_desc from sys.databases where name='clsdb'; If not enabled use the below query to enable the same : ALTER DATABASE clsdb SET ALLOW_SNAPSHOT_ISOLATION ON; In this case, the ALLOW_SNAPSHOT_ISOLATION was off for this DB and we had to enable to make changes to the table structure of dbo.gls_feature Change datatypes for a few columns on table dbo.gls_feature Kindly execute the below queries : ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN vendor varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN issuer varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN issued datetime; ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN notice varchar(MAX); ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN serialnumber varchar(MAX);   ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN starts datetime; ALTER TABLE clsdb.dbo.gls_feature ALTER COLUMN expiry datetime; Fix Version and Resolution The BUG will be fixed in future releases.  ... View more