[ https://issues.apache.org/jira/browse/GEODE-9645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen Nichols closed GEODE-9645. ------------------------------- > MultiUserAuth: DataSerializerRecoveryListener is called without auth > information. Promptly fails > ------------------------------------------------------------------------------------------------ > > Key: GEODE-9645 > URL: https://issues.apache.org/jira/browse/GEODE-9645 > Project: Geode > Issue Type: Bug > Components: core > Reporter: Mark Hanson > Assignee: Mark Hanson > Priority: Major > Labels: GeodeOperationAPI, pull-request-available, unreleased > Fix For: 1.15.0 > > > When multiuserSecureModeEnabled is enabled, a user may register a > DataSerializer. When endpoint manager detects a new endpoint, it will attempt > to register the data serializers with other machines. This is a problem was > there is no authentication information in the background process to > authenticate. Hence the error seen below. > > {noformat} > [warn 2021/09/27 18:03:02.804 PDT <poolTimer-DEFAULT-2> tid=0x62] > DataSerializerRecoveryTask - Error recovering dataSerializers: > java.lang.UnsupportedOperationException: Use Pool APIs for doing operations > when multiuser-secure-mode-enabled is set to true. > at > org.apache.geode.cache.client.internal.PoolImpl.authenticateIfRequired(PoolImpl.java:1540) > > at > org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:816) > at > org.apache.geode.cache.client.internal.RegisterDataSerializersOp.execute(RegisterDataSerializersOp.java:40) > > at > org.apache.geode.cache.client.internal.DataSerializerRecoveryListener$RecoveryTask.run2(DataSerializerRecoveryListener.java:116) > > at > org.apache.geode.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1337) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748){noformat} -- This message was sent by Atlassian Jira (v8.20.7#820007)