September 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2753) Method end on PGXAConnection has been called twice

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2753?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2753: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1025 > Method end on PGXAConnection has been called twice > -------------------------------------------------- > > Key: JBTM-2753 > URL: https://issues.jboss.org/browse/JBTM-2753 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.0.Final > Environment: Wildfly 8 > Reporter: Florian Mélot > Priority: Minor > Fix For: 5.next > > > End method from PGXAConnection has been called twice when an EJB called another EJB to get data from psql database (9.2.5) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2753) Method end on PGXAConnection has been called twice

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2753?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2753: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Method end on PGXAConnection has been called twice > -------------------------------------------------- > > Key: JBTM-2753 > URL: https://issues.jboss.org/browse/JBTM-2753 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.0.Final > Environment: Wildfly 8 > Reporter: Florian Mélot > Priority: Minor > Fix For: 5.next > > > End method from PGXAConnection has been called twice when an EJB called another EJB to get data from psql database (9.2.5) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2753) Method end on PGXAConnection has been called twice

by Florian Mélot (JIRA)

Florian Mélot created JBTM-2753: ----------------------------------- Summary: Method end on PGXAConnection has been called twice Key: JBTM-2753 URL: https://issues.jboss.org/browse/JBTM-2753 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.3.0.Final Environment: Wildfly 8 Reporter: Florian Mélot Priority: Minor Fix For: 5.later End method from PGXAConnection has been called twice when an EJB called another EJB to get data from psql database (9.2.5) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2752) Database connection on POSTGRE required max_prepared_statement

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2752?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2752: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1025 > Database connection on POSTGRE required max_prepared_statement > -------------------------------------------------------------- > > Key: JBTM-2752 > URL: https://issues.jboss.org/browse/JBTM-2752 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > max_prepared_statement is required on the file (postgre.conf) to connect on pgsql base. > If this option wasn't activate, the method end is called twice on PGXAConnection > Please find below original discussion : > https://developer.jboss.org/message/958507#958507 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2752) Database connection on POSTGRE required max_prepared_statement

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2752?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2752: -------------------------------- Forum Reference: https://developer.jboss.org/message/958553?et=watches.email.thread#958553 > Database connection on POSTGRE required max_prepared_statement > -------------------------------------------------------------- > > Key: JBTM-2752 > URL: https://issues.jboss.org/browse/JBTM-2752 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > max_prepared_statement is required on the file (postgre.conf) to connect on pgsql base. > If this option wasn't activate, the method end is called twice on PGXAConnection > Please find below original discussion : > https://developer.jboss.org/message/958507#958507 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2752) Database connection on POSTGRE required max_prepared_statement

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2752?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved WFLY-7099 to JBTM-2752: ------------------------------------------- Project: JBoss Transaction Manager (was: WildFly) Key: JBTM-2752 (was: WFLY-7099) Component/s: JTA (was: Transactions) Affects Version/s: (was: 8.2.0.Final) > Database connection on POSTGRE required max_prepared_statement > -------------------------------------------------------------- > > Key: JBTM-2752 > URL: https://issues.jboss.org/browse/JBTM-2752 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > > max_prepared_statement is required on the file (postgre.conf) to connect on pgsql base. > If this option wasn't activate, the method end is called twice on PGXAConnection > Please find below original discussion : > https://developer.jboss.org/message/958507#958507 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2752) Database connection on POSTGRE required max_prepared_statement

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2752?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2752: -------------------------------- Fix Version/s: 5.next > Database connection on POSTGRE required max_prepared_statement > -------------------------------------------------------------- > > Key: JBTM-2752 > URL: https://issues.jboss.org/browse/JBTM-2752 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > max_prepared_statement is required on the file (postgre.conf) to connect on pgsql base. > If this option wasn't activate, the method end is called twice on PGXAConnection > Please find below original discussion : > https://developer.jboss.org/message/958507#958507 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2733) Adding section about inflow transactions and EIS interaction

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2733?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2733: --------------------------------------- Ok, I see. Thank you for confirmation! > Adding section about inflow transactions and EIS interaction > ------------------------------------------------------------ > > Key: JBTM-2733 > URL: https://issues.jboss.org/browse/JBTM-2733 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I would like ask for enhancing Narayana documentation for section where information about inflow transactions and interaction with EIS would be part of. > This ask for the addition came from discussion about behaviour of inflow transaction on jbossts mailing list. Particularly information how EIS and TM is expected to interoperate during recovery process. E.g. how EIS is expected to finish transaction when TM jvm crash occurs or how EIS is expected to finish transaction when participant of txn involved under management of TM (TM is manager of subordinate transaction) and such participant independently decides to rollback (after prepare is confirmed) which causes heuristic exception being thrown to EIS RAR and transaction is put to heuristic state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2733) Adding section about inflow transactions and EIS interaction

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2733?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2733: ------------------------------------- Sorry, you are right that you can OR them. > Adding section about inflow transactions and EIS interaction > ------------------------------------------------------------ > > Key: JBTM-2733 > URL: https://issues.jboss.org/browse/JBTM-2733 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I would like ask for enhancing Narayana documentation for section where information about inflow transactions and interaction with EIS would be part of. > This ask for the addition came from discussion about behaviour of inflow transaction on jbossts mailing list. Particularly information how EIS and TM is expected to interoperate during recovery process. E.g. how EIS is expected to finish transaction when TM jvm crash occurs or how EIS is expected to finish transaction when participant of txn involved under management of TM (TM is manager of subordinate transaction) and such participant independently decides to rollback (after prepare is confirmed) which causes heuristic exception being thrown to EIS RAR and transaction is put to heuristic state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2733) Adding section about inflow transactions and EIS interaction

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2733?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2733: --------------------------------------- Hi [~tomjenkinson], I was wondering on your comment https://issues.jboss.org/browse/JBTM-2733?focusedCommentId=13284121#comme... and now I found some time to go through the XA spec for it. I wasn't able to find reason behind why the recover sequence should be {{xa_recover(START), xa_commit/rb, xa_recover(END)}} and can't be e.g. like {{xa_recover(START|END), xa_commit/rb}}. Would you be so kind and elaborate a bit on this? Or can you point me to spec/article where I got information how this is expected to be used? It's quite possible that I just haven't read/searched properly. I'm just curious. Thanks in advance. > Adding section about inflow transactions and EIS interaction > ------------------------------------------------------------ > > Key: JBTM-2733 > URL: https://issues.jboss.org/browse/JBTM-2733 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Affects Versions: 5.3.4.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I would like ask for enhancing Narayana documentation for section where information about inflow transactions and interaction with EIS would be part of. > This ask for the addition came from discussion about behaviour of inflow transaction on jbossts mailing list. Particularly information how EIS and TM is expected to interoperate during recovery process. E.g. how EIS is expected to finish transaction when TM jvm crash occurs or how EIS is expected to finish transaction when participant of txn involved under management of TM (TM is manager of subordinate transaction) and such participant independently decides to rollback (after prepare is confirmed) which causes heuristic exception being thrown to EIS RAR and transaction is put to heuristic state. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2016