CAS 6.6.3 No TransactionManager on JPA ticket registry

161 views
Skip to first unread message

Lauri

unread,
Dec 22, 2022, 7:54:15 AM12/22/22
to CAS Community
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?

Gregory G

unread,
Jan 2, 2023, 11:17:35 PM1/2/23
to CAS Community, Lauri
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

Lauri

unread,
Jan 12, 2023, 4:22:05 AM1/12/23
to CAS Community, Gregory G, Lauri
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


Reply all
Reply to author
Forward
0 new messages