Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds date for changelog for apama-in-c8y-20241104-Fixed-a-potential-deadlock #2611

Merged
merged 2 commits into from
Nov 21, 2024
Merged

Adds date for changelog for apama-in-c8y-20241104-Fixed-a-potential-deadlock #2611

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
de9d560
Adds dummy date
jato-c8y Nov 6, 2024
d9224a4
Update version and release date
skom-c8y Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...potential-deadlock-when-a-large-number-of-requests-are-waiting-to-be-flushed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
date:
date: 2024-11-21
title: Fixed a potential deadlock when a large number of requests are waiting to be flushed
change_type:
- value: change-VSkj2iV9m
Expand All @@ -12,6 +12,6 @@ build_artifact:
- value: tc-KXXmo2SUR
label: apama-in-c8y
ticket: PAM-35075
version: 25.298.0
version: 25.311.0
---
When using a large number of client connections with the `client.numClients` tenant option, there was a potential deadlock when a large number of requests were waiting to be flushed. This has been fixed.