Hello Marius, regarding your transaction code, I filed this ticket: https://issues.jboss.org/browse/KEYCLOAK-2235 Didn't get to do some docker/postgres 9.3 tests But for my shell history, I was using 9.3 - but not sure if w/ EAP (6.3.x / 6.4.1) or WildFly More on Doccker tomorrow On Thu, Dec 17, 2015 at 11:10 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

Hi Matthias, early January sounds great. Just let me know when I can start testing the master branch in the preproduction environment. I will let you know my experiences. Thank you very much for your help! Best regards Marius Hi Marius, looks like with the recent Keycloak version (1.7.0), this issue is no longer present. On master we already have KC 1.7.0 as our main server. Would it help if we get a 1.2.0-alpha.1 out early January? (that would be basically 1.1.1 + KC 1.7.0) On Thu, Dec 17, 2015 at 6:47 PM, Matthias Wessendorf < <mailto:matzew@apache.org> matzew(a)apache.org&gt; wrote: Hello Marius, regarding your transaction code, I filed this ticket: <https://issues.jboss.org/browse/KEYCLOAK-2235> https://issues.jboss.org/browse/KEYCLOAK-2235 Didn't get to do some docker/postgres 9.3 tests But for my shell history, I was using 9.3 - but not sure if w/ EAP (6.3.x / 6.4.1) or WildFly More on Doccker tomorrow On Thu, Dec 17, 2015 at 11:10 AM, Matthias Wessendorf < <mailto:matzew@apache.org> matzew(a)apache.org&gt; wrote: Hello Marius, sorry for the late reply - your mail was stuck in the moderators queue. Did you subscribe before sending? Anyways. I am not sure about this issue, looks like there is a bug in the "old" Keycloak we use, on 1.1.0 of UPS. We are in the process of updating it to a more recent version of Keycloak (1.7.0): <https://github.com/aerogear/aerogear-unifiedpush-server/pull/659> https://github.com/aerogear/aerogear-unifiedpush-server/pull/659 Can you file a JIRA against Keycloak -> <http://JIRA.jboss.org/browse/KEYCLOAK> http://JIRA.jboss.org/browse/KEYCLOAK We have done a bit of testing w/ UPS 1.1.0 and Postgres9 - but I am, tbh, not sure if we did test w/ 9.3 :/ I will create docker-compose files, that will use this DB for our own testing of UPS. I will share my evaluations of this later (today/tomorow) Sorry for the inconvenience! HTH, Matthias On Mon, Dec 14, 2015 at 4:48 PM, Marius Schellenberger < <mailto:marius.schellenberger@petafuel.de> marius.schellenberger(a)petafuel.de&gt; wrote: Hello AeroGear dev‘s, I’m currently evaluating the AeroGear Unified Push Server in a pre-production environment (RedHat JBoss EAP 6.4.4) and I’m facing an issue with an idle database transaction, which is executed every time the app is deployed (or the JBoss Server is started). I’m using Postgresql 9.3 as the database backend. The idle process listed in ps aux: postgres: keycloak keycloak 10.0.6.106(55387) idle in transaction The transaction seems to hang at this SQL statement: select authentica0_.REALM_ID as REALM_ID4_28_1_, authentica0_.ID as ID1_3_1_, authentica0_.ID as ID1_3_0_, authentica0_.ALIAS as ALIAS2_3_0_, authentica0_.PROVIDER_ID as PROVIDER3_3_0_, authentica0_.REALM_ID as REALM_ID4_3_0_ from AUTHENTICATOR authentica0_ where authentica0_.REALM_ID=$1 The query results nothing, as you can see below: select * from AUTHENTICATOR; id | alias | realm_id | provider_id ----+-------+----------+------------- (0 rows) Can you guys please help me identifying this issue? Kind regards, Marius Schellenberger _______________________________________________ Aerogear-users mailing list <mailto:Aerogear-users@lists.jboss.org> Aerogear-users(a)lists.jboss.org <https://lists.jboss.org/mailman/listinfo/aerogear-users> https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf