August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2486) JDBC object store closes connections after resultset/statements which is incorrect order

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2486?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2486: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JDBC object store closes connections after resultset/statements which is incorrect order > ---------------------------------------------------------------------------------------- > > Key: JBTM-2486 > URL: https://issues.jboss.org/browse/JBTM-2486 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As reported by IronJacamar team we should treat the JDBC resources as a stack. > Specific case reported: > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/cl... > https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/cl... > https://gist.github.com/maeste/835073a1e8ea6e38b9bd -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2487) Initialize method of JDBC object store driver uses a connection outside of a try with resources

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2487: ----------------------------------- Summary: Initialize method of JDBC object store driver uses a connection outside of a try with resources Key: JBTM-2487 URL: https://issues.jboss.org/browse/JBTM-2487 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Offending code: https://github.com/jbosstm/narayana/blob/5.2.1.Final/ArjunaCore/arjuna/cl... Technique to use: https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceC... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2454) Internal IBM J9 compiler error building XTS

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2454?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2454: ------------------------------------- Fortunately (or not) revised CI config now fails in the reproducing job: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2454-narayana-ibm-jdk/2/ {code} java -version export TXF_TESTS=0 XTS_TESTS=0 txbridge=0 JTA_CDI_TESTS=0 XTS_AS_TESTS=0 RTS_AS_TESTS=0 RTS_TESTS=0 NARAYANA_TESTS=0 BLACKTIE=0 QA_TESTS=0 export NARAYANA_BUILD=1 AS_BUILD=1 SUN_ORB=0 JAC_ORB=0 IBM_ORB=1 PROFILE=NONE ./scripts/hudson/narayana.sh -Denforcer.skip=true export JBOSS_HOME=`pwd`/jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT cp jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT/docs/examples/configs/standalone-xts.xml jboss-as/build/target/wildfly-10.0.0.Beta1-SNAPSHOT/standalone/configuration/ ./build.sh -f XTS/localjunit/pom.xml -Parq -Dorg.jboss.remoting-jmx.timeout=300 clean install {code} I am going to try to execute each command by hand in the job config instead of lauching localjunit/* and see if that will pass. > Internal IBM J9 compiler error building XTS > ------------------------------------------- > > Key: JBTM-2454 > URL: https://issues.jboss.org/browse/JBTM-2454 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Attachments: compensations.tar > > > On lancel we get the following error. I am unable to reproduce it on my laptop. > The compiler details are: > {quote} > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr1-20150417_01(SR1)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150410_243669 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR1_20150410_1531_B243669 > JIT - tr.r14.java_20150402_88976.03 > GC - R28_Java8_SR1_20150410_1531_B243669_CMPRSS > J9CL - 20150410_243669) > JCL - 20150413_01 based on Oracle jdk8u45-b13 > {quote} > and the build error is: > {quote} > [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ localjunit-disabled-context-propagation-tests --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 12 source files to /home/hudson/workspace/narayana-ibm-jdk/XTS/localjunit/disabled-context-propagation/target/test-classes > An exception has occurred in the compiler (1.8.0-internal). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report. Thank you. > java.lang.NullPointerException > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:142) > at javax.lang.model.util.ElementScanner6.visitType(ElementScanner6.java:189) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:777) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.visitType(JavacProcessingEnvironment.java:758) > at com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1162) > at javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:157) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$ComputeAnnotationSet.scan(JavacProcessingEnvironment.java:798) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.findAnnotationsPresent(JavacProcessingEnvironment.java:993) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:891) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1182) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1182) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:868) > at com.sun.tools.javac.main.Main.compile(Main.java:535) > at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:141) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:150) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:152) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2328) Deprecate the HeuristicInformation interface

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2328?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2328. --------------------------------- Resolution: Done > Deprecate the HeuristicInformation interface > -------------------------------------------- > > Key: JBTM-2328 > URL: https://issues.jboss.org/browse/JBTM-2328 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > There exists and HeuristicInformation interface (https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes...) which was intended to allow an AbstractRecord implementor to provide additional details about the heuristic state of the record as well as provide access to tooling to clear the state of the heuristic within the (potentially remove) resource manager. > This has been decoupled from the tooling for many iterations (the ability to resolve the heuristic appears as though it was never wired up) and though Mike is updating the tooling to access the additional context of the heuristic state we do not propose to continue with this as the recommendation of resolving heuristics. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2482?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2482. ------------------------------- > Update pre-release.sh to update the version of Narayana in the performance repo > ------------------------------------------------------------------------------- > > Key: JBTM-2482 > URL: https://issues.jboss.org/browse/JBTM-2482 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.1 > > > Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2482) Update pre-release.sh to update the version of Narayana in the performance repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2482?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2482: -------------------------------- Fix Version/s: 5.2.1 (was: 5.next) > Update pre-release.sh to update the version of Narayana in the performance repo > ------------------------------------------------------------------------------- > > Key: JBTM-2482 > URL: https://issues.jboss.org/browse/JBTM-2482 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.1 > > > Currently the version number in the performance repo is a manual step -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2460. ------------------------------- > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.1 > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2460: -------------------------------- Fix Version/s: 5.2.1 (was: 5.next) > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.1 > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2477. ------------------------------- Resolution: Rejected > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2477) Measure timed out transactions in TxStats

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2477?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2477: -------------------------------- Fix Version/s: (was: 5.next) > Measure timed out transactions in TxStats > ----------------------------------------- > > Key: JBTM-2477 > URL: https://issues.jboss.org/browse/JBTM-2477 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 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 August 2015