[keycloak-dev] JTA issues
Stian Thorgersen
sthorger at redhat.com
Mon Aug 15 07:42:21 EDT 2016
There's a proper transaction manager running in WF, maybe we should drop
our stuff and use that instead. We can manage the transactions by
retrieving the transaction manager from JNDI.
On 8 August 2016 at 14:46, Bill Burke <bburke at redhat.com> wrote:
>
>
> On 8/8/16 8:31 AM, Marek Posolda wrote:
> > The question is, if we can fix liquibase instead of require people to
> > change DS? Maybe I can try to continue in your branch later this week
> > and look at it?
> >
>
> It's not just liquibase. J
>
> > Another possibility: Don't bootstrap JTA automatically at
> > KeycloakSessionFactory.create() but instead do it just in HTTP
> > requests (in KeycloakSessionServletFilter ). Then liquibase bootstrap
> > won't be an issue?
> >
>
> JPA Model will also barf with the same error if a JTA transaction is
> started as we do local JPA transactions. So we have to have the
> datasource flag or change how we interact with EntityManagers.
>
> Bill
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-dev/attachments/20160815/9c7bbba1/attachment.html
More information about the keycloak-dev
mailing list