August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2120) Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2120?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2120: -------------------------------- Component/s: Transaction Core > Add a deferred exceptions to the rollback exception if the first resource throws a heuristic rollback > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-2120 > URL: https://issues.jboss.org/browse/JBTM-2120 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Pull https://github.com/jbosstm/narayana/pull/598 added deferred throwables in case the XAR::end fails during commit. It doesn't handle the case of the HEURISTIC_ROLLBACK of a first resource where Narayana rolls back the remaining participants and then clears the failed/heuristic lists (and marks the txn as rolled back). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2488: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/899 > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2488) Fix findbugs issues in rts modules

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2488?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2488: ----------------------------------- Description: The relevant issues can be seen by running: bq. mvn clean site -DskipTests -Pfindbugs -f rts/pom.xml was: The relevant issues can be seen by running: bq. mvn site -DskipTests -Pfindbugs -f rts/pom.xml > Fix findbugs issues in rts modules > ---------------------------------- > > Key: JBTM-2488 > URL: https://issues.jboss.org/browse/JBTM-2488 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The relevant issues can be seen by running: > bq. mvn clean site -DskipTests -Pfindbugs -f rts/pom.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2467) REST-AT undertow performance tests and quickstart fail

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2467: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST-AT undertow performance tests and quickstart fail > ------------------------------------------------------ > > Key: JBTM-2467 > URL: https://issues.jboss.org/browse/JBTM-2467 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue)

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2234: --------------------------------- [~mmusgrov], can you show me how to start these jts performance tests ? > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Optional > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Spring

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Amos Feng updated JBTM-855: --------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/148 update to add the jta example > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2467) REST-AT undertow performance tests and quickstart fail

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2467: ----------------------------------- Summary: REST-AT undertow performance tests and quickstart fail (was: REST-AT performance tests fail) > REST-AT undertow performance tests and quickstart fail > ------------------------------------------------------ > > Key: JBTM-2467 > URL: https://issues.jboss.org/browse/JBTM-2467 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2467) REST-AT performance tests fail

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2467: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/147, https://github.com/jbosstm/performance/pull/17 > REST-AT performance tests fail > ------------------------------ > > Key: JBTM-2467 > URL: https://issues.jboss.org/browse/JBTM-2467 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 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 updated JBTM-2454: -------------------------------- Comment: was deleted (was: http://albany.eng.hst.ams2.redhat.com/job/JBTM-2454-narayana-ibm-jdk/) > 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: Tom Jenkinson > 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)

9 years, 3 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: ------------------------------------- Added a work around to code base such that we execute the localjunit sub modules by hand in narayana.sh rather than the parent pom > 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: Tom Jenkinson > 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)

9 years, 3 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