March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-1147) Modify permits under lock

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1147?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1147. ------------------------------------ Resolution: Done > Modify permits under lock > ------------------------- > > Key: JBJCA-1147 > URL: https://issues.jboss.org/browse/JBJCA-1147 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.1.3.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.1.4.Final, 1.2.0.Beta1 > > > The permits needs to be locked when releasing a permit in SemaphoreArrayListManagedConnectionPool -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1801) DuplicateTest fails when testing OOB multicast to all three senders

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1801?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1801: ------------------------------------------- For an example of the failure: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JGro... > DuplicateTest fails when testing OOB multicast to all three senders > ------------------------------------------------------------------- > > Key: JGRP-1801 > URL: https://issues.jboss.org/browse/JGRP-1801 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Windows (18), Solaris (2), RHEL(1) where (x) is the number of failures seen > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > DuplicateTest does the following: > - creates three channels containing the DUPL layer called c1, c2, c3 > - DUPL is used to duplicate messages sent > - channel receiver for channel each keeps a map of messages received from each sender > - channels send messages: regular, OOB, or mixed > - the test checks that the messages received by each channel are correct in number and in order > The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: > {noformat} > Error Message > expected size=3, msgs: [C2, C1] > Stacktrace > java.lang.AssertionError > at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) > at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) > {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1801) DuplicateTest fails when testing OOB multicast to all three senders

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1801?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz updated JGRP-1801: -------------------------------------- Description: DuplicateTest does the following: - creates three channels containing the DUPL layer called c1, c2, c3 - DUPL is used to duplicate messages sent - channel receiver for channel each keeps a map of messages received from each sender - channels send messages: regular, OOB, or mixed - the test checks that the messages received by each channel are correct in number and in order The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: {noformat} Error Message expected size=3, msgs: [C2, C1] Stacktrace java.lang.AssertionError at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) {noformat} was: DuplicateTest does the following: - creates three channels containing the DUPL layer called c1, c2, c3 (DUPL is used to duplicate messages sent) - channel receiver for each keeps a map of messages received from each sender - channels send messages: regular, OOB, or mixed - the test checks that the messages received by each channel are correct in number and in order The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: {noformat} Error Message expected size=3, msgs: [C2, C1] Stacktrace java.lang.AssertionError at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) {noformat} > DuplicateTest fails when testing OOB multicast to all three senders > ------------------------------------------------------------------- > > Key: JGRP-1801 > URL: https://issues.jboss.org/browse/JGRP-1801 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.13 > Environment: Windows (18), Solaris (2), RHEL(1) where (x) is the number of failures seen > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.2.13 > > > DuplicateTest does the following: > - creates three channels containing the DUPL layer called c1, c2, c3 > - DUPL is used to duplicate messages sent > - channel receiver for channel each keeps a map of messages received from each sender > - channels send messages: regular, OOB, or mixed > - the test checks that the messages received by each channel are correct in number and in order > The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: > {noformat} > Error Message > expected size=3, msgs: [C2, C1] > Stacktrace > java.lang.AssertionError > at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) > at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) > {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1801) DuplicateTest fails when testing OOB multicast to all three senders

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created JGRP-1801: ----------------------------------------- Summary: DuplicateTest fails when testing OOB multicast to all three senders Key: JGRP-1801 URL: https://issues.jboss.org/browse/JGRP-1801 Project: JGroups Issue Type: Bug Affects Versions: 3.2.13 Environment: Windows (18), Solaris (2), RHEL(1) where (x) is the number of failures seen Reporter: Richard Achmatowicz Assignee: Bela Ban Fix For: 3.2.13 DuplicateTest does the following: - creates three channels containing the DUPL layer called c1, c2, c3 (DUPL is used to duplicate messages sent) - channel receiver for each keeps a map of messages received from each sender - channels send messages: regular, OOB, or mixed - the test checks that the messages received by each channel are correct in number and in order The test testOOBMuloticastToAll3Senders is failing regularly on multple platforms. The test makes each of the channels send OOB multicast messages to the group, but only two of three members ever end up receiving the multicast messages. Al example of the failure: {noformat} Error Message expected size=3, msgs: [C2, C1] Stacktrace java.lang.AssertionError at org.jgroups.tests.DuplicateTest.check(DuplicateTest.java:217) at org.jgroups.tests.DuplicateTest.testOOBMulticastToAll3Senders(DuplicateTest.java:123) {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1147) Modify permits under lock

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1147: -------------------------------------- Summary: Modify permits under lock Key: JBJCA-1147 URL: https://issues.jboss.org/browse/JBJCA-1147 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.1.3.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.1.4.Final, 1.2.0.Beta1 The permits needs to be locked when releasing a permit in SemaphoreArrayListManagedConnectionPool -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1141) Allow 'connectable' to be configured per deployment

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1141?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1141. ------------------------------------ Resolution: Done > Allow 'connectable' to be configured per deployment > --------------------------------------------------- > > Key: JBJCA-1141 > URL: https://issues.jboss.org/browse/JBJCA-1141 > Project: IronJacamar > Issue Type: Task > Components: Common, Core, Deployer > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.24.Final, 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1146) Optimize removal in TransactionSynchronizer

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1146?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1146. ------------------------------------ Resolution: Done > Optimize removal in TransactionSynchronizer > ------------------------------------------- > > Key: JBJCA-1146 > URL: https://issues.jboss.org/browse/JBJCA-1146 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.24.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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2519) Useless mod_cluster drained context logging (...UndertowContext@3abb2fbc)

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2519?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-2519. -------------------------------- > Useless mod_cluster drained context logging (...UndertowContext@3abb2fbc) > ------------------------------------------------------------------------- > > Key: WFLY-2519 > URL: https://issues.jboss.org/browse/WFLY-2519 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 8.0.0.CR1 > > > {noformat}18:21:17,409 INFO [org.jboss.modcluster] (MSC service thread 1-8) MODCLUSTER000021: All pending requests drained from default-host:org.wildfly.mod_cluster.undertow.UndertowContext@3abb2fbc in 0.0 seconds > {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2171) Use deployment unit processors to register mod_cluster metrics

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2171?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-2171. -------------------------------- > Use deployment unit processors to register mod_cluster metrics > -------------------------------------------------------------- > > Key: WFLY-2171 > URL: https://issues.jboss.org/browse/WFLY-2171 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 8.0.0.Final > > > Remove static dependency and make it runtime using DUPs. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1146) Optimize removal in TransactionSynchronizer

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1146: -------------------------------------- Summary: Optimize removal in TransactionSynchronizer Key: JBJCA-1146 URL: https://issues.jboss.org/browse/JBJCA-1146 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.24.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

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014