Thank you very much. I tried your patch and it is working fine on my side. On Monday, December 7, 2015 at 7:29:46 PM UTC+1, Misagh Moayyed wrote: > > This turned out to be a bug with the entity manager prematurely closing. > This will be fixed in 4.1.3; You can try to test this with 4.1.3 SNAPSHOT > for the time being until it’s released in a couple of weeks. > > > > *From:* [email protected] <javascript:> [mailto:[email protected] > <javascript:>] *On Behalf Of *Jean L. > *Sent:* Sunday, December 6, 2015 3:18 PM > *To:* jasig-cas-user <[email protected] <javascript:>> > *Cc:* [email protected] <javascript:> > *Subject:* Re: [cas-user] 4.1.2: JpaTicketRegistry: No transactional > EntityManager available > > > > Hi, > > > > I have the same "No transactional EntityManager available" issue on my > side, with a simple JPA Ticket registry (and JSON Service registry). > > I have also added a minimal GH project to help reproducing the issue: > > https://github.com/jlorieux/cas-jpaTicket > > > > In my case, the TGT ticket is successfully created in the database, but > not the ST ticket ("No transactional EntityManager available" occurs > before). > > I'm using a MySQL 5.5/Tomcat 8 backend. > > > > Regards, > > > > Jean L. > > > > > On Sunday, December 6, 2015 at 1:49:17 PM UTC+1, Robert Oschwald wrote: > > Misagh, > > I added a sample overlay project on GH with JPA Ticket+Service registry > config (using a shared TransactionManager in this case). > I receive the same error as in my project: > org.hibernate.hql.internal.ast.QuerySyntaxException: > AbstractRegisteredService is not mapped > > Here it is: > > https://github.com/robertoschwald/jasig-cas-examples-robertoschwald/tree/4.1.2_jpa > > > Note: The Master branch holds a default overlay config using in-memory > (which works and was the base for the JPA config example in 4.1.2_jpa). > > Config was done as described in > http://jasig.github.io/cas/4.1.x/installation/JPA-Ticket-Registry.html > and > > http://jasig.github.io/cas/4.1.x/installation/Service-Management.html#registered-services > > > See comment at line 153 in deployerConfigContext of cas-server-overlay. > > Please have a look. Thanks! > > Robert > > > > > Am 02.12.2015 um 19:12 schrieb Misagh Moayyed <[email protected]>: > > > > I ran a quick test, with both JPA service registry and JPA ticket > registry defined in an overlay using the same transaction manager. No > issues. > > > > Post your overlay somewhere on github or pastebin and we might be able > to spot something. Otherwise so far, it’s more likely a config issue on > your end. > > > > - Misagh > > > >> On Dec 1, 2015, at 10:15 PM, Tai Hu <[email protected]> wrote: > >> > >> Do you find the solution for this "No transactional EntityManager > available" issue? I just ran into the exact same problem. For both > PostgreSQL and MySQL, merge method is never under a transaction. Thanks. > >> > >> On Monday, November 30, 2015 at 7:48:05 AM UTC-5, robertoschwald wrote: > >> Hi all, > >> > >> while configuring CAS 4.1.2 with JpaTicketRegistry, I cannot get it to > work. > >> I always receive the following Exception: > >> Exception thrown executing > org.jasig.cas.web.flow.GenerateServiceTicketAction@6e6a43a4 <javascript:> > in state 'generateServiceTicket' of flow 'login' > >> javax.persistence.TransactionRequiredException: No transactional > EntityManager available > >> at > org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:275) > > > >> at com.sun.proxy.$Proxy49.merge(Unknown Source) > >> at > org.jasig.cas.ticket.registry.JpaTicketRegistry.updateTicket(JpaTicketRegistry.java:57) > > > >> > >> > >> I used the described config in > http://jasig.github.io/cas/4.1.x/installation/JPA-Ticket-Registry.html > and also added some pointcuts described in > >> > >> http://stackoverflow.com/a/33663812 > >> > >> But it still fails. > >> > >> My JPA config is in spring-configuration/ticketRegistry.xml. > >> > >> Anything else I’m missing? > >> > >> > >> Robert > >> > >> > >> > >> > >> -- > >> 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 [email protected]. > >> Visit this group at > http://groups.google.com/a/apereo.org/group/cas-user/. > > > > > > -- > > 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 [email protected]. > > Visit this group at > http://groups.google.com/a/apereo.org/group/cas-user/. > > -- > 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 [email protected]. > Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/. > > > -- > 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 [email protected] <javascript:>. > Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/. > > -- > 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 [email protected] <javascript:>. > Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/. >
-- 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 [email protected]. Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/.
