[
https://issues.apache.org/jira/browse/CASSANDRA-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14687:
----------------------------------------
Status: Patch Available (was: Open)
||branch||utests||dtests||
|[branch|https://github.com/beobal/cassandra/tree/14687-trunk]|[utests|https://circleci.com/gh/beobal/cassandra/398]|[vnodes|https://circleci.com/gh/beobal/cassandra/399]
/ [no vnodes|https://circleci.com/gh/beobal/cassandra/397]|
> Revert parameterization of AuthCacheMBean interface
> ---------------------------------------------------
>
> Key: CASSANDRA-14687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14687
> Project: Cassandra
> Issue Type: Bug
> Components: Auth
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Major
> Fix For: 4.0
>
>
> In CASSANDRA-14662, a type parameter {{<T>}} and {{invalidate<T t>}} method
> were added to {{AuthCacheMBean}} with the intention that this would
> automatically expose via JMX the {{invalidate}} method from {{AuthCache}}
> itself. Actually, this is not the case, as type erasure obscures the actual
> type of the parameter and so JMX clients like jconsole and jmc disable access
> to the method.
> Only {{PasswordAuthenticator.CredentialsCache}} provided method like this
> previously, via {{CredentialsCacheMBean extends AuthCacheMBean}}, so the most
> straightforward fix is to just revert the change to {{AuthCacheMBean}}.
> Future/alternative cache implementations can continue to specify their own
> MBean interfaces to add specialised methods as before.
> I should've caught this before committing the CASSANDRA-14662 as it broke a
> couple of dtests in AuthTest, mea culpa.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
