August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2245: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2296: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

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 updated JBTM-2328: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2409: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

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: 5.next (was: 5.2.1) > 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 > Fix For: 5.next > > > Will be useful for monitoring according to GSS -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2419: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/m...] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2433: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 1 month

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: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > 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 > > > 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, 1 month

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2015