May 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2899) Consider independently versioning the quickstarts

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2899: ----------------------------------- Summary: Consider independently versioning the quickstarts Key: JBTM-2899 URL: https://issues.jboss.org/browse/JBTM-2899 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson It would be clearer to know when an individual quickstart has changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2766: -------------------------------- Description: Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. (was: Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage.) > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2766: -------------------------------- Summary: Allow Transactional Driver to be used with commons-dbcp in Tomcat (was: Implement pooling for transactional driver) > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1488) Implement the REST-JDI specification

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1488?page=com.atlassian.jira.plugin.... ] Work on JBTM-1488 started by Michael Musgrove. ---------------------------------------------- > Implement the REST-JDI specification > ------------------------------------ > > Key: JBTM-1488 > URL: https://issues.jboss.org/browse/JBTM-1488 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Labels: student > Fix For: 6.later > > > https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2766) Implement pooling for transactional driver

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1180 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Implement pooling for transactional driver > ------------------------------------------ > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1435549|https://bugzilla.redhat.com/show_bug.cgi?id=1435549] from POST to MODIFIED > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.next > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2760) SPI to check if JTA or JTS transaction is active during graceful shutdown

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2760?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2760: ------------------------------------- Link to the code at the time of Gytis' comments: https://github.com/jbosstm/jboss-transaction-spi/blob/efe7825ec9780b06877... > SPI to check if JTA or JTS transaction is active during graceful shutdown > ------------------------------------------------------------------------- > > Key: JBTM-2760 > URL: https://issues.jboss.org/browse/JBTM-2760 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > > During graceful shutdown EJB subsystem should check with transaction subsystem if request should be allowed in. Only requests participating in an existing transaction are permitted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2898) Consider Java 9 alternatives to reflection for STM

by Mark Little (JIRA)

Mark Little created JBTM-2898: --------------------------------- Summary: Consider Java 9 alternatives to reflection for STM Key: JBTM-2898 URL: https://issues.jboss.org/browse/JBTM-2898 Project: JBoss Transaction Manager Issue Type: Feature Request Components: STM Reporter: Mark Little Assignee: Mark Little -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1179 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcac... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1178 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3...) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3...) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2017