December 2012 - jbossts-issues - Jboss List Archives

[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: ------------------------------- Fix Version/s: 5.0.0.M2 (was: 5.0.0.Final) > 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: Paul Robinson > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > 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. The default should be "enabled" providing the feature is enabled in the XTS server config. -- 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

12 years

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... ] Work on JBTM-986 stopped by Paul Robinson. > 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: Paul Robinson > Labels: assign > Fix For: 5.0.0.M2 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > 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. The default should be "enabled" providing the feature is enabled in the XTS server config. -- 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

12 years

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: ------------------------------- Original Estimate: 4 days (was: 3 days) Remaining Estimate: 4 days (was: 3 days) > 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: Paul Robinson > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 4 days > Remaining Estimate: 4 days > > 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. The default should be "enabled" providing the feature is enabled in the XTS server config. -- 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

12 years

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 commented on JBTM-986: ------------------------------------ Update the quickstarts to use it. > 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: Paul Robinson > Labels: assign > Fix For: 5.0.0.Final > > Original Estimate: 4 days > Remaining Estimate: 4 days > > 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. The default should be "enabled" providing the feature is enabled in the XTS server config. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1393) XTSDemoTest fails because jbossHome does not exist

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1393?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1393. --------------------------------- Resolution: Done > XTSDemoTest fails because jbossHome does not exist > -------------------------------------------------- > > Key: JBTM-1393 > URL: https://issues.jboss.org/browse/JBTM-1393 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 15 minutes > Remaining Estimate: 0 minutes > > See: http://172.17.131.2/job/btny-EAP61-quickstarts/570 > {noformat} > Tests in error: > org.jboss.jbossts.xts.demotest.XTSDemoTest: jbossHome 'C:\hudson\workspace\jbossts-narayana-skipTests\jboss-as\build\target\jboss-as-7.2.0.Alpha1-SNAPSHOT' must exist > {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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1354) JCA recovery race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1354?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1354: ------------------------------------- http://172.17.131.2/job/jbossts-narayana-java6-ipv6-dualstack/61/ > JCA recovery race condition > --------------------------- > > Key: JBTM-1354 > URL: https://issues.jboss.org/browse/JBTM-1354 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, JTA, Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > Evidenced in SimpleIsolatedServers::testSimultaneousRecovery > Basically XATerminatorImple -> SAA::activate() -> XAResourceRecord::restore_state() -> getNewXAResource() -> XARecoveryModule::getNewXAResource() > At this point _xidScans may be none-null but still only partial from the first scan: periodicWorkSecondPass -> bottomUpRecovery -> resourceInitiatedRecoveryForRecoveryHelpers -> xaRecovery > if (_xidScans == null) > _xidScans = new Hashtable<XAResource,RecoveryXids>(); > What I am not sure of is whether we should synchronize bottomUpRecovery and getNewXAResource as that would stop this race condition. Gonna give that a whirl. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1394) TXFramework ATTest fails because of unhandled TransactionRolledBackException

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1394?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1394: -------------------------------- Original Estimate: 2 days (was: 1 hour) Remaining Estimate: 2 days (was: 1 hour) > TXFramework ATTest fails because of unhandled TransactionRolledBackException > ---------------------------------------------------------------------------- > > Key: JBTM-1394 > URL: https://issues.jboss.org/browse/JBTM-1394 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TXFramework > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > See: http://172.17.131.2/job/jbossts-narayana-java7/98 > {noformat} > Tests in error: > testSimple(org.jboss.narayana.txframework.functional.ATTest) > testMultiInvoke(org.jboss.narayana.txframework.functional.ATTest) > {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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1393) XTSDemoTest fails because jbossHome does not exist

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1393?page=com.atlassian.jira.plugin.... ] Paul Robinson logged work on JBTM-1393: --------------------------------------- Author: Paul Robinson Created on: 14/Dec/12 10:54 AM Start Date: 14/Dec/12 10:54 AM Worklog Time Spent: 15 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour) Time Spent: 15 minutes Worklog Id: (was: 12428219) > XTSDemoTest fails because jbossHome does not exist > -------------------------------------------------- > > Key: JBTM-1393 > URL: https://issues.jboss.org/browse/JBTM-1393 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 1 hour > Time Spent: 15 minutes > Remaining Estimate: 0 minutes > > See: http://172.17.131.2/job/btny-EAP61-quickstarts/570 > {noformat} > Tests in error: > org.jboss.jbossts.xts.demotest.XTSDemoTest: jbossHome 'C:\hudson\workspace\jbossts-narayana-skipTests\jboss-as\build\target\jboss-as-7.2.0.Alpha1-SNAPSHOT' must exist > {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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1380) Build times out because of not enough PermGen space

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1380?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1380: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Build times out because of not enough PermGen space > --------------------------------------------------- > > Key: JBTM-1380 > URL: https://issues.jboss.org/browse/JBTM-1380 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Fix For: 4.17.4, 5.0.0.M2 > > > http://172.17.131.2/job/jbossts-narayana-java7/93. This build timed out and surefire log says that it ran out of PermGen space -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1355) Merge XTS JUnit and Arquillian tests

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1355?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1355: -------------------------------- Issue Type: Task (was: Feature Request) > Merge XTS JUnit and Arquillian tests > ------------------------------------ > > Key: JBTM-1355 > URL: https://issues.jboss.org/browse/JBTM-1355 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 4.17.4, 5.0.0.M2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When migrating the XTS tests to Arquillian, we wanted to make sure that the old tests where still functional whilst the Arquillian counterparts stabilized. As a result we now have two classes for each test. The Arquillian test delegates each @Test method to the corresponding @Test in the old suite. > For example: > We have the actual test in: > ./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiClose.java > And then a Arquillian JUnit test which just calls the test methods above is here: > ./XTS/localjunit/WSTX/src/test/java/com/arjuna/wst11/tests/arq/ba/MultiCloseTest.java > To resolve this issue, we should remove the tests under './XTS/localjunit/WSTX/src/main/java' and merge the test methods into Arquillian test. At the end of this process "./XTS/localjunit/WSTX/src/main" should be empty (and thus removed). > This applies to most, if not all suites under "./XTS/localjunit/". -- 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

12 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 December 2012