March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1512) com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1512: ------------------------------------- Summary: com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed Key: JBTM-1512 URL: https://issues.jboss.org/browse/JBTM-1512 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor Fix For: 4.17.4 See: http://172.17.131.2/job/jbossts-EAP601/318 {noformat} /home/hudson/workspace/jbossts-EAP601/build.xml:55: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:283: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:285: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/ArjunaJTS/jts/build.xml:85: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:468: The following error occurred while executing this line: /home/hudson/workspace/jbossts-EAP601/sharedbuild.xml:528: Test com.hp.mwtests.ts.jts.local.transactions.TransactionTest1 failed {noformat} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1509) Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror:

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1509?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1509: -------------------------------- Affects Version/s: 4.6.1.CP12 (was: 4.6.1.CP13) (was: 4.16.0.Final) > Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror: > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1509 > URL: https://issues.jboss.org/browse/JBTM-1509 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.6.1.CP12 > Environment: JBoss EAP 5.1.2 > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 4.6.1.CP14 > > > JBoss TM prints a warning > 17/01/13 09:18:48.672 WARN com.arjuna.ats.jta.logging.loggerI18N 5952 Thread-63 (Horn a9f5517:e5ec:50f6e612:14491 Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror: [key='com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror']TransactionImple.enlistResource, XAException.XAER_RMERR, < 131075, 41, 27, 80798279834849954953484848459757102535349555810153101995853481025410154495058495252574997571025353495558101531019958534810254101544950584952529850 > > due to corrupted resource string -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1509) Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror:

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1509?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1509: -------------------------------- Fix Version/s: (was: 5.0.0.M2) (was: 4.16.7) (was: 4.17.4) > Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror: > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1509 > URL: https://issues.jboss.org/browse/JBTM-1509 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.6.1.CP13, 4.16.0.Final > Environment: JBoss EAP 5.1.2 > Reporter: Tom Ross > Assignee: Tom Jenkinson > Fix For: 4.6.1.CP14 > > > JBoss TM prints a warning > 17/01/13 09:18:48.672 WARN com.arjuna.ats.jta.logging.loggerI18N 5952 Thread-63 (Horn a9f5517:e5ec:50f6e612:14491 Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror: [key='com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror']TransactionImple.enlistResource, XAException.XAER_RMERR, < 131075, 41, 27, 80798279834849954953484848459757102535349555810153101995853481025410154495058495252574997571025353495558101531019958534810254101544950584952529850 > > due to corrupted resource string -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-986) Automatically setup the client side handler chain

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-986?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-986: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Automatically setup the client side handler chain > ------------------------------------------------- > > Key: JBTM-986 > URL: https://issues.jboss.org/browse/JBTM-986 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Time Spent: 2 weeks, 30 minutes > Remaining Estimate: 0 minutes > > When invoking a WS-AT or WS-BA Web service, the client side handler has to be added to the client stub to manage transaction context propagation. The code required to do this is as follows: > {code} > BindingProvider bindingProvider = (BindingProvider) client; > List<Handler> handlers = new ArrayList<Handler>(1); > handlers.add(new JaxWSHeaderContextProcessor()); > bindingProvider.getBinding().setHandlerChain(handlers); > {code} > This is not very user friendly. > This could be done using a JAX-WS feature passed to the Client-side port. > We also need to support client stubs created using @WebServiceRef. Here's some examples of its use: > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > http://anonsvn.jboss.org/repos/jbossws/shared-testsuite/trunk/testsuite/s... > The feature should be "enabled" by default providing the feature is enabled in the XTS server config. > The quickstarts also need updated to use this. -- 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, 9 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1447?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1447: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1504) Update TXFramework tests to use WSTXFeature

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1504?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1504: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update TXFramework tests to use WSTXFeature > ------------------------------------------- > > Key: JBTM-1504 > URL: https://issues.jboss.org/browse/JBTM-1504 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M2 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1188) Support override of CheckedAction

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1188?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1188: ----------------------------------- If someone really wants to do this at the BasicAction level then they could use the global config option and register a single CheckedAction instance that has its own methods and lifecycle for providing a pre-instance CheckedAction, i.e., the BasicAction CheckedAction never changes, but redirects to a specific CheckedAction maintained by that global instance. > Support override of CheckedAction > --------------------------------- > > Key: JBTM-1188 > URL: https://issues.jboss.org/browse/JBTM-1188 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Mark Little > > Hi Mark, > Assigned to you initially to confirm whether this is behavior we want. Please assign back to me with a comment if we do need this and I will implement it. Otherwise please do reject it. > BasicAction::setCheckedAction is protected so cannot be called by user code (4.16.x and above). > The suggestion given at: > https://community.jboss.org/message/742293#742293 > Would therefore not work with current versions of Narayana. > Thanks, > Tom -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1188) Support override of CheckedAction

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1188?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1188: ----------------------------------- There's a good reason it's protected at the moment: changing the CheckedAction is not something that we'd encourage user/application code to do in an uncontrolled manner for a number of reasons, including thread safety and understanding of precisely when such a change might take affect within the lifecycle of a transaction. By making the method protected we are allowing people to create their own transaction implementations which could provide updates on a more dynamic and per-instance basis. But pushing this into BasicAction is not something I think we should support at this stage. > Support override of CheckedAction > --------------------------------- > > Key: JBTM-1188 > URL: https://issues.jboss.org/browse/JBTM-1188 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Mark Little > > Hi Mark, > Assigned to you initially to confirm whether this is behavior we want. Please assign back to me with a comment if we do need this and I will implement it. Otherwise please do reject it. > BasicAction::setCheckedAction is protected so cannot be called by user code (4.16.x and above). > The suggestion given at: > https://community.jboss.org/message/742293#742293 > Would therefore not work with current versions of Narayana. > Thanks, > Tom -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-668) Consider .NET interop

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-668?page=com.atlassian.jira.plugin.s... ] Mark Little closed JBTM-668. ---------------------------- > Consider .NET interop > --------------------- > > Key: JBTM-668 > URL: https://issues.jboss.org/browse/JBTM-668 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.Final > > > http://www.jnbridge.com/jnbpro-transactions.htm -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-668) Consider .NET interop

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-668?page=com.atlassian.jira.plugin.s... ] Mark Little resolved JBTM-668. ------------------------------ Resolution: Done With the advent of AMQP support from MSFT as well as REST transactions, there are now other alternatives to WS-*. Plus we've not had an update on this request for years. So closing for now. Can be reopened if sufficient requirement surfaces. > Consider .NET interop > --------------------- > > Key: JBTM-668 > URL: https://issues.jboss.org/browse/JBTM-668 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.Final > > > http://www.jnbridge.com/jnbpro-transactions.htm -- 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, 9 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