December 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2222) Rename TXFramework -> Compensations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2222?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2222. ------------------------------- > Rename TXFramework -> Compensations > ----------------------------------- > > Key: JBTM-2222 > URL: https://issues.jboss.org/browse/JBTM-2222 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.4 > > > TXFramework now just focuses on Compensating transactions. The ACID transaction improvements have been moved into XTS and REST components. Therefore, we should drop the TXFramework name in favour of "Compensations" or "Compensating Transactions". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2317) SAX parsing of properties file fails when offline

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2317?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2317. ------------------------------- > SAX parsing of properties file fails when offline > ------------------------------------------------- > > Key: JBTM-2317 > URL: https://issues.jboss.org/browse/JBTM-2317 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > The SAX parser verifies DTDs during parsing of the XML files, this is not done for the StAX parser. As our properties files usually link to the Sun DTD for properties on from java.sun.com this causes SAX parsing to fail when offline. > We only have one test that uses SAX parsing (SAX parsing was added for Android). The workaround is to access the XMLReader from the parser and disable validation and loading-external-dtd's. The unit test still works with this disabled so I think it is safe to ignore downloading the Sun properties DTD. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2208) Deprecate unused method from ActionManager

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2208?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2208. ------------------------------- > Deprecate unused method from ActionManager > ------------------------------------------ > > Key: JBTM-2208 > URL: https://issues.jboss.org/browse/JBTM-2208 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Transaction Core > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > Removed unused method from ActionManager, and thereby a System.currentTimeMillis call -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2253) Brandon CI node misconfiguration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2253?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2253. ------------------------------- > Brandon CI node misconfiguration > --------------------------------- > > Key: JBTM-2253 > URL: https://issues.jboss.org/browse/JBTM-2253 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana/639/PROFILE=BLACKTIE,jdk=jdk... > {code} > [0m[31m12:39:56,830 ERROR [org.codehaus.stomp.jms.ProtocolConverter] (StompConnect Transport: tcp:///127.0.0.1:44813) Connection is closed: org.codehaus.stomp.jms.ProtocolConverter@10c10e8 > [0m[31m12:39:56,831 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:44813) Caught an exception: Broken pipe: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) [rt.jar:1.7.0_51] > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) [rt.jar:1.7.0_51] > at java.net.SocketOutputStream.write(SocketOutputStream.java:159) [rt.jar:1.7.0_51] > at java.io.DataOutputStream.write(DataOutputStream.java:107) [rt.jar:1.7.0_51] > at java.io.FilterOutputStream.write(FilterOutputStream.java:97) [rt.jar:1.7.0_51] > at org.codehaus.stomp.StompMarshaller.marshal(StompMarshaller.java:83) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.tcp.TcpTransport.onStompFrame(TcpTransport.java:80) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.jms.ProtocolConverter.sendToStomp(ProtocolConverter.java:498) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:209) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101) [wildfly-blacktie-5.0.4.Final-SNAPSHOT.jar:5.0.4.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > [0mTests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 110.88 sec > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.TestTopic > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.162 sec > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.server.BlackTieServerTestCase > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.248 sec > Results : > Tests in error: > AtmiBrokerEnvXMLTest.testEnv:53 » UnknownHost brandon.buildnet.ncl.jboss.com: ... > TestConnection.setUp:29 » Configuration Could not create the orb management fu... > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2278) Allow the transaction manager suspend operation to succeed for JTS mode

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2278?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2278. ------------------------------- > Allow the transaction manager suspend operation to succeed for JTS mode > ----------------------------------------------------------------------- > > Key: JBTM-2278 > URL: https://issues.jboss.org/browse/JBTM-2278 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > It is not possible to perform TransactionManager::suspend operation during an afterCompletion call when the server is configured for JTS and has JacORB configured with interposition interceptors. This is because the transaction has not been used on the thread yet and when OTSManager.current() operation finds the PropagationContext in PICurrent to tries to recreate the hierarchy and ArjunaTransactionImple register_resource detects the transaction is no longer active so throws an Inactive exception causing suspend to fail. > SystemException is a valid response code from suspend but it would be desirable to try to avoid this when the transaction is local to the Synchronization. > Allowing suspend means this code would work: > public afterCompletion(status) { > tm.suspend() > tm.begin() > tm.commit() > } -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1939) Consider using awestruct to develop http://narayana.io

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1939?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1939. ------------------------------- > Consider using awestruct to develop http://narayana.io > ------------------------------------------------------ > > Key: JBTM-1939 > URL: https://issues.jboss.org/browse/JBTM-1939 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Awestruct appears to be a powerful and flexible tool to develop websites with. This task is to research the capabilities of the tool and determine if the benefits of awestruct apply to our website. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2182. ------------------------------- > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2218) testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2218?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2218. ------------------------------- > testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed > --------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2218 > URL: https://issues.jboss.org/browse/JBTM-2218 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > http://172.17.131.2/view/Status/job/narayana/575/PROFILE=XTS,jdk=jdk7.lat... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1369. ------------------------------- > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2286) Create a zip with all javadocs included

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2286?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2286. ------------------------------- > Create a zip with all javadocs included > --------------------------------------- > > Key: JBTM-2286 > URL: https://issues.jboss.org/browse/JBTM-2286 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Currently javadocs are split by component. It would be convenient to produce a single bundle of javadocs of all project as well for ease of publishing on the site. > What we are proposing is to produce a single Javadoc artifact for the Narayana project which has all the public API stuff (ignoring **/internal/**). Same as what you get with the JSE or JEE javadocs. A single link for users to see all public Narayana javadoc. > Each component will create its own JavaDocs as normal but a single uber zip would also be produced and this is what would be published on the site. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 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 2014