Skip to content

VQConnector-VCC-1.5.8
Compare
Choose a tag to compare
@zeeshanalikhan15 zeeshanalikhan15 released this 03 Dec 03:57
v1.5.8
01e6caa
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Update:

- Update virtualQ.Net SDK:

Reason: virtualQ.Net SDK was not ablr to support latest 1.2 version of TLS for virtualQ communication.
Requirement: Ad support for TLS 1.2
Solution: Connector will now support TLS 1.2 with virtualQ.NET latest version: 1.1.1
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-40

- Database disconnection on Azure:

Reason: Client is using Azure DB cluster and sometime connection drop with connector.
Requirement: Connection should not drop.
Solution: Connector will now be able to better communicate with Azure db cluster
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-7

- Database instance goes null:

Reason: Sometimes database instance goes null in connector.
Requirement: find the casue of this and remove it.
Solution: Removed the issue and now db instance will not go null.
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-37

- Duplicate callbacks:

Reason: Sometimes database has multiple callback entries from connector.
Requirement: find the casue of this and remove it. Although unable to reproduce in lab.
Solution: Removed the issue and now db will have only on callback per caller. Also added extra logging in case if issue sill persists.
Ticket: https://virtualq.atlassian.net/jira/software/projects/CON/boards/11?selectedIssue=CON-55

Assets 3
Loading