August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9203) Clustering test failures with node0 and node1 configured

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9203?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-12612 to WFLY-9203: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9203 (was: JBEAP-12612) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering Test Suite (was: Clustering) (was: Test Suite) Affects Version/s: 11.0.0.Beta1 (was: 7.1.0.ER3) > Clustering test failures with node0 and node1 configured > -------------------------------------------------------- > > Key: WFLY-9203 > URL: https://issues.jboss.org/browse/WFLY-9203 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > > Several clustering (wildfly-ts-integ-clustering module) test start failing in ER3. > *reproduce* > w/o test ips - no failures > {noformat} > mvn clean test | tee no_mytestip > {noformat} > w/ test ips - 6 failures > {noformat} > mvn clean test -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 | tee mytestip > ... > Running org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.322 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase > test(org.jboss.as.test.clustering.cluster.dispatcher.CommandDispatcherTestCase) Time elapsed: 12.315 sec <<< ERROR! > javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/command-dispatcher/ClusterTopologyRetrieverBean", view is interface org.jboss.as.test.clustering.cluster.dispatcher.bean.ClusterTopologyRetriever, affinity is None > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:570) > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.293 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase > test(org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatefulEJBFailoverTestCase) Time elapsed: 12.286 sec <<< ERROR! > javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "/transactional-remote-stateful-ejb-failover-test/StatefulIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor?stateful" [Root exception is javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/transactional-remote-stateful-ejb-failover-test/StatefulIncrementorBean", view is interface org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor, affinity is None] > at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:158) > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.161 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBFailoverTestCase > test(org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBFailoverTestCase) Time elapsed: 12.153 sec <<< ERROR! > javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "/remote-stateful-ejb-failover-test/StatefulIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor?stateful" [Root exception is javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/remote-stateful-ejb-failover-test/StatefulIncrementorBean", view is interface org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor, affinity is None] > at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:158) > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.161 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBFailoverTestCase > test(org.jboss.as.test.clustering.cluster.ejb.remote.RemoteStatefulEJBFailoverTestCase) Time elapsed: 12.153 sec <<< ERROR! > javax.naming.CommunicationException: EJBCLIENT000062: Failed to look up "/remote-stateful-ejb-failover-test/StatefulIncrementorBean!org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor?stateful" [Root exception is javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/remote-stateful-ejb-failover-test/StatefulIncrementorBean", view is interface org.jboss.as.test.clustering.cluster.ejb.remote.bean.Incrementor, affinity is None] > at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:158) > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.324 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase > test(org.jboss.as.test.clustering.cluster.provider.ServiceProviderRegistrationTestCase) Time elapsed: 13.317 sec <<< ERROR! > javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/service-provider-registration/ServiceProviderRetrieverBean", view is interface org.jboss.as.test.clustering.cluster.provider.bean.ServiceProviderRetriever, affinity is None > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:570) > Running org.jboss.as.test.clustering.cluster.registry.RegistryTestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 12.398 sec <<< FAILURE! - in org.jboss.as.test.clustering.cluster.registry.RegistryTestCase > test(org.jboss.as.test.clustering.cluster.registry.RegistryTestCase) Time elapsed: 12.393 sec <<< ERROR! > javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/registry/RegistryRetrieverBean", view is interface org.jboss.as.test.clustering.cluster.registry.bean.RegistryRetriever, affinity is None > at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:570) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9035) TransactionAttribute annotation is inherited from interface which not according to the spec

by Radovan Stancel (JIRA)

