March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1794) OOBTest method testNonBlockingUnicastOOBMessage fails to correctly receive all OOB mssages

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1794?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1794. ---------------------------- Resolution: Done > OOBTest method testNonBlockingUnicastOOBMessage fails to correctly receive all OOB mssages > ------------------------------------------------------------------------------------------- > > Key: JGRP-1794 > URL: https://issues.jboss.org/browse/JGRP-1794 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Solaris, RHEL, Windows, HPUX > tcp stack only > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > This test fails regularly on multiple platforms. It doesn't fail all the time, but perhaps on 5/10 platform executions. > The test consists of a sender and a receiver. The receiver B will receive OOB messages but blocks on a latch for 25 seconds when it receives a non-OOB message. After 25 seconds, it unblocks and continues receiving > The test does this: > - send 1 regular message from A -> B > - send 9 OOB meesages from A -> B > - wait 20 seconds for messages to arrive > - check that all 9 OOB messages have arrived > - unblock the latch > - check that all 10 message have arrived > The test failures all involve the first 9 OOB messages not arriving completely. For example, sample lists of received messages before the first 20 second interval are: > [3,2,6,8,9,10,4] > [2,3,4,8,9,5] > [2,3,4,8,7,9] > [2,3,5,4,6] > So, it appears that either the messages are slow to arrive or not arriving at all. > A correct result looks like this: > {noformat} > list = [2, 4, 3, 7, 8, 9, 10, 5, 6] > [main]: releasing latch > list = [2, 4, 3, 7, 8, 9, 10, 5, 6, 1] > {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, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1806) UnicastLoopbackTest fails to receive all messages in the allotted time

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1806?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1806: --------------------------- Fix Version/s: 3.2.14 (was: 3.2.13) > UnicastLoopbackTest fails to receive all messages in the allotted time > ---------------------------------------------------------------------- > > Key: JGRP-1806 > URL: https://issues.jboss.org/browse/JGRP-1806 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: RHEL, Windows, Solaris > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.14 > > > UnicastLoopbackTest.testUnicastMessagesWithLoopback() is failing with the following error: > {noformat} > Error Message > Test timed out before all messages were received > Stacktrace > java.lang.AssertionError > at org.testng.Assert.fail(Assert.java:94) > at org.jgroups.tests.UnicastLoopbackTest.testUnicastMsgsWithLoopback(UnicastLoopbackTest.java:78) > {noformat} > The test does the following: > - creates one channel with loopback enabled in the transport > - the channel is assigned a receiver which collects the messages received and sets a Boolean valued Promise when all messages have been received > - the channel sends 1000 messages to itself in a burst > - waits 20 seconds for the promise to be set to true > The test fails because the messages do not arrive within the allotted 20 seconds. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1806) UnicastLoopbackTest fails to receive all messages in the allotted time

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1806?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1806: --------------------------- Fix Version/s: 3.2.13 (was: 3.2.14) > UnicastLoopbackTest fails to receive all messages in the allotted time > ---------------------------------------------------------------------- > > Key: JGRP-1806 > URL: https://issues.jboss.org/browse/JGRP-1806 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: RHEL, Windows, Solaris > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > UnicastLoopbackTest.testUnicastMessagesWithLoopback() is failing with the following error: > {noformat} > Error Message > Test timed out before all messages were received > Stacktrace > java.lang.AssertionError > at org.testng.Assert.fail(Assert.java:94) > at org.jgroups.tests.UnicastLoopbackTest.testUnicastMsgsWithLoopback(UnicastLoopbackTest.java:78) > {noformat} > The test does the following: > - creates one channel with loopback enabled in the transport > - the channel is assigned a receiver which collects the messages received and sets a Boolean valued Promise when all messages have been received > - the channel sends 1000 messages to itself in a burst > - waits 20 seconds for the promise to be set to true > The test fails because the messages do not arrive within the allotted 20 seconds. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1806) UnicastLoopbackTest fails to receive all messages in the allotted time

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1806?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1806. ---------------------------- Resolution: Done > UnicastLoopbackTest fails to receive all messages in the allotted time > ---------------------------------------------------------------------- > > Key: JGRP-1806 > URL: https://issues.jboss.org/browse/JGRP-1806 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: RHEL, Windows, Solaris > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > UnicastLoopbackTest.testUnicastMessagesWithLoopback() is failing with the following error: > {noformat} > Error Message > Test timed out before all messages were received > Stacktrace > java.lang.AssertionError > at org.testng.Assert.fail(Assert.java:94) > at org.jgroups.tests.UnicastLoopbackTest.testUnicastMsgsWithLoopback(UnicastLoopbackTest.java:78) > {noformat} > The test does the following: > - creates one channel with loopback enabled in the transport > - the channel is assigned a receiver which collects the messages received and sets a Boolean valued Promise when all messages have been received > - the channel sends 1000 messages to itself in a burst > - waits 20 seconds for the promise to be set to true > The test fails because the messages do not arrive within the allotted 20 seconds. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1802) OverlappingUnicastMergeTest fails to receive all messages

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1802?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1802. ---------------------------- Resolution: Done > OverlappingUnicastMergeTest fails to receive all messages > --------------------------------------------------------- > > Key: JGRP-1802 > URL: https://issues.jboss.org/browse/JGRP-1802 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Solaris, RHEL > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > OverlappingUnicastMergeTest does the following: > - set up three channels a,b,c with the layers MERGE2, VERIFY_SUSPECT and FC removed > - the receiver of each channel will look at all incoming messages: if mcast, ignore it; if unicast, add to the list of messages received > - inject some new view into the channels which represents a view configuration which should be recovered from > - send messages to the channels and check that the messages are received, despite the injected view > OverlappingUnicastMergeTest this test is failing in a number of ways (i.e. many of the test methods are failing within the test class on multiple platforms. > What we expect to see is: > {noformat} > receiver A: ucasts=15 > receiver B: ucasts=15 > receiver C: ucasts=15 > {noformat} > What we instead see is: > {noformat} > receiver A: ucasts=15 > receiver B: ucasts=11 > ucasts for B: > B: unicast msg #1 from B B: unicast msg #2 from B B: unicast msg #3 from B B: unicast msg #4 from B B: unicast msg #5 from B A: unicast msg #1 from A C: unicast msg #2 from C C: unicast msg #3 from C A: unicast msg #4 from A C: unicast msg #4 from C C: unicast msg #5 from C > {noformat} > The order here is the order in which the unicasts were received from all three senders by the single receiver. For example, in the above, in testWithViewBC, channel A should receive messages #1 through #5 from channels A, B and C, but it does not receive #1 from channel C. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3130) Add a custom RuntimeException to add-user utility.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3130?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3130: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1062595 > Add a custom RuntimeException to add-user utility. > -------------------------------------------------- > > Key: WFLY-3130 > URL: https://issues.jboss.org/browse/WFLY-3130 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > The add-user utility uses a RuntimeException to indicate failure in non-interactive mode, this does not look good so should switch it to a custom exception of our own. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3130) Add a custom RuntimeException to add-user utility.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3130: -------------------------------------- Summary: Add a custom RuntimeException to add-user utility. Key: WFLY-3130 URL: https://issues.jboss.org/browse/WFLY-3130 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.1.Final The add-user utility uses a RuntimeException to indicate failure in non-interactive mode, this does not look good so should switch it to a custom exception of our own. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-951) It is not possible to enable AtomicActionExpiryScanner in EAP 6.x

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-951?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris commented on WFLY-951: -------------------------------------- Sorry for delayed response. I have quite a lot on my plate at the moment. But I think I could sort this out in April, if that's all right? > It is not possible to enable AtomicActionExpiryScanner in EAP 6.x > ----------------------------------------------------------------- > > Key: WFLY-951 > URL: https://issues.jboss.org/browse/WFLY-951 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Environment: JBoss EAP 6.01 > Reporter: Tom Ross > Assignee: Gytis Trikleris > > It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below: > {noformat} > <system-properties> > <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner\\s+com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/> > </system-properties> > {noformat} > Unfortunately the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no easy way of removing transaction manager debris from object store. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3129) Update to HAL 2.2.0.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-3129: --------------------------------- Summary: Update to HAL 2.2.0.Final Key: WFLY-3129 URL: https://issues.jboss.org/browse/WFLY-3129 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Priority: Blocker Fix For: 8.0.1.Final This release contains the slimmed HAL console (see HAL-381 for details) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3125) Update help text for add-user to reflect that password is checked against the configured policy.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3125: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1063888|https://bugzilla.redhat.com/show_bug.cgi?id=1063888] from ASSIGNED to POST > Update help text for add-user to reflect that password is checked against the configured policy. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3125 > URL: https://issues.jboss.org/browse/WFLY-3125 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > -- 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, 1 month

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 March 2014