September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1855: --------------------------------------- [~tomjenkinson], I looked through the commit and it seems good to me. > No unit tests for queue with RTS transport > ------------------------------------------ > > Key: JBTM-1855 > URL: https://issues.jboss.org/browse/JBTM-1855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, REST, Testing > Reporter: Crispin Boylan > Assignee: Amos Feng > Fix For: 5.0.0.M5 > > > There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml. > When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error: > 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:///127.0.0.1:49804) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</volatileParticipantEnlistmentURI></coordinator> > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:] > at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea] -- 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-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1938: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug 1009931|https://bugzilla.redhat.com/show_bug.cgi?id=1009931] Hi Tom, thanks for the fix. >From my point of view the bz https://bugzilla.redhat.com/show_bug.cgi?id=971358 was fixed. But Stefano could have some more input on it. I'm not sure. Ondra > Caching of datasource for JDBC store incompatible with WildFly :reload operation > -------------------------------------------------------------------------------- > > Key: JBTM-1938 > URL: https://issues.jboss.org/browse/JBTM-1938 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). > Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- 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-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1938: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1009931 > Caching of datasource for JDBC store incompatible with WildFly :reload operation > -------------------------------------------------------------------------------- > > Key: JBTM-1938 > URL: https://issues.jboss.org/browse/JBTM-1938 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). > Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- 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-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1938: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/445, https://github.com/jbosstm/narayana/pull/446 > Caching of datasource for JDBC store incompatible with WildFly :reload operation > -------------------------------------------------------------------------------- > > Key: JBTM-1938 > URL: https://issues.jboss.org/browse/JBTM-1938 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.11, 5.0.0.M5 > > > The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). > Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- 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-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1938: ----------------------------------- Summary: Caching of datasource for JDBC store incompatible with WildFly :reload operation Key: JBTM-1938 URL: https://issues.jboss.org/browse/JBTM-1938 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.11, 5.0.0.M5 The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace). Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called. -- 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-987) Document Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-987: ------------------------------- Component/s: Documentation > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Optional > Labels: Documentation,, TXFramework > Fix For: 5.0.0.Final > > > Should cover all existing features and provide a skeleton for the final document. -- 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-987) Document Compensations API

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-987?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-987: ------------------------------- Labels: TXFramework (was: Documentation, TXFramework) > Document Compensations API > -------------------------- > > Key: JBTM-987 > URL: https://issues.jboss.org/browse/JBTM-987 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Optional > Labels: TXFramework > Fix For: 5.0.0.Final > > > Should cover all existing features and provide a skeleton for the final document. -- 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-1932) Consider using the same jboss-parent as other JBoss community projects such as WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1932?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1932: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Consider using the same jboss-parent as other JBoss community projects such as WildFly > -------------------------------------------------------------------------------------- > > Key: JBTM-1932 > URL: https://issues.jboss.org/browse/JBTM-1932 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M5 > > > It would standardise the versions of the build plugins we use and would ensure that we build with java versions that are compatible with WildFly. On the flip side it will restrict our community options although many of the variables do appear to be configurable: > https://github.com/jboss/jboss-parent-pom/ -- 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-1444) Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1444: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback > ---------------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Labels: assign > Fix For: 5.0.0.M5 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Check what happens when each possible Exception is thrown from a WS-AT participant's commit or Rollback method. > For each case consider whether enough logging is provided. -- 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-1558) Prune redundant code from jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1558?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1558: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Prune redundant code from jboss-transaction-spi > ----------------------------------------------- > > Key: JBTM-1558 > URL: https://issues.jboss.org/browse/JBTM-1558 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > Attachments: as8.zip, ij-tx-spi.txt > > > We can use jboss-transaction-spi to get started > There is much old code in jboss-transaction-spi that does not get used in AS7 and does not apply to Narayana. > Run tattletale over AS8, identify redundant methods and add new SPI functions if necessary -- 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 September 2013