[Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Marius Schellenberger

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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
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):

Can you file a JIRA against 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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
Hello Marius,

regarding your transaction code, I filed this ticket:

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 <[hidden email]> 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):

Can you file a JIRA against 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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
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 <[hidden email]> wrote:
Hello Marius,

regarding your transaction code, I filed this ticket:

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 <[hidden email]> 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):

Can you file a JIRA against 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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--



--



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Marius Schellenberger

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 <[hidden email]> wrote:

Hello Marius,

 

regarding your transaction code, I filed this ticket:

 

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 <[hidden email]> 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):

 

Can you file a JIRA against 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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



 

--



 

--



 

--


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
Hi Marius,

you can already use it today, as the master branch is on 1.7.0.

To build the distribution/release binaries, simply run:
mvn clean install -Pdist,test

and in the "dist/target" folder, you'll find the WAR files, as part of the "aerogear-unifiedpush-server-1.2.0-SNAPSHOT-dist.tar.gz" file.


I think this would be good, if you can tell us if the KC bug in question has been fixed, and that way we also don't need to 'rush' on such an alpha.1 release.

Makes sense?
-Matthias

On Wed, Dec 23, 2015 at 4:39 PM, Marius Schellenberger <[hidden email]> wrote:

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 <[hidden email]> wrote:

Hello Marius,

 

regarding your transaction code, I filed this ticket:

 

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 <[hidden email]> 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):

 

Can you file a JIRA against 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 <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



 

--



 

--



 

--


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Marius Schellenberger
In reply to this post by Marius Schellenberger

Hi Matthias,

alright, give me some days to test.
I think next week I will have the results.

Best regards
Marius


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
Perfecto!

have a nice xmas break!

On Wed, Dec 23, 2015 at 5:31 PM, Marius Schellenberger <[hidden email]> wrote:

Hi Matthias,

alright, give me some days to test.
I think next week I will have the results.

Best regards
Marius


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Marius Schellenberger

Dear Matthias,

 

I got the newest commit (880de40) running.

 

Now there are two idle transactions on the database, instead of one.

 

The SQL statement has also changed.

 

select pid,datname,query from pg_stat_activity where pid = 27622 or pid = 27714;

  pid  | datname  |                                                                                                                                                                                                  query                                                                                                                                                                                              

-------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

27622 | keycloak | select defaultgro0_.REALM_ID as REALM_ID1_28_1_, defaultgro0_.GROUP_ID as GROUP_ID2_31_1_, groupentit1_.ID as ID1_21_0_, groupentit1_.NAME as NAME2_21_0_, groupentit1_.PARENT_GROUP as PARENT_G3_21_0_, groupentit1_.REALM_ID as REALM_ID4_21_0_ from REALM_DEFAULT_GROUPS defaultgro0_ inner join KEYCLOAK_GROUP groupentit1_ on defaultgro0_.GROUP_ID=groupentit1_.ID where defaultgro0_.REALM_ID=$1

27714 | keycloak | select defaultgro0_.REALM_ID as REALM_ID1_28_1_, defaultgro0_.GROUP_ID as GROUP_ID2_31_1_, groupentit1_.ID as ID1_21_0_, groupentit1_.NAME as NAME2_21_0_, groupentit1_.PARENT_GROUP as PARENT_G3_21_0_, groupentit1_.REALM_ID as REALM_ID4_21_0_ from REALM_DEFAULT_GROUPS defaultgro0_ inner join KEYCLOAK_GROUP groupentit1_ on defaultgro0_.GROUP_ID=groupentit1_.ID where defaultgro0_.REALM_ID=$1

 

Also when I kill these transactions manually using

select pg_terminate_backend(27622);

select pg_terminate_backend(27714);

 

the transactions seem to never show up again.

 

The idle transactions are back if the JBoss server is restarted or the App is redeployed.

 

Please tell me if you need any more information.

 

Best regards

Marius

 

 

 

Perfecto!

 

have a nice xmas break!

 

On Wed, Dec 23, 2015 at 5:31 PM, Marius Schellenberger <[hidden email]> wrote:

Hi Matthias,

alright, give me some days to test.
I think next week I will have the results.

Best regards
Marius


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



 

--


_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Idle in transaction using AeroGear Unified Push 1.1.0 and postgresql 9.3

Matthias Wessendorf
Hi Marius,


and reopen the ticket? 

Thanks

On Tuesday, 29 December 2015, Marius Schellenberger <[hidden email]> wrote:

Dear Matthias,

 

I got the newest commit (880de40) running.

 

Now there are two idle transactions on the database, instead of one.

 

The SQL statement has also changed.

 

select pid,datname,query from pg_stat_activity where pid = 27622 or pid = 27714;

  pid  | datname  |                                                                                                                                                                                                  query                                                                                                                                                                                              

-------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

27622 | keycloak | select defaultgro0_.REALM_ID as REALM_ID1_28_1_, defaultgro0_.GROUP_ID as GROUP_ID2_31_1_, groupentit1_.ID as ID1_21_0_, groupentit1_.NAME as NAME2_21_0_, groupentit1_.PARENT_GROUP as PARENT_G3_21_0_, groupentit1_.REALM_ID as REALM_ID4_21_0_ from REALM_DEFAULT_GROUPS defaultgro0_ inner join KEYCLOAK_GROUP groupentit1_ on defaultgro0_.GROUP_ID=groupentit1_.ID where defaultgro0_.REALM_ID=$1

27714 | keycloak | select defaultgro0_.REALM_ID as REALM_ID1_28_1_, defaultgro0_.GROUP_ID as GROUP_ID2_31_1_, groupentit1_.ID as ID1_21_0_, groupentit1_.NAME as NAME2_21_0_, groupentit1_.PARENT_GROUP as PARENT_G3_21_0_, groupentit1_.REALM_ID as REALM_ID4_21_0_ from REALM_DEFAULT_GROUPS defaultgro0_ inner join KEYCLOAK_GROUP groupentit1_ on defaultgro0_.GROUP_ID=groupentit1_.ID where defaultgro0_.REALM_ID=$1

 

Also when I kill these transactions manually using

select pg_terminate_backend(27622);

select pg_terminate_backend(27714);

 

the transactions seem to never show up again.

 

The idle transactions are back if the JBoss server is restarted or the App is redeployed.

 

Please tell me if you need any more information.

 

Best regards

Marius

 

 

 

Perfecto!

 

have a nice xmas break!

 

On Wed, Dec 23, 2015 at 5:31 PM, Marius Schellenberger <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;marius.schellenberger@petafuel.de&#39;);" target="_blank">marius.schellenberger@...> wrote:

Hi Matthias,

alright, give me some days to test.
I think next week I will have the results.

Best regards
Marius


_______________________________________________
Aerogear-users mailing list
<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;Aerogear-users@lists.jboss.org&#39;);" target="_blank">Aerogear-users@...
https://lists.jboss.org/mailman/listinfo/aerogear-users



 

--



--
Sent from Gmail Mobile

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Loading...