May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-512) Update build to target JDK 7

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-512?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-512: ---------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 967794|https://bugzilla.redhat.com/show_bug.cgi?id=967794] Created a PR for this: https://github.com/jbossas/jboss-eap/pull/158 > Update build to target JDK 7 > ---------------------------- > > Key: WFLY-512 > URL: https://issues.jboss.org/browse/WFLY-512 > Project: WildFly > Issue Type: Sub-task > Components: Build System > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1044) Support LazyEnlistableManagedConnection detection

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1044: -------------------------------------- Summary: Support LazyEnlistableManagedConnection detection Key: JBJCA-1044 URL: https://issues.jboss.org/browse/JBJCA-1044 Project: IronJacamar Issue Type: Task Components: AS Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.1.0.CR1 The RAR info tool should detect if the ManagedConnection associated with each ManagedConnectionFactory implements javax.resource.spi.LazyEnlistableManagedConnection {noformat} Class: com.acme.eis.ManagedConnectionFactoryImpl Validating: No Enlistment: Yes CCI: No ConnectionFactory (com.acme.eis.ConnectionFactory): ... {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1043) Support DissociatableManagedConnection detection

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1043: -------------------------------------- Summary: Support DissociatableManagedConnection detection Key: JBJCA-1043 URL: https://issues.jboss.org/browse/JBJCA-1043 Project: IronJacamar Issue Type: Task Components: AS Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.1.0.CR1 The RAR info tool should detect if the ManagedConnection associated with each ManagedConnectionFactory implements javax.resource.spi.DissociatableManagedConnection {noformat} Class: com.acme.eis.ManagedConnectionFactoryImpl Validating: No Sharable: Yes CCI: No ConnectionFactory (com.acme.eis.ConnectionFactory): ... {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1403) RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1403: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 967842|https://bugzilla.redhat.com/show_bug.cgi?id=967842] Github PR: https://github.com/jbossas/jboss-eap/pull/155 > RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1403 > URL: https://issues.jboss.org/browse/WFLY-1403 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Alpha2 > > > The RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan in the domain mode testsuite contains a bug as it refers to 'maxFailOnePlan' plan instead of 'maxFailPercPlan'. Hence, if the test methods are not run in alphabetical order they will fail due to this bug. > This has been somewhat fixed by adding an explicit ordering of test methods in that class, but this is a workaround rather than a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1403) RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1403: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=967842, https://bugzilla.redhat.com/show_bug.cgi?id=969381 (was: https://bugzilla.redhat.com/show_bug.cgi?id=967842) > RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1403 > URL: https://issues.jboss.org/browse/WFLY-1403 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Alpha2 > > > The RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan in the domain mode testsuite contains a bug as it refers to 'maxFailOnePlan' plan instead of 'maxFailPercPlan'. Hence, if the test methods are not run in alphabetical order they will fail due to this bug. > This has been somewhat fixed by adding an explicit ordering of test methods in that class, but this is a workaround rather than a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1403) RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1403: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 969381|https://bugzilla.redhat.com/show_bug.cgi?id=969381] Created a PR for this: https://github.com/jbossas/jboss-eap/pull/157 > RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1403 > URL: https://issues.jboss.org/browse/WFLY-1403 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Alpha2 > > > The RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan in the domain mode testsuite contains a bug as it refers to 'maxFailOnePlan' plan instead of 'maxFailPercPlan'. Hence, if the test methods are not run in alphabetical order they will fail due to this bug. > This has been somewhat fixed by adding an explicit ordering of test methods in that class, but this is a workaround rather than a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1403) RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1403: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 969381|https://bugzilla.redhat.com/show_bug.cgi?id=969381] from NEW to ASSIGNED > RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1403 > URL: https://issues.jboss.org/browse/WFLY-1403 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Alpha2 > > > The RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan in the domain mode testsuite contains a bug as it refers to 'maxFailOnePlan' plan instead of 'maxFailPercPlan'. Hence, if the test methods are not run in alphabetical order they will fail due to this bug. > This has been somewhat fixed by adding an explicit ordering of test methods in that class, but this is a workaround rather than a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann updated WFLY-1406: ------------------------------------- Attachment: javap.log The output of "javac -version" is: javac 1.7.0_21 The output of "javap -s -c -verbose de.shop.artikelverwaltung.domain.package-info" is attached in javap.log > Hibernate cannot process package-info.java any more > --------------------------------------------------- > > Key: WFLY-1406 > URL: https://issues.jboss.org/browse/WFLY-1406 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > Attachments: javap.log, server.log, tar.log > > > I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError: > "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below. > Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1: > @XmlAccessorType(FIELD) > @Vetoed > package de.shop.artikelverwaltung.domain; > import static javax.xml.bind.annotation.XmlAccessType.FIELD; > import javax.enterprise.inject.Vetoed; > import javax.xml.bind.annotation.XmlAccessorType; > The stacktrace: > ... > 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21] > at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final] > at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info > at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21] > at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final] > ... 28 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1431) org.jboss.as.test.integration.ejb.interceptor.lifecycle.chains.InterceptorLifecycleSFSBTestCase failed

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-1431?page=com.atlassian.jira.plugin.... ] Chao Wang updated WFLY-1431: ---------------------------- Attachment: WFLY-1431.patch attach patch > org.jboss.as.test.integration.ejb.interceptor.lifecycle.chains.InterceptorLifecycleSFSBTestCase failed > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-1431 > URL: https://issues.jboss.org/browse/WFLY-1431 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Attachments: WFLY-1431.patch > > > org.jboss.as.test.integration.ejb.interceptor.lifecycle.chains.InterceptorLifecycleSFSBTestCase failed with > {noformat} > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:92) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertTrue(Assert.java:54) > at org.jboss.as.test.integration.ejb.interceptor.lifecycle.chains.InterceptorLifecycleSFSBTestCase.testInterceptorPostConstructWithProceed(InterceptorLifecycleSFSBTestCase.java:67) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:128) > at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:107) > at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:214) > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) > at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) > at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792) > at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:527) > at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:263) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:915) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1403) RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1403: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> made a comment on [bug 967842|https://bugzilla.redhat.com/show_bug.cgi?id=967842] Changing flags from jboss‑eap‑6.1.1 to jboss‑eap‑6.2.0 as this bugzilla is an EAP 6.2 one. I will clone this BZ for 6.1.1 and also create a new PR for EAP 6.1.1. > RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan incorrectly refers to a rollout plan from different test method > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1403 > URL: https://issues.jboss.org/browse/WFLY-1403 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Alpha2 > > > The RolloutPlanTestCase#testMaxFailServersPercentageRolloutPlan in the domain mode testsuite contains a bug as it refers to 'maxFailOnePlan' plan instead of 'maxFailPercPlan'. Hence, if the test methods are not run in alphabetical order they will fail due to this bug. > This has been somewhat fixed by adding an explicit ordering of test methods in that class, but this is a workaround rather than a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2013