[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1804:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.5.Final)
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
> Key: JBTM-1804
> URL: https://issues.jboss.org/browse/JBTM-1804
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Amos Feng
> Fix For: 5.next
>
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1340:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.5.Final)
> BeanPopulator overhead needs looking into
> -----------------------------------------
>
> Key: JBTM-1340
> URL: https://issues.jboss.org/browse/JBTM-1340
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Common
> Affects Versions: 4.17.2
> Environment: Mac OS 10.7
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit.
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled
> 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance
> 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance
> 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init>
> 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString
> 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey
> 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName
> 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get
--
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 Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1854:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.5.Final)
> 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: Gytis Trikleris
> 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.next
(was: 5.2.5.Final)
> 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