March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1510) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1510: ------------------------------------- Summary: QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076 Key: JBTM-1510 URL: https://issues.jboss.org/browse/JBTM-1510 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor Fix For: 5.0.0.M3 See: http://172.17.131.2/job/narayana/173/ -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1429) Document the PartcipantCompletion race condition

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1429?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1429: -------------------------------- Priority: Major (was: Minor) > Document the PartcipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1429 > URL: https://issues.jboss.org/browse/JBTM-1429 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 3 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > * Add logging to WARN when it happens > * Add explanation of why and when it happens to XTS docs and how to spot if you have it > * Blog about it > * Link to the docs in the quickstart -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1447) Create WebserviceFeature for TXBridge

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?focusedWorklogId=12428739&page=... ] Gytis Trikleris logged work on JBTM-1447: ----------------------------------------- Author: Gytis Trikleris Created on: 04/Mar/13 6:40 AM Start Date: 01/Mar/13 6:39 AM Worklog Time Spent: 1 day, 2 hours Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 6 hours) Time Spent: 2 days, 2 hours (was: 1 day) Worklog Id: (was: 12428739) > Create WebserviceFeature for TXBridge > ------------------------------------- > > Key: JBTM-1447 > URL: https://issues.jboss.org/browse/JBTM-1447 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > Original Estimate: 1 day > Time Spent: 2 days, 2 hours > Remaining Estimate: 0 minutes > > h2. Create: > * JTAOverWSATFeature > * Configuration option on the XTS Subsytem (defaultContextPropagation) > h2. Semantics: > h4. JTAOverWSATFeature absent, defaultContextPropagation disabled > This is the current OOTB experience for EAP 5&6. No handlers are activated automatically. The developer has to add them manually for all ports. When the developer does add the handlers, the MustUnderstand attribute of the WS-TX context is set to true. > h4. JTAOverWSATFeature absent, defaultContextPropagation enabled (Default OOTB) > All Web service requests that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to false. > h4. JTAOverWSATFeature enabled, defaultContextPropagation disabled > All Web service requests, for this port, that are made in the context of a JTA transaction will be bridged to WS-AT and the WS-AT context added to the request soap header. MustUnderstand is set to true. > h5. JTAOverWSATFeature disabled, defaultContextPropagation enabled > All Web service requests, for this port, don't bridge JTA. > h2. Implementation > The XTS Subsystem reads its config on boot. It carries out one of the following actions depending on what it finds: > # <defaultContextPropagation enabled=”true” /> (default OOTB config) > Add the Bridge handler initialized to be enabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # <defaultContextPropagation enabled=”false” /> > Add the Bridge handler initialized to be disabled by default then do [JBTM-986] after. Ensure that the Bridge handler is invoked before the WSTX handler. > # Config absent. > Error. Fail config parse. > h5. Bridge handler > Two handlers that delegate to the existing TXBridge handler: > # Disabled by default. Only invokes the TXBridge handler if the JTAOverWSATFeature is present and enabled. > # Enabled by default. Always invokes the TXBridge handler unless the JTAOverWSATFeature is present and disabled. > If the bridge detects the JTAOverWSATFeature, but no WSTXFeature, it adds the WSTXFeature to the invocation context (setting WSTXFeature.enabled = JTAOverWSATFeature.enabled). This is needed by the WSTX handler and prevents the developer from having to add both. > h5. Backwards compatibility > Existing applications (written before this feature was released) will be specifying Handler chains manually via the binding provider. Therefore we need to tolerate the situation where these handlers are added twice. Once for by this feature and again by the developer. > In particular the handlers added by this feature and [JBTM-986] should do nothing if the com.arjuna.mw.wst11.client.JaxWSHeaderContextProcessor handler is already in the handler chain. We could achieve this by adding this handler in the post handler chain. We could then look for an existing WSTX header and do nothing if we find it. This is just a suggestion, there may be a better way to achieve this behaviour. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1191) TXFramework enlists with invalid url if @Path is used on a service request method

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1191?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1191: -------------------------------- Fix Version/s: 5.0.0.Final > TXFramework enlists with invalid url if @Path is used on a service request method > --------------------------------------------------------------------------------- > > Key: JBTM-1191 > URL: https://issues.jboss.org/browse/JBTM-1191 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > For this interface: > {code} > @Path("/taxi") > public interface TaxiServiceAT { > @POST > @Produces("text/plain") > @Path("makeBooking") > public Response makeBooking(); > } > {code} > the following enlist url is created: > http://localhost:8080/test/taxi/makeBooking0_ffffc0a80068_2a160422_4fe205... > The addition of the '/makeBooking' fragment breaks the url pattern expected by the participant endpoint (@Path("{txid}/{pId}/terminate")) and messages from the coordinator are ignored. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1190) TXFramework prefixes @Path value to TX id

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1190?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1190: -------------------------------- Fix Version/s: 5.0.0.M3 > TXFramework prefixes @Path value to TX id > ----------------------------------------- > > Key: JBTM-1190 > URL: https://issues.jboss.org/browse/JBTM-1190 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > > For example, a service with @Path("/restaurant") results in a terminator url of: "http://localhost:8080/test/restaurant0_ffffc0a80068_2a160422_4fe20541_155...". Notice the missing '/' between restaurant and the txid. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1190) TXFramework prefixes @Path value to TX id

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1190?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1190: -------------------------------- Affects Version/s: (was: 5.0.0.M2) > TXFramework prefixes @Path value to TX id > ----------------------------------------- > > Key: JBTM-1190 > URL: https://issues.jboss.org/browse/JBTM-1190 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > > For example, a service with @Path("/restaurant") results in a terminator url of: "http://localhost:8080/test/restaurant0_ffffc0a80068_2a160422_4fe20541_155...". Notice the missing '/' between restaurant and the txid. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce API changes for *-AT and Compensations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1391: -------------------------------- Affects Version/s: 5.0.0.M2 > Prepare a blog post to introduce API changes for *-AT and Compensations > ----------------------------------------------------------------------- > > Key: JBTM-1391 > URL: https://issues.jboss.org/browse/JBTM-1391 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Affects Versions: 5.0.0.M2 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 1 day, 2 hours, 45 minutes > Remaining Estimate: 1 hour > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce API changes for *-AT and Compensations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1391: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Prepare a blog post to introduce API changes for *-AT and Compensations > ----------------------------------------------------------------------- > > Key: JBTM-1391 > URL: https://issues.jboss.org/browse/JBTM-1391 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Affects Versions: 5.0.0.M2 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Original Estimate: 2 days > Time Spent: 1 day, 2 hours, 45 minutes > Remaining Estimate: 1 hour > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1191) TXFramework enlists with invalid url if @Path is used on a service request method

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1191?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1191: -------------------------------- Affects Version/s: (was: 5.0.0.M2) > TXFramework enlists with invalid url if @Path is used on a service request method > --------------------------------------------------------------------------------- > > Key: JBTM-1191 > URL: https://issues.jboss.org/browse/JBTM-1191 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Priority: Minor > > For this interface: > {code} > @Path("/taxi") > public interface TaxiServiceAT { > @POST > @Produces("text/plain") > @Path("makeBooking") > public Response makeBooking(); > } > {code} > the following enlist url is created: > http://localhost:8080/test/taxi/makeBooking0_ffffc0a80068_2a160422_4fe205... > The addition of the '/makeBooking' fragment breaks the url pattern expected by the participant endpoint (@Path("{txid}/{pId}/terminate")) and messages from the coordinator are ignored. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1486) Prepare a blog post for XTS default context propagation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1486?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1486: -------------------------------- Affects Version/s: 5.0.0.M2 > Prepare a blog post for XTS default context propagation > -------------------------------------------------------- > > Key: JBTM-1486 > URL: https://issues.jboss.org/browse/JBTM-1486 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge, XTS > Affects Versions: 5.0.0.M2 > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 0 minutes > > Describing JBTM-1447 and JBTM-986. -- 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

11 years, 2 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 March 2013