[ https://issues.jboss.org/browse/WFLY-9035?page=com.atlassian.jira.plugin.... ] Radovan Stancel updated WFLY-9035: ---------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1466909 > TransactionAttribute annotation is inherited from interface which not according to the spec > ------------------------------------------------------------------------------------------- > > Key: WFLY-9035 > URL: https://issues.jboss.org/browse/WFLY-9035 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Radovan Stancel > Labels: transaction > > The annotation @TransactionAttribute is inherited from the business interface which is not according to the EJB specification. > Any annotation on the bean's implemenation class or deployment descriptor is overridden if the Interface is annotated with @TransactionAttribute > The EJB 3.2 specification chapter 8.3.7 says > "For a session bean written to the EJB 3.x client view API, the transaction attributes are speci- > fied for those methods of the session bean class that correspond to the bean’s business inter- > face" > Also the Javadoc for TransactionAttribute (http://docs.oracle.com/javaee/7/api/javax/ejb/TransactionAttribute.html) mention the bean class only. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9035) TransactionAttribute annotation is inherited from interface which not according to the spec

by Radovan Stancel (JIRA)

[ https://issues.jboss.org/browse/WFLY-9035?page=com.atlassian.jira.plugin.... ] Radovan Stancel reassigned WFLY-9035: ------------------------------------- Assignee: Radovan Stancel > TransactionAttribute annotation is inherited from interface which not according to the spec > ------------------------------------------------------------------------------------------- > > Key: WFLY-9035 > URL: https://issues.jboss.org/browse/WFLY-9035 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Radovan Stancel > Labels: transaction > > The annotation @TransactionAttribute is inherited from the business interface which is not according to the EJB specification. > Any annotation on the bean's implemenation class or deployment descriptor is overridden if the Interface is annotated with @TransactionAttribute > The EJB 3.2 specification chapter 8.3.7 says > "For a session bean written to the EJB 3.x client view API, the transaction attributes are speci- > fied for those methods of the session bean class that correspond to the bean’s business inter- > face" > Also the Javadoc for TransactionAttribute (http://docs.oracle.com/javaee/7/api/javax/ejb/TransactionAttribute.html) mention the bean class only. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1696) Events that are already expired at insert time, doesn't always produce activations

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1696?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1696: --------------------------------------- Looks like it is related to this commit https://github.com/baldimir/drools/commit/0b72f3f6e09b2a625f8f14d6f3aed44... > Events that are already expired at insert time, doesn't always produce activations > ---------------------------------------------------------------------------------- > > Key: DROOLS-1696 > URL: https://issues.jboss.org/browse/DROOLS-1696 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Fix For: 7.2.0.Final > > > When inserting events that have timestamp in the past and don't have expiration defined (@expires), the events don't always produce activations. See a test example [1]. This test fails "randomly". > I will create a PR with a reproducer. > [1] https://gist.github.com/baldimir/fb9808ce1e6d49c83dc24570b3cb6093 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9202) /subsystem=messaging-activemq:remove fails when not run in batch

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9202?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-12610 to WFLY-9202: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9202 (was: JBEAP-12610) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: 11.0.0.Beta1 (was: 7.1.0.ER3) > /subsystem=messaging-activemq:remove fails when not run in batch > ---------------------------------------------------------------- > > Key: WFLY-9202 > URL: https://issues.jboss.org/browse/WFLY-9202 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 11.0.0.Beta1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > > Calling the following command in ER3 fails (passed with reload required in ER2.2): > {noformat} > /subsystem=messaging-activemq:remove() > {noformat} > {noformat} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.messaging-activemq.client-thread-pool was depended upon by service jboss.messaging-activemq.default.jms.manager", > "rolled-back" => true, > "response-headers" => undefined > } > {noformat} > The command now needs to be run in batch to succeed. I'm tempted to call this a blocker due to management operation backward compatibility (breaks scripts which don't run the remove operation in batch), [~okalman] WDYT? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2208) FlowControlUnitTest.testNonBlockingFlowControlWithMessageQueueBlocking() sometimes blocks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2208?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2208. ---------------------------- Resolution: Done > FlowControlUnitTest.testNonBlockingFlowControlWithMessageQueueBlocking() sometimes blocks > ----------------------------------------------------------------------------------------- > > Key: JGRP-2208 > URL: https://issues.jboss.org/browse/JGRP-2208 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.5 > > > Possibly because the full (blocking) message queue is not cleared on stop()? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2208) FlowControlUnitTest.testNonBlockingFlowControlWithMessageQueueBlocking() sometimes blocks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2208?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2208: -------------------------------- This was changed by adding a task to {{UFC_NB}} and {{MFC_NB}} which is run every {{max_block_time}} ms and asks receivers for credits should the senders have insufficient credits. > FlowControlUnitTest.testNonBlockingFlowControlWithMessageQueueBlocking() sometimes blocks > ----------------------------------------------------------------------------------------- > > Key: JGRP-2208 > URL: https://issues.jboss.org/browse/JGRP-2208 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.5 > > > Possibly because the full (blocking) message queue is not cleared on stop()? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9201) Upgrade to transaction client 1.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9201?page=com.atlassian.jira.plugin.... ] Kabir Khan moved JBEAP-12608 to WFLY-9201: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9201 (was: JBEAP-12608) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Transactions (was: Transactions) > Upgrade to transaction client 1.0.0.Final > ----------------------------------------- > > Key: WFLY-9201 > URL: https://issues.jboss.org/browse/WFLY-9201 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Kabir Khan > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9200) Upgrade to naming client 1.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9200?page=com.atlassian.jira.plugin.... ] Kabir Khan moved JBEAP-12606 to WFLY-9200: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9200 (was: JBEAP-12606) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Naming (was: Naming) > Upgrade to naming client 1.0.0.Final > ------------------------------------ > > Key: WFLY-9200 > URL: https://issues.jboss.org/browse/WFLY-9200 > Project: WildFly > Issue Type: Component Upgrade > Components: Naming > Reporter: Kabir Khan > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9199) Upgrade to http client 1.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9199?page=com.atlassian.jira.plugin.... ] Kabir Khan moved JBEAP-12604 to WFLY-9199: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9199 (was: JBEAP-12604) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) > Upgrade to http client 1.0.0.Final > ---------------------------------- > > Key: WFLY-9199 > URL: https://issues.jboss.org/browse/WFLY-9199 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Kabir Khan > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 August 2017