May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1171) improve XAResource preparefailed logging

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1171?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1171: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=959462 > improve XAResource preparefailed logging > ---------------------------------------- > > Key: JBTM-1171 > URL: https://issues.jboss.org/browse/JBTM-1171 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.6.1.CP12 > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Fix For: 4.6.1.CP13 > > > com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed does not log the underlying XA exception. In cases where e.g. db constraints are deferred to tx commit time, such errors can contain useful information. > Note that non-deferred constraints are covered by JBTM-575 as the problem manifests at the earlier beforeCompletion (i.e. sql flush) stage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1171) improve XAResource preparefailed logging

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1171?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-1171: ------------------------------------ reopening since with an XA datasource the exception is properly logged but not so with a non XA data source. > improve XAResource preparefailed logging > ---------------------------------------- > > Key: JBTM-1171 > URL: https://issues.jboss.org/browse/JBTM-1171 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.6.1.CP12 > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Fix For: 4.6.1.CP13 > > > com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed does not log the underlying XA exception. In cases where e.g. db constraints are deferred to tx commit time, such errors can contain useful information. > Note that non-deferred constraints are covered by JBTM-575 as the problem manifests at the earlier beforeCompletion (i.e. sql flush) stage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12429212&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 27/May/13 4:11 PM Start Date: 27/May/13 4:11 PM Worklog Time Spent: 6 hours, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 day) Time Spent: 3 weeks, 1 day, 4 hours, 59 minutes (was: 3 weeks, 6 hours, 29 minutes) Worklog Id: (was: 12429212) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 3 weeks, 1 day, 4 hours, 59 minutes > Remaining Estimate: 0 minutes > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1365: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/303, https://github.com/jbosstm/narayana/pull/306 > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 3 weeks, 1 day, 4 hours, 59 minutes > Remaining Estimate: 0 minutes > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12429210&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 27/May/13 8:53 AM Start Date: 27/May/13 8:53 AM Worklog Time Spent: 3 days, 3 hours, 18 minutes Issue Time Tracking ------------------- Remaining Estimate: 1 day (was: 3 days) Time Spent: 3 weeks, 6 hours, 29 minutes (was: 2 weeks, 2 days, 3 hours, 11 minutes) Worklog Id: (was: 12429210) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 3 weeks, 6 hours, 29 minutes > Remaining Estimate: 1 day > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1505?focusedWorklogId=12429209&page=... ] Gytis Trikleris logged work on JBTM-1505: ----------------------------------------- Author: Gytis Trikleris Created on: 27/May/13 8:49 AM Start Date: 27/May/13 8:49 AM Worklog Time Spent: 1 minute Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 1 hour, 1 minute (was: 1 hour) Worklog Id: (was: 12429209) > WS-BA transaction context not propagated if JTA transaction present. > -------------------------------------------------------------------- > > Key: JBTM-1505 > URL: https://issues.jboss.org/browse/JBTM-1505 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 1 hour, 1 minute > Remaining Estimate: 0 minutes > > With default-context-propagation enabled: > What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: > {code} > final CoordinationContextType coordinationContext ; > if (atContext != null) > { > coordinationContext = atContext.getCoordinationContext() ; > } > else if (baContext != null) > { > coordinationContext = baContext.getCoordinationContext() ; > } > {code} > I'm not yet sure how we handle this case. We certainly need a test for it though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1505?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1505: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/305 > WS-BA transaction context not propagated if JTA transaction present. > -------------------------------------------------------------------- > > Key: JBTM-1505 > URL: https://issues.jboss.org/browse/JBTM-1505 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > With default-context-propagation enabled: > What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: > {code} > final CoordinationContextType coordinationContext ; > if (atContext != null) > { > coordinationContext = atContext.getCoordinationContext() ; > } > else if (baContext != null) > { > coordinationContext = baContext.getCoordinationContext() ; > } > {code} > I'm not yet sure how we handle this case. We certainly need a test for it though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1505?focusedWorklogId=12429208&page=... ] Gytis Trikleris logged work on JBTM-1505: ----------------------------------------- Author: Gytis Trikleris Created on: 27/May/13 8:49 AM Start Date: 27/May/13 8:49 AM Worklog Time Spent: 1 hour Issue Time Tracking ------------------- Remaining Estimate: 1 hour (was: 2 hours) Time Spent: 1 hour Worklog Id: (was: 12429208) > WS-BA transaction context not propagated if JTA transaction present. > -------------------------------------------------------------------- > > Key: JBTM-1505 > URL: https://issues.jboss.org/browse/JBTM-1505 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 2 hours > Time Spent: 1 hour > Remaining Estimate: 1 hour > > With default-context-propagation enabled: > What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block: > {code} > final CoordinationContextType coordinationContext ; > if (atContext != null) > { > coordinationContext = atContext.getCoordinationContext() ; > } > else if (baContext != null) > { > coordinationContext = baContext.getCoordinationContext() ; > } > {code} > I'm not yet sure how we handle this case. We certainly need a test for it though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1704) Add JavaDoc to Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1704?focusedWorklogId=12429207&page=... ] Paul Robinson logged work on JBTM-1704: --------------------------------------- Author: Paul Robinson Created on: 27/May/13 6:03 AM Start Date: 27/May/13 6:03 AM Worklog Time Spent: 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 4 hours) Time Spent: 30 minutes Worklog Id: (was: 12429207) > Add JavaDoc to Compensations API > -------------------------------- > > Key: JBTM-1704 > URL: https://issues.jboss.org/browse/JBTM-1704 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 4 hours > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1718: ----------------------------------- Summary: Resolve the ParticipantCompletion race condition Key: JBTM-1718 URL: https://issues.jboss.org/browse/JBTM-1718 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TXFramework Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M4 This issue is documented here: JBTM-1429 In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 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 May 2013