[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:
--------------------------------
Priority: Major (was: Minor)
> 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.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-2492) Build and deploy Blacktie as part of BRP.xml
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2492?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2492:
--------------------------------
Priority: Minor (was: Major)
> Build and deploy Blacktie as part of BRP.xml
> --------------------------------------------
>
> Key: JBTM-2492
> URL: https://issues.jboss.org/browse/JBTM-2492
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Release Process
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.next
>
>
> We only update the Blacktie java artifacts so these should be able to be done from any machine:
> {code}
> call "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat"
> build.bat -f blacktie\wildfly-blacktie\pom.xml install -DskipTests
> build.bat -f blacktie\pom.xml install -DskipTests
> build.bat -f blacktie\pom.xml deploy -DskipTests
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-1854) Journal failures in CI test suite on JDKORB
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris reassigned JBTM-1854:
-------------------------------------
Assignee: Michael Musgrove (was: Gytis Trikleris)
> Journal failures in CI test suite on JDKORB
> -------------------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
> Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz
>
>
> The first CI job link includes:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
> The second CI job link includes:
> JTSRemote_ImplicitPropagationTest failure
> CrashRecovery02_2_Test46 hang
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-2524) CMRIntegrationTest failed with can not start the container
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2524?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2524:
--------------------------------
Fix Version/s: 5.2.5.Final
(was: 5.next)
> CMRIntegrationTest failed with can not start the container
> ----------------------------------------------------------
>
> Key: JBTM-2524
> URL: https://issues.jboss.org/browse/JBTM-2524
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA, Testing
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.2.5.Final
>
>
> http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-jdk8/PROFIL...
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Sep 24, 2015 8:54:59 AM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.9.Final
> [0m08:55:01,492 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
> [0m[0m08:55:02,403 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> [0m[0m08:55:02,728 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.0.0.CR4 "Kenny" starting
> [0m[0m08:55:06,434 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[31m08:55:06,456 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("http-connector" => "http-connector")
> ]) - failure description: "WFLYCTL0155: endpoint may not be null"
> {code}
> I think we need to avoid to using the static ArjunaJTA/jta/src/test/resources/standalone-cmr.xml and try to clone the jboss-as/standalone/configuration/standalone-full.xml with adding the cmr configs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-2524) CMRIntegrationTest failed with can not start the container
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2524?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2524.
-------------------------------
> CMRIntegrationTest failed with can not start the container
> ----------------------------------------------------------
>
> Key: JBTM-2524
> URL: https://issues.jboss.org/browse/JBTM-2524
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA, Testing
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.2.5.Final
>
>
> http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-jdk8/PROFIL...
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Sep 24, 2015 8:54:59 AM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.9.Final
> [0m08:55:01,492 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
> [0m[0m08:55:02,403 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> [0m[0m08:55:02,728 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.0.0.CR4 "Kenny" starting
> [0m[0m08:55:06,434 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[31m08:55:06,456 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("http-connector" => "http-connector")
> ]) - failure description: "WFLYCTL0155: endpoint may not be null"
> {code}
> I think we need to avoid to using the static ArjunaJTA/jta/src/test/resources/standalone-cmr.xml and try to clone the jboss-as/standalone/configuration/standalone-full.xml with adding the cmr configs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-2524) CMRIntegrationTest failed with can not start the container
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2524?page=com.atlassian.jira.plugin.... ]
Amos Feng updated JBTM-2524:
----------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> CMRIntegrationTest failed with can not start the container
> ----------------------------------------------------------
>
> Key: JBTM-2524
> URL: https://issues.jboss.org/browse/JBTM-2524
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA, Testing
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.next
>
>
> http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-jdk8/PROFIL...
> {code}
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
> Sep 24, 2015 8:54:59 AM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.1.Final
> Sep 24, 2015 8:55:00 AM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.9.Final
> [0m08:55:01,492 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
> [0m[0m08:55:02,403 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> [0m[0m08:55:02,728 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Core 2.0.0.CR4 "Kenny" starting
> [0m[0m08:55:06,434 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> [0m[31m08:55:06,456 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 20) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "default"),
> ("http-connector" => "http-connector")
> ]) - failure description: "WFLYCTL0155: endpoint may not be null"
> {code}
> I think we need to avoid to using the static ArjunaJTA/jta/src/test/resources/standalone-cmr.xml and try to clone the jboss-as/standalone/configuration/standalone-full.xml with adding the cmr configs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2115:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.5.Final)
> Not all classes are under code coverage
> ---------------------------------------
>
> Key: JBTM-2115
> URL: https://issues.jboss.org/browse/JBTM-2115
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.0.1
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The following poms contain skipped classes for code coverage:
> ArjunaCore/arjuna/pom.xml
> ArjunaJTA/jdbc/pom.xml
> ArjunaJTA/jta/pom.xml
> ArjunaJTA/spi/pom.xml
> XTS/localjunit/pom.xml
> We should aim to test everything
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months