SQL exceptions in /opt/CA/VNA/wildfly/standalone/log/server.log with respect to Velocloud

Products

• Network Observability

Issue/Introduction

Several Sql Exceptions are being seen in VNA server.log

2025-04-15 08:05:01,380 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EE-ManagedExecutorService-persistenceTaskExecutor-Thread-1) Data truncation: Data too long for column 'description' at row 1

2025-04-15 08:05:01,381 ERROR [org.hibernate.internal.ExceptionMapperStandardImpl] (EE-ManagedExecutorService-persistenceTaskExecutor-Thread-1) HHH000346: Error during managed flush [org.hibernate.exception.DataException: could not execute statement]

2025-04-15 08:05:01,875 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (Thread-298 (ActiveMQ-client-global-threads)) Column 'notificationId' cannot be null
2025-04-15 08:05:01,875 ERROR [org.hibernate.internal.ExceptionMapperStandardImpl] (Thread-298 (ActiveMQ-client-global-threads)) HHH000346: Error during managed flush [org.hibernate.exception.ConstraintViolationException: could not execute statement]

Environment

DX NetOps VNA 24.3.7 version

Velocloud 6.2.0.x

Cause

Reference 

https://techdocs.broadcom.com/us/en/vmware-sde/velocloud-sase/vmware-velocloud-sd-wan/6-2/vmware-velocloud-sdwan-620-release-notes.html

Fixed Issue 157545: Sequential IDs were omitted from event query results to maintain consistency across MySQL and ClickHouse data sources.

A new system property events.mysql.return.id is introduced to control the inclusion of MySQL sequential IDs in event query results. When 

events.mysql.return.id  is enabled (set to true), event queries within the past month will include both the sequential IDs and logical IDs.

Event queries exceeding one month will include logical IDs for all events, but sequential IDs will only be present for events within the last one month.

Data older than one month is sourced from ClickHouse, which does not have sequential IDs.

 

Resolution

Set the parameter events.mysql.return.id=true in the Velocloud configuration to ensure the necessary ID values are returned correctly during event persistence.

Upgrade Velocloud to version 6.2.0.4, which addresses the identified issues and includes necessary fixes for proper event handling and persistence.