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.

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

pom.xml uses incorrect/outdated connection cache size env var name #762

Closed
andrewazores opened this issue Dec 1, 2021 · 0 comments · Fixed by #763
Closed

pom.xml uses incorrect/outdated connection cache size env var name #762

andrewazores opened this issue Dec 1, 2021 · 0 comments · Fixed by #763
Assignees
Labels
bug Something isn't working test

Comments

@andrewazores
Copy link
Member

No description provided.

@andrewazores andrewazores added bug Something isn't working test labels Dec 1, 2021
@andrewazores andrewazores self-assigned this Dec 1, 2021
andrewazores added a commit to andrewazores/cryostat that referenced this issue Dec 1, 2021
Remove connection cache size/TTL config, which used an incorrect/outdated cache max size env var name, to better reflect a standard Cryostat deployment using default cache settings (unlimited size, 10s TTL)

Fixes cryostatio#762
andrewazores added a commit to andrewazores/cryostat that referenced this issue Dec 1, 2021
Remove connection cache size/TTL config, which used an incorrect/outdated cache max size env var name, to better reflect a standard Cryostat deployment using default cache settings (unlimited size, 10s TTL)

Fixes cryostatio#762
andrewazores added a commit to andrewazores/cryostat that referenced this issue Dec 1, 2021
Remove connection cache size/TTL config, which used an incorrect/outdated cache max size env var name, to better reflect a standard Cryostat deployment using default cache settings (unlimited size, 10s TTL)

Fixes cryostatio#762
andrewazores added a commit to andrewazores/cryostat that referenced this issue Dec 6, 2021
Remove connection cache size/TTL config, which used an incorrect/outdated cache max size env var name, to better reflect a standard Cryostat deployment using default cache settings (unlimited size, 10s TTL)

Fixes cryostatio#762
andrewazores added a commit that referenced this issue Dec 7, 2021
* fix(rules): signal connections opened by rules may be immediately closed

Related to #756

* fix(pom): remove itest connection cache size config

Remove connection cache size/TTL config, which used an incorrect/outdated cache max size env var name, to better reflect a standard Cryostat deployment using default cache settings (unlimited size, 10s TTL)

Fixes #762

* fix(rules): do not create cached connections for automated rules

Related to #756

Automated rules processing will reuse existing cached connections if available. If none are available then a new connection will be created and NOT cached, in order to avoid automated rules causing evictions of cached connections for other interactive clients

* remove unnecessary toString()

* re-add null guards

* allow TargetConnectionManager to handle closing connection

* fix(activereports): fix classcastexception

* fix(itest): correct /api/v1 to /api/beta in JWT asset download tests

* test(pom): set itest cache TTL to 60s

* feat(tcm): listen for target LOST events and invalidate from cache

* update README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant