August 2015 - jbossts-issues - Jboss List Archives

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2467: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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)

8 years, 8 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: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > 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)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2468: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > xts, jts and rts performance comparison job has failures > -------------------------------------------------------- > > Key: JBTM-2468 > URL: https://issues.jboss.org/browse/JBTM-2468 > 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 weekly NCL jenkins job for performance comparison of jts/xts/rts has three issues: > - the throughput is coming out at 0 (I think it is because its very slow but it needs investigating); > - the jts component fails to configure wildfly into jts mode (I have temporarily disabled it in the job config); > - it runs against 9.0.0.Alpha2-SNAPSHOT (so it needs updating to run against the wildfly bi weekly builds) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

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.2) > 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, 8 months

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.2) > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2312) Wrong logging format of ARJUNA016005

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2312?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2312: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Wrong logging format of ARJUNA016005 > ------------------------------------ > > Key: JBTM-2312 > URL: https://issues.jboss.org/browse/JBTM-2312 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 4.17.24 > Reporter: Ondřej Chaloupka > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Logging format of warning warn_recovery_failedtorecover is strange or maybe better to say wrong. It looks: > {code} > WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016005: JTS XARecoveryModule.xaRecovery - failed to recover XAResource. status is $2 > {code} > This message came from XAResourceRecord.xaRecoverySecondPass and it's message warn_recovery_failedtorecover. The code with dolar sign seems to me a bit confusing. > I think it would be better first not have the dolar sign there and second rather to print string representation of the error code. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

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.2) > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2476: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2491) JTS and JacORB NS Docker images quickstart with Kubernetes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2491?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2491: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > JTS and JacORB NS Docker images quickstart with Kubernetes > ---------------------------------------------------------- > > Key: JBTM-2491 > URL: https://issues.jboss.org/browse/JBTM-2491 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create example Kubernetes configuration for JTS and JacORB NS Docker images. As well as a test case for them. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2485) Close and release nexus deployed artifacts from build script

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2485?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2485: -------------------------------- Fix Version/s: 5.next (was: 5.2.2) > Close and release nexus deployed artifacts from build script > ------------------------------------------------------------ > > Key: JBTM-2485 > URL: https://issues.jboss.org/browse/JBTM-2485 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Release Process > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > Currently we need to visit the nexus site during NRP, it would be nice to be able to execute these steps from the command line as part of the release process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 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