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

Fix #25258 No message defined on setting invalid pool name of JDBC resource #25259

Merged

Conversation

dmiya3
Copy link
Contributor

@dmiya3 dmiya3 commented Dec 2, 2024

After fixed:

# /opt/glassfish7-fixed/glassfish/bin/asadmin set resources.jdbc-resource.jdbc/__default.pool-name=MissingPool
remote failure: Could not change the attributes: Constraints for this JdbcResource configuration have been violated: on property [ pool-name ] violation reason [ Invalid pool name, check whether the pool exists. ]
Constraints for this JdbcResource configuration have been violated: on property [ pool-name ] violation reason [ Invalid pool name! Check whether the pool exists. ]
Command set failed.

Signed-off-by: dmiya3 [email protected]

@pzygielo
Copy link
Contributor

pzygielo commented Dec 2, 2024

Just for reference other occurrences:

resourceref.invalid.poolname=Invalid pool name! Check whether the pool exists.

resourceref.invalid.poolname=Invalid pool name! Check whether the pool exists.

So after this, we'll have it 3 times.

@pzygielo pzygielo added this to the 7.0.20 milestone Dec 2, 2024
@pzygielo pzygielo merged commit 1091ef4 into eclipse-ee4j:master Dec 2, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No message defined on setting invalid pool name of JDBC resource
2 participants