January 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2985) Make jdbc transaction driver dynamic properties file being loaded from classpath

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2985?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2985: ---------------------------------- Description: It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should be considered maybe rather for some major release or if discussed at: The fix is here https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... Info on using driver is here https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... was: It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should not be considered for micro releases or only in case it's needed for some bugfix. The fix is here https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... Info on using driver is here https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... > Make jdbc transaction driver dynamic properties file being loaded from classpath > -------------------------------------------------------------------------------- > > Key: JBTM-2985 > URL: https://issues.jboss.org/browse/JBTM-2985 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should be considered maybe rather for some major release or if discussed at: > The fix is here > https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... > Info on using driver is here > https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2985) Make jdbc transaction driver dynamic properties file being loaded from classpath

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2985?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2985: ---------------------------------- Description: It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should not be considered for micro releases or only in case it's needed for some bugfix. The fix is here https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... Info on using driver is here https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... was: It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should not be considered for micro releases or only in case it's needed for some bugfix. Consider this for {{5.8.0}} or rather for {{6.0.0}}. The fix is here https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... Info on using driver is here https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... > Make jdbc transaction driver dynamic properties file being loaded from classpath > -------------------------------------------------------------------------------- > > Key: JBTM-2985 > URL: https://issues.jboss.org/browse/JBTM-2985 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transactional Driver > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should not be considered for micro releases or only in case it's needed for some bugfix. > The fix is here > https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... > Info on using driver is here > https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2985) Make jdbc transaction driver dynamic properties file being loaded from classpath

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2985: ------------------------------------- Summary: Make jdbc transaction driver dynamic properties file being loaded from classpath Key: JBTM-2985 URL: https://issues.jboss.org/browse/JBTM-2985 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transactional Driver Affects Versions: 5.7.1.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor It would be good to add behaviour to load jdbc datasource properties file from the classpath too and not only from 'abs/relative' path. This is a change of the default behaviour and it should not be considered for micro releases or only in case it's needed for some bugfix. Consider this for {{5.8.0}} or rather for {{6.0.0}}. The fix is here https://github.com/ochaloup/narayana/commit/c383cf7fc860345b795efb5b38eec... Info on using driver is here https://jbossts.blogspot.cz/2017/12/narayana-jdbc-transactional-driver.ht... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2984) Ensure that the JMS integration classes are in the Maven sources jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2984?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2984: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Ensure that the JMS integration classes are in the Maven sources jar > -------------------------------------------------------------------- > > Key: JBTM-2984 > URL: https://issues.jboss.org/browse/JBTM-2984 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > There is a problem that the JMS integration sources are not in the uploaded maven sources artifact. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2984) Ensure that the JMS integration classes are in the Maven sources jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2984?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1273 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Ensure that the JMS integration classes are in the Maven sources jar > -------------------------------------------------------------------- > > Key: JBTM-2984 > URL: https://issues.jboss.org/browse/JBTM-2984 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > There is a problem that the JMS integration sources are not in the uploaded maven sources artifact. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2984) Ensure that the JMS integration classes are in the Maven sources jar

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2984: ----------------------------------- Summary: Ensure that the JMS integration classes are in the Maven sources jar Key: JBTM-2984 URL: https://issues.jboss.org/browse/JBTM-2984 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next There is a problem that the JMS integration sources are not in the uploaded maven sources artifact. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ] Ondra Chaloupka commented on JBTM-860: -------------------------------------- I created a documentation issue for the JBoss EAP: https://issues.jboss.org/browse/JBEAP-14113 . Feel free to add your remarks. Thank you. > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on JBTM-860: ------------------------------------ Sorry Alon - I see you raised the discussions - they were just waiting in moderation as it must be your first post to that community I guess. Thanks again for the interest! > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson commented on JBTM-860: ------------------------------------ +1 - and would recommend a docs JBEAP issue if it is not reflected accurately in the EAP docs. Narayana is a opensource community project which is integrated into a number of containers (opensource or commercial), for example: WildFly, EAP, Spring, Karaf, Tomcat. Issues can be resolved here but still have downstream problems (in this case it seems an issue in EAP docs). Thanks for your interest in Narayana - if there is anything more we can do to help feel free to comment on issue or in our forums or IRC - there are some good links here: http://narayana.io/community/index.html > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.s... ] Ondra Chaloupka commented on JBTM-860: -------------------------------------- Hi [~alon3392], the fix of the issue is part of the JBoss EAP from release 7.0.0. I have to admit that the documentation is not clear in this and the section seems to be a remainder from times of the EAP 6.4. The core of the fix is let the transaction manager to know what is the data source of particular unfinished record in the transaction object store. That's ensured by verifying jndi name bound to the particular XAResource (loaded from the object store). The value of the jndi name is obtained from XAResources implementing the special interface https://github.com/jbosstm/jboss-transaction-spi/blob/master/src/main/jav.... If particular implementation of the XAResource uses the wrapper and provides the jndi name identifier for the transaction manager then it's capable to decide if the indoubt transaction participant loaded from the object store was or wasn't committed. This interface is "implemented" by ironjacamar (JCA implementation in WildFly) and by Artemis ActiveMQ resource adapter. In summary it means the fix JBTM-860 involves * any datasource - database jdbc connection - configured in WildFly * artemis activemq resource adapter - {{messaging-activemq}} WildFly configuration If you use other resource adapters (e.g. WSMQ) then this fix does not apply for it. > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 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 January 2018