Hi! I updated to v6.6.4 but have still the same error. I have found a workaround by setting: cas.ticket.registry.core.enable-locking=false
Gregory G kirjutas Teisipäev, 3. jaanuar 2023 kl 06:17:35 UTC+2: > Hello, > > I have the same error, and seems to be fixed in CAS 6.6.4 > > Since 3 days, our testing env start again, without any modifications > > Le jeudi 22 décembre 2022 à 13:54:15 UTC+1, Lauri a écrit : > >> Hi! >> I get an error: >> "Caused by: >> org.springframework.beans.factory.NoUniqueBeanDefinitionException: No >> qualifying bean of type >> 'org.springframework.transaction.TransactionManager' available: expected >> single matching bean but found 4: >> ticketTransactionManager,transactionManagerGoogleAuthenticator,transactionManagerEvents,transactionManagerMfaAuthnTrust" >> when trying to use JPA ticket registry together with Google >> Authenticator, Events and MFA authn trust dependencies. >> I use MySQL5InnoDBDialect in CAS 6.6.3 in external Tomcat 9. >> It worked in CAS 6.2. >> When I remove Google Authenticator, Events and MFA authn trust >> dependencies, then JPA ticket registry works and no such error is thrown. >> Is there some configuration value what I should set in order to set >> transaction manager for JPA ticket registry? >> > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/8da99d5f-803e-4d85-a4a7-5180dc1645b3n%40apereo.org.
