Graphic Hub 3.7.1

• Important: Fixed an issue where the replication server in a cluster setup does not store Viz Pilot data changes as open transactions when running as main and does not copy them to the partner when it is started again (VIZGH-7591). This affects Graphic Hub 3.7.0 only and it is highly recommended to upgrade to 3.7.1.

• Files are closed after a delay (instead of immediately) when a session has finished reading and only has read permissions (VIZGH-7568). This affects Graphic Hub 3.7.0 only.

Graphic Hub 3.7.0

• Upgrade to CodeMeter Runtime 7.40 in the Graphic Hub Bundle Installer (VIZGH-7290) along with an upgrade of the CodeMeter client SDK to 7.40 (VIZGH-7495, VIZGH-7358).

• Graceful emergency shutdown of the Graphic Hub with proper logging, waiting for critical operations to finish and blocking of requests during shutdown (VIZGH-7534, VIZGH-7358).

• Increased rate of synchronized open transactions on a Graphic Hub cluster (main and replication) when recovering (VIZGH-7533).

Graphic Hub REST 2.7.0

• Journal logging capability for the Media Sequencer (MSE) through Graphic Hub REST (VIZGH-7489).

Graphic Hub Terminal 3.7.0

• Perform a fast and secure shutdown of Graphic Hub in case of a Windows shutdown and wait until it is finished with a delay of the Windows shutdown operation (VIZGH-7534, VIZGH-2637, VIZGH-2016).

Graphic Hub 3.7.0, Graphic Hub Terminal 3.7.0

• Removed support to retrieve and use licenses from Hardlock/Sentinel dongles, as announced in previous releases (VIZGH-7491, VIZGH-7493).

• Deadlock monitoring shuts down Graphic Hub now when deadlocks are detected and released to avoid possible follow up issues and corruptions (VIZGH-7537, VIZGH-7536). In addition, it has no influence anymore on main and replication mode or switchback decision making. Added creation of a dump that is included in the Graphic Hub Terminal report to better debug such issues when observed.

• Increased amount of log information in Graphic Hub log file (VIZGH-7536, VIZGH-7537). Now logs the number of rows loaded per table instead of the loaded fields (VIZGH-7539).

• Added the UTC time when scheduled tasks trigger to Graphic Hub Terminal and a note that scheduled tasks always trigger on the server's UTC time, not the client time (VIZGH-7528).

Graphic Hub REST 2.7.0

• Changed default, minimum and maximum values for socket timeouts (from 30, three, 59 seconds to two, one and 30 minutes) and maximum request timeout (from five to 30 minutes) (VIZGH-7513).

Graphic Hub 3.7.0

• Important: Fixed restore of files when an overwrite of an existing file fails (for example, session disconnected while writing) (VIZGH-7525). The original file content was not recovered properly and reported as not restorable. Affects Graphic Hub versions 3.4.0 to 3.6.0.

• Important: Fixed a session cleanup issue that may occur on Viz Pilot requests from Graphic Hub REST that run into timeouts and can cause a memory issue (VIZGH-7426).

• Important: Fixed a possible freeze of the Graphic Hub Main server when recovering open transactions (VIZGH-7520).

• Important: Fixed a possible crash of the Graphic Hub process when multiple sessions try to overwrite or read the same files in parallel, or access referenced files in parallel (VIZGH-7531, VIZGH-7524).

• Important: Fixed several Graphic Hub cluster (main and replication) related issues, especially when running on virtualized environments (VIZGH-7536).

  • Altered startup sequence and decision making for main and replication modes to avoid situations where one of the partners shuts down unintentionally.

  • Configurable timeout and better timeout handling for monitoring requests between Graphic Hubs running in main and replication mode to avoid situations where short interruptions cause a failover or shutdown of one of the instances (especially on virtualized environments).

  • The active session count was removed from the decision making for the current mode and when to switch and is now based on open transactions and switch times. If there are no open transactions the cluster partners just switch to their original modes.

  • Reduced wait time to retrieve cluster state at startup and added proper validation of open transactions on startup.

  • Fixed an issue where sessions were not removed properly on switchback or logoff.

  • Unified Main/Replication logic and processing to avoid status issues during switchback and improved response times.

  • Unified state handling in Graphic Hub to avoid inconsistencies and speed up reaction on certain events (for example, shutdown, recovery, switchback). Improved responsiveness by reduced locking of resources.

  • Cluster partners do not shut down each other anymore. Each decides on its own if a shutdown is needed to improve responsiveness and be more fault tolerant.

  • Reduced request overhead between main and replication partners by introducing a new request that provides all required information for decision making and monitoring.

  • Added functionality to determine if a request is issues by the partner server or the client. Fixed issues where clients still performed requests on the replication server during switchback. Requests are now blocked when clients have not moved to the active main and are still issuing requests to the replication server.

• Resolved issues with WIBU license allocation from a local container with CodeMeter 7.21a or newer (VIZGH-7321).

• Fixed an issue where lock file status is not persisted when failover and switchback happen on a Main/Replication setup (VIZGH-7405).

• Do not start synchronization of open transactions when cluster partners connect again when a shutdown is scheduled (VIZGH-7410).

• Bundle installer failed to install with C++ Redistributable 14.0.24245 on Windows 10 (VIZGH-7498). Fixed by upgrading of the Visual Studio 140-143 redistributable to 14.31.21103.

• Fixed an issue where the Graphic Hub gets unresponsive for some seconds when file writing sessions cannot be reached and are removed due to failed Ping requests (for example, because they are firewalled) (VIZGH-7516).

• Fixed an issue where client requests were accepted during shutdown (VIZGH-7527).

• Fixed a possible crash when a partner server is started and stopped multiple times in a sequence (VIZGH-7540).

• Fixed a possible crash when multiple sessions delete and access the same content in parallel (VIZGH-7543).

• Fixed an issue where corrupted Pilot data fields were not deployable (VIZGH-7517). Added additional logging of defects found on startup (affected rows and fields). Corrupt fields get dummy entries now when starting in safe mode and log entries show which fields were repaired. GH Manager can be used with Pilot Differences to deploy the corrupted content to a different Graphic Hub.

Graphic Hub Terminal 3.7.0

• Fixed an issue where Viz Pilot data elements cleanup task deletes items newer than the selected interval when months are used as interval unit (VIZGH-7503).

Graphic Hub REST 2.7.0

• Important: Fixed an issue where session limits per user get exceeded when timeouts on long running Viz Pilot requests happen (VIZGH-7426).

Graphic Hub Manager 5.7.0

• Important: Fixed an archive export/import issue where Graphic Hub Manager versions 5.5.2 to 5.6.0 export archives that may fail import in Viz Artist, Viz Engine or Graphic Hub Manager import archive context menu (VIZGH-7484, VIZGH-7412). If the import fails, those archives can be imported in the Graphic Hub Manager archive panel based import as workaround.

Graphic Hub ImEx Agent 1.7.0

• ImEx Agent based import failed when Graphic Hub REST is configured on Main/Replication and only Replication is running (VIZGH-7494).

Hardware and Software Compatibility

For details on hardware, operating systems and browser requirements please refer to the System Requirements in the Graphic Hub Administrator Guide.

For details on compatibility when the Graphic Hub is used as a Viz Pilot data back end, see Viz Pilot Database Management in the Graphic Hub Administrator Guide.