So far the SDK provided a messaging API that was not thread-safe (i.e. goroutine-safe). Additionally the SDK provided a MutexAPI which made it thread-safe at the cost of removed concurrency possibilities. The changes implemented in this commit replace both implementations with a thread-safe connection pool based solution.
The api gateway is a SDK user that requires reliable high performance send capabilities with a limit amount of amqp connections. These changes in the PR try address their requirements by moving the responsibility of connection management into the SDK. From this change other SDK users will benefit as well.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-62
* logging all errors related to the session and connection close
* closing the sender properly not only in case of an error
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-61
Updates library versions to fix a reported vulnerability in a test dependency and to use latest versions. Adds a convenience method to set the built flag in the builder without constructing an event.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-40
Concurrent invocations on the SequenceNumberGenerator can lead to gaps and duplicate sequence numbers. To fix the issue an internal "backlog" is added as a buffer. If a new number is requested the "backlog" is checked first before creating a new number.
The "host" HTTP-Header is filtered out hide internal information.
The following build dependencies have been updated:
- Go has been updated to version 1.23.3.
- Golanglint-ci has been updated to version v1.62.0.
- Buf has been updated to version v1.46.0
The following library dependencies have been updated:
- go.opentelemetry.io/otel has been updated to version v1.32.0
- go.opentelemetry.io/otel/trace has been updated to version v1.32.0
Related work items: #696569
