March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1149) Recovery connection not closed correctly

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1149: -------------------------------------- Summary: Recovery connection not closed correctly Key: JBJCA-1149 URL: https://issues.jboss.org/browse/JBJCA-1149 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.1.3.Final, 1.0.24.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.2.0.Beta1 -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1802) OverlappingUnicastMergeTest

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1802?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1802: ------------------------------------------- Of course, the comment above concerning receivers is incorrect - you are just calling ch.getReceiver() to pick up ra, rb and rc. > OverlappingUnicastMergeTest > --------------------------- > > 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, 3.5 > > > 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. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1802) OverlappingUnicastMergeTest

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1802?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz updated JGRP-1802: -------------------------------------- Comment: was deleted (was: I also noticed that the test description you provided in the javadoc for testWithViewBC() is no longer carried out in the test. In the javadoc description, you: - send messages - inject a new view and then - send more messages whereas in the actual test, you just inject a view and then send messages). Any reason for the change? The first test seems more realistic. ) > OverlappingUnicastMergeTest > --------------------------- > > 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, 3.5 > > > 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. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3071) upgrade Generic JMS RA to 1.0.2.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-3071: --------------------------------- Summary: upgrade Generic JMS RA to 1.0.2.Final Key: WFLY-3071 URL: https://issues.jboss.org/browse/WFLY-3071 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JCA Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1805) OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1805?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1805: ------------------------------------------- https://github.com/belaban/JGroups/pull/127 > OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view > ----------------------------------------------------------------------------------------- > > Key: JGRP-1805 > URL: https://issues.jboss.org/browse/JGRP-1805 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: RHEL > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13, 3.5 > > > This test does the following: > - creates four channels a,b,c,d > - injects views A: {A,C,B}, B:{A,C,B}, C:{A,C,B} and D: {B,A,C,D} > - injects a merge event in each of channels A,B,C,D representing these four views > - checks that all channels have the final view of size 4 > The test fails intermittently on RHEL, with the same failure each time: > {noformat} > 181595 [DEBUG] GMS: - A: installing view [A|2] [A] > [testng] 181596 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|2] > [testng] 181866 [TRACE] GMS: - view [A|3] [] is empty: will not multicast it (last view) > [testng] > [testng] ------------------------------------------------------------------- > [testng] GMS: address=A, cluster=OverlappingMergeTest, physical address=10.16.94.42:27199 > [testng] ------------------------------------------------------------------- > [testng] 184954 [TRACE] GMS: - A: no initial members discovered: creating group as first member > [testng] 184954 [DEBUG] GMS: - A: installing view [A|0] [A] > [testng] 184955 [DEBUG] GMS: - created group (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl > [testng] > [testng] ------------------------------------------------------------------- > [testng] GMS: address=B, cluster=OverlappingMergeTest, physical address=10.16.94.42:27200 > [testng] ------------------------------------------------------------------- > [testng] 184961 [TRACE] GMS: - B: initial_mbrs are A > [testng] 184961 [DEBUG] GMS: - election results: {A=1} > [testng] 184961 [DEBUG] GMS: - sending JOIN(B) to A > [testng] 185013 [TRACE] GMS: - A: new members=[B], suspected=[], leaving=[], new view: [A|1] [A, B] > [testng] 185014 [TRACE] GMS: - A: mcasting view [A|1] [A, B] (2 mbrs) > [testng] > [testng] 185025 [DEBUG] GMS: - A: installing view [A|1] [A, B] > [testng] 185026 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|1] > [testng] 185055 [TRACE] GMS: - B: JOIN-RSP=[A|1] [A, B] [size=2] > [testng] > [testng] > [testng] 185055 [DEBUG] GMS: - B: installing view [A|1] [A, B] > [testng] 185057 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|1] > [testng] > [testng] ------------------------------------------------------------------- > [testng] GMS: address=C, cluster=OverlappingMergeTest, physical address=10.16.94.42:27201 > [testng] ------------------------------------------------------------------- > [testng] 185064 [TRACE] GMS: - C: initial_mbrs are B A > [testng] 185064 [DEBUG] GMS: - election results: {A=2} > [testng] 185064 [DEBUG] GMS: - sending JOIN(C) to A > [testng] 185108 [TRACE] GMS: - A: new members=[C], suspected=[], leaving=[], new view: [A|2] [A, B, C] > [testng] 185108 [TRACE] GMS: - A: mcasting view [A|2] [A, B, C] (3 mbrs) > [testng] > [testng] 185117 [DEBUG] GMS: - A: installing view [A|2] [A, B, C] > [testng] 185118 [DEBUG] GMS: - B: installing view [A|2] [A, B, C] > [testng] 185119 [TRACE] GMS: - A: received all 2 ACKs from members for view [A|2] > [testng] 185148 [TRACE] GMS: - C: JOIN-RSP=[A|2] [A, B, C] [size=3] > [testng] > [testng] > [testng] 185149 [DEBUG] GMS: - C: installing view [A|2] [A, B, C] > [testng] 185151 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|2] > [testng] > [testng] ------------------------------------------------------------------- > [testng] GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.94.42:27202 > [testng] ------------------------------------------------------------------- > [testng] 185164 [TRACE] GMS: - D: initial_mbrs are B C A > [testng] 185164 [DEBUG] GMS: - election results: {A=3} > [testng] 185164 [DEBUG] GMS: - sending JOIN(D) to A > [testng] 185203 [TRACE] GMS: - A: new members=[D], suspected=[], leaving=[], new view: [A|3] [A, B, C, D] > [testng] 185203 [TRACE] GMS: - A: mcasting view [A|3] [A, B, C, D] (4 mbrs) > [testng] > [testng] 185210 [DEBUG] GMS: - A: installing view [A|3] [A, B, C, D] > [testng] 185211 [DEBUG] GMS: - B: installing view [A|3] [A, B, C, D] > [testng] 185211 [DEBUG] GMS: - C: installing view [A|3] [A, B, C, D] > [testng] 185213 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|3] > [testng] 185242 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4] > [testng] > [testng] > [testng] 185242 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D] > [testng] 185242 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|3] > [testng] > [testng] ==== Injecting view [A|4] [A, C, B] into A, B and C ==== > [testng] 185243 [DEBUG] GMS: - A: installing view [A|4] [A, C, B] > [testng] 185243 [DEBUG] GMS: - B: installing view [A|4] [A, C, B] > [testng] 185244 [DEBUG] GMS: - C: installing view [A|4] [A, C, B] > [testng] > [testng] ==== Injecting view [B|4] [B, A, C, D] into D ==== > [testng] > [testng] 185245 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D] > [testng] A: [A|4] [A, C, B] > [testng] B: [A|4] [A, C, B] > [testng] C: [A|4] [A, C, B] > [testng] D: [B|4] [B, A, C, D] > [testng] > [testng] ==== Injecting a merge event into A, B, C and D==== > [testng] 185251 [TRACE] GMS: - A: got merge response from A, merge_id=A::3, merge data is sender=A, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (0)], A: [4 (4)] > [testng] 185253 [TRACE] GMS: - B: queue is suspended; request MERGE(4 views) is discarded > [testng] 185255 [TRACE] GMS: - C: queue is suspended; request MERGE(4 views) is discarded > [testng] 185255 [TRACE] GMS: - A: got merge response from B, merge_id=A::3, merge data is sender=B, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (1)], A: [4 (4)] > [testng] 190286 [TRACE] GMS: - A: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs) > [testng] > [testng] 190286 [TRACE] GMS: - B: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs) > [testng] > [testng] 190317 [DEBUG] GMS: - A: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] > [testng] 190318 [DEBUG] GMS: - B: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] > [testng] 190318 [DEBUG] GMS: - C: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] > [testng] 190320 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|5] > [testng] 190320 [TRACE] GMS: - B: received all 3 ACKs from members for view [A|5] > [testng] A: [A|5] [A, B, C] (coord=true) > [testng] B: [A|5] [A, B, C] (coord=false) > [testng] C: [A|5] [A, B, C] (coord=false) > [testng] D: [B|4] [B, A, C, D] (coord=false) > [testng] 195277 [DEBUG] GMS: - D: sending LEAVE request to B > [testng] FAIL: [1] org.jgroups.tests.OverlappingMergeTest.testMergeWithDifferentPartitions() > {noformat} > Whenever this test fails, I see that the queues are suspended on the initial merge attempt. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3070) The download link for Wildfly at http://www.jboss.org/projects is broken

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3070?page=com.atlassian.jira.plugin.... ] David Hladky commented on WFLY-3070: ------------------------------------ Hi, http://wildfly.org/project.properties needs to be fixed. Magnolia updates the project matrix once a day from this source. > The download link for Wildfly at http://www.jboss.org/projects is broken > ------------------------------------------------------------------------ > > Key: WFLY-3070 > URL: https://issues.jboss.org/browse/WFLY-3070 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Karel Piwko > > The link currently points to http://www.wildfly.org/download/, however should actually be http://wildfly.org/downloads/. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3070) The download link for Wildfly at http://www.jboss.org/projects is broken

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/WFLY-3070?page=com.atlassian.jira.plugin.... ] Karel Piwko moved ORG-1946 to WFLY-3070: ---------------------------------------- Project: WildFly (was: jboss.org) Key: WFLY-3070 (was: ORG-1946) Workflow: GIT Pull Request workflow (was: JBoss Community Team workflow) > The download link for Wildfly at http://www.jboss.org/projects is broken > ------------------------------------------------------------------------ > > Key: WFLY-3070 > URL: https://issues.jboss.org/browse/WFLY-3070 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Karel Piwko > Assignee: David Hladky > > The link currently points to http://www.wildfly.org/download/, however should actually be http://wildfly.org/downloads/. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3070) The download link for Wildfly at http://www.jboss.org/projects is broken

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/WFLY-3070?page=com.atlassian.jira.plugin.... ] Karel Piwko updated WFLY-3070: ------------------------------ Assignee: (was: David Hladky) > The download link for Wildfly at http://www.jboss.org/projects is broken > ------------------------------------------------------------------------ > > Key: WFLY-3070 > URL: https://issues.jboss.org/browse/WFLY-3070 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Karel Piwko > > The link currently points to http://www.wildfly.org/download/, however should actually be http://wildfly.org/downloads/. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-446) Literals may be ambiguously resolved as classes on case insensitive filesystems

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-446?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-446: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Literals may be ambiguously resolved as classes on case insensitive filesystems > ------------------------------------------------------------------------------- > > Key: DROOLS-446 > URL: https://issues.jboss.org/browse/DROOLS-446 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.1.0.CR1 > > > When a candidate class literal is analyzed, e.g. : > {code} > declare Foo > f1 : Bar = new Bar() > f2 : boolean = false > end > {code} > "Bar" is tentatively resolved (twice) and its f.q.n. is substituted as needed. > However, even "false" is tentatively resolved as well. > On a case insensitive filesytems, the presence of a class named False will cause the literal to be resolved erroneously. > The same will happen to "true" and "null" -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-446) Literals may be ambiguously resolved as classes on case insensitive filesystems

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-446?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-446. -------------------------------- Resolution: Done > Literals may be ambiguously resolved as classes on case insensitive filesystems > ------------------------------------------------------------------------------- > > Key: DROOLS-446 > URL: https://issues.jboss.org/browse/DROOLS-446 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.0.1.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.1.0.CR1 > > > When a candidate class literal is analyzed, e.g. : > {code} > declare Foo > f1 : Bar = new Bar() > f2 : boolean = false > end > {code} > "Bar" is tentatively resolved (twice) and its f.q.n. is substituted as needed. > However, even "false" is tentatively resolved as well. > On a case insensitive filesytems, the presence of a class named False will cause the literal to be resolved erroneously. > The same will happen to "true" and "null" -- 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

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014