September 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2704: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Compensations framework cannot instantiate bean from ear archive > ---------------------------------------------------------------- > > Key: JBTM-2704 > URL: https://issues.jboss.org/browse/JBTM-2704 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be used by the compensations framework. It works fine with war and jar archives, because all deployment classes are accessible for the root bean manager. However, ear archives have multiple bean managers and some classes cannot be accessed. > Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get the correct bean manager. > It would be better to find a solution for this without adding a direct dependency on weld-core and instead injecting the correct bean manager once by the subsystem. However, if that is not possible, we should use the provided workaround. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2749: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done The new SPI is available in org.jboss:jboss-transaction-spi:7.3.4.Final and the implementation of the SPI is on narayana master > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-2749 at 9/7/16 6:59 AM: ---------------------------------------------------------------- The new SPI method is org.jboss.tm.ExtendedJBossXATerminator and is implemented by both of our JTA and JTS variants (com.arjuna.ats.internal.jbossatx.jta.jca.XATerminator and com.arjuna.ats.internal.jbossatx.jts.jca.XATerminator) was (Author: mmusgrov): The new SPI method is org.jboss.tm.ExtendedJBossXATerminator and is implemented by our JTA and JTA variants (com.arjuna.ats.internal.jbossatx.jta.jca.XATerminator and com.arjuna.ats.internal.jbossatx.jts.jca.XATerminator) > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2749: ---------------------------------------- The new SPI method is org.jboss.tm.ExtendedJBossXATerminator and is implemented by our JTA and JTA variants (com.arjuna.ats.internal.jbossatx.jta.jca.XATerminator and com.arjuna.ats.internal.jbossatx.jts.jca.XATerminator) > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2748) Prevent JTS bottom-up recovery from rolling back prepared inflowed JCA transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2748?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2748: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Prevent JTS bottom-up recovery from rolling back prepared inflowed JCA transactions > ----------------------------------------------------------------------------------- > > Key: JBTM-2748 > URL: https://issues.jboss.org/browse/JBTM-2748 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA, JTS, Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > There exists a defect that if a recovering JVM does the following steps: > doRecoveryScan() > waitForOrphanInterval() > doRecoveryScan() > *Before* XATerminator::recover is called in the root coordinator then bottom-up recovery will be told there is NoTransaction which is infers as a rollback. > I saw two options, one was to have TransactionCacheItem try to peek in the objectstore for ServerTransaction/JCA classes. The alternative is to add a new recovery module that can load the ServerTransaction/JCA classes periodically so the transaction won't be lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2747) Modify the SimpleIsolatedServers example such that it does not need the "transport" to maintain its own map of transactions

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2747?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1067 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Modify the SimpleIsolatedServers example such that it does not need the "transport" to maintain its own map of transactions > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2747 > URL: https://issues.jboss.org/browse/JBTM-2747 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Fix For: 5.next > > > The previous example relied upon the "transport" piece maintaining a list of root transactions it had seen. It is actually possible to use the existing list from the TransactionImple -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2749: ----------------------------------- Priority: Critical (was: Major) > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2749: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #13 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > When EJB remoting sees an incomming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2719) tpcall get three seconds delay in the fooapp quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2719?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2719: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > tpcall get three seconds delay in the fooapp quickstart > ------------------------------------------------------- > > Key: JBTM-2719 > URL: https://issues.jboss.org/browse/JBTM-2719 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > The apr_pollset_poll in HybridSocketEndpointQueue.cxx Line 392 is blocking and timing out after 3 second. It is the root cause for the tpcall delaying. > So it should try to wake up the polling in non-conversation session while disconnect -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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 September 2016