Skip to content
New issue

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

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

Already on GitHub? # to your account

FISH-8888 ClearCache command rest endpoint corrected #6850

Conversation

NotedSalmon
Copy link
Contributor

FISH-8888 clear-cache command endpoint incorrect.

Description

I changed the parameter name to cache-name as the previous key was already being used which resulted in an error.

Important Info

Blockers

Testing

New tests

Testing Performed

Tested using ./asadmin start-domain --debug domain1. Got the name of a cache from - localhost:4848/management/domain/list-caches and cleared successfully.

Testing Environment

Documentation

Notes for Reviewers

I changed the parameter name to cache-name as the previous key was already being used which resulted in an error.
@breakponchito
Copy link
Contributor

Jenkins test please

Co-authored-by: Andrew Pielage <pandrex247@hotmail.com>
Copy link
Member

@Pandrex247 Pandrex247 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still seem to get the error listed on the Jira issue.

WSL, Zulu Java 11.0.23, Maven 3.9.8

Cannot find cacheName in clear-cache command model, file a bug
injection failed on fish.payara.nucleus.hazelcast.admin.ClearCache.cacheName with class java.lang.String

@NotedSalmon NotedSalmon merged commit 3ab0e0c into payara:main Aug 5, 2024
1 check passed
Pandrex247 pushed a commit to Pandrex247/Payara that referenced this pull request Aug 13, 2024
…-rest-endpoint-incorrect

FISH-8888 ClearCache command rest endpoint corrected
@NotedSalmon NotedSalmon deleted the FISH-8888-clear-cache-rest-endpoint-incorrect branch September 19, 2024 11:31
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants