BcsService

BcsService 3.6.x for BCS 6.x

Dependencies

BcsService 3.6.x isn't compatible with BCS 5.x

Known issues

• Recommendation to all customers. For already existed BCSS configurations, reduce parameter FileHandlingResultKeepTime in "Service" section from 60000 (old default value) to 5000 to avoid out of memory. New BCSS versions set it to 5000 in new configurations by default
• If client locked BCS node and then unexpected terminated (e.g. killed in Task Manager) locked node will be unlocked only after client connection inactivity timeout is exceeded
• Full name in DigaSystem must be always filled and be unique by every user. Otherwise, isn't possible to set properly speaker & speaking speed in broadcast list

Fixed Vulnerabilities

• [OIA-932] Preventing grant of access to BCS with using any password for user if user with the same login already authenticated by service

New features

• Calculate loudness state for metadata from BCS notifications. Warning! Using this feature can be very unperformable by slow hardware
• Direct WebSocket communication with BCS
• Check minimum required BCS version
• Service can be started before and after BCS
• Handle delayed DigaSQL initialization by autostart as Windows service. Initialization by autostart can be up to 10 seconds longer
• Compatibility with more strict path processing rules after .NET security update
• Active scan WebSocket clients to identify dead connections
• Performance optimization by BCS events handling
• Human-readable error message if BCS 6.x has WebSocket implementation incompatible with .NET WebSocket client
• Separate handling out of memory workflow
• Memory consumption watcher

Fixed Issues

• Prevent memory leak by closing WebSocket connection
• SGU-5440: Deallocate failed file handling task
• SGU-5440: Reduce default keep time for values from file handling job result to prevent out of memory
• SGU-5446: Release file handling resources immediately after task is done
• SGU-5446: Prevent potential race condition by file handling task releasing
• SGU-5446: Minimize to use number of BCSHelpers file handling task to update speaker for the whole show
• Preventing race conditions when connection initialization to BCS
• SGU-5033: Properly handle OIDC connection request if the user matched to OIDC token was already logged
• SGU-5033: Send notifications to clients via internal queue to prevent stopping receiving BCS notifications while loudness calculation
• SGU-5268: Send notifications to clients if notification was initiated on higher level as notified node only with affected BCS metadata
• SGU-4672: More clear error messages
• No unnecessary day initialization when reading special locations in BCS program
• SGU-5546: Handle delayed DigaSQL initialization by slow workstations
• SGU-5531: Check all WebSocket connections, even if one or more connections have no ping / pong mechanism

BcsService 3.5.x BCS v5.x

Dependencies

BcsService 3.5.x is compatible with the BCS 6.x. but only with x32 version and if the BCS is configured to use the old communication method

Known issues

• Recommendation to all customers. For already existed BCSS configurations, reduce parameter FileHandlingResultKeepTime in "Service" section from 60000 (old default value) to 5000 to avoid out of memory. New BCSS versions set it to 5000 in new configurations by default
• If client locked BCS node and then unexpected terminated (e.g. killed in Task Manager) locked node will be unlocked only after client connection inactivity timeout is exceeded
• Full name in DigaSystem must be always filled and be unique by every user. Otherwise, isn't possible to set properly speaker & speaking speed in broadcast list

Fixed Vulnerabilities

• OIA-932 - Preventing grant of access to BCS with using any password for user if user with the same login already authenticated by service

New features

• OIA-1092: Information about connections cache & identifiers cache
• OIA-1092: Memory consumption watcher

Fixed Issues

• SGU-5446: Release file handling resources immediately after the task is done
• SGU-5446: Prevent potential race conditions by file handling task releasing
• SGU-5446: Information about adding/removing file handling tasks in cache in debug log
• SGU-5446: Minimize to use a number of BCSHelpers file handling tasks to update the speaker for the whole show
• Human-readable error messages if request to BCS via IBCS.dll failed by file handling
• OIA-1026: Allow to copy nodes into Jingles, DayTemplates, ShowTemplates, Preproduction