This error is seen in the oc.log file.
2021-09-30 16:52:15,499 ERROR (EE-ManagedThreadFactory-default-Thread-3) Viptela_b3f1725b-f3f8-4e9f-8c4e-126ac854e788=Performance Poll [OC_ACQUISITION] TimProcessFunction 182 Failed to invoke plugin ViptelaHttpFunction from ViptelaHttpFunction Acquisition Viptela tunnel statistics: java.lang.reflect.InvocationTargetException
Caused by: java.lang.NegativeArraySizeException
This error is seen in the server.log file. It is a frequently repeated Notification related error causing server.log file growth. It also is a contributor to possible performance issues with swagger web UI access.
2021-10-04 16:36:16,479 ERROR [org.jboss.as.ejb3.invocation] (Thread-15 (ActiveMQ-client-global-threads)) WFLYEJB0034: EJB Invocation failed on component NotificationManager for method public void com.ca.em.sdn.gateway.broker.core.notification.NotificationManager.processResponse(com.ca.em.sdn.gateway.broker.plugins.NormalizedNotificationResponse): javax.ejb.EJBTransactionRolledbackException: Could not create a session: IJ000460: Error checking for a transaction
Caused by: javax.jms.JMSRuntimeException: Could not create a session: IJ000460: Error checking for a transaction
Caused by: javax.jms.JMSException: Could not create a session: IJ000460: Error checking for a transaction
Caused by: javax.resource.ResourceException: IJ000460: Error checking for a transaction
Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff0ab94257:-27344245:615b2049:7da11 status: ActionStatus.ABORT_ONLY >, owner=Local transaction context for provider JBoss JTA transaction provider)
This error is seen in the gateway.log file. This error is repeated a great deal and is unnecessarily filling up the logs on the server potentially causing disk space problems.
2021-10-04 15:33:19,093 ERROR (Thread-5 (ActiveMQ-client-global-threads)) [NOTIFICATION_PERSISTENCE_SERVICE] NotificationPersistenceService 381 Unable to complete notification persistence action. Reason: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not prepare statement , For more details enable the TRACE mode
Very large Viptela environment responding with very large data set triggers the errors from VNA.
All supported DX NetOps Performance Management and Virtual Network Assurance versions r21.2.6 and earlier
Errors related to environment size. Upgrade to the r21.2.7 or newer releases to obtain code changes from defect DE516716 that resolve these errors.