July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2140) Replace Table with RingBuffer in UNICAST3 and NAKACK2

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2140?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2140: --------------------------- Description: Table does allocate memory on resizing or compaction; whereas RingBuffer doesn't. Replacing Table with RingBuffer might bring memory allocation rates even further down. However, using RingBuffer as message store means that the capacity is fixed; when the RingBuffer is full, sender threads would have to block as messages cannot be dropped. Blocking is actually something that should be done in a flow control protocol, such as {{UFC}} or {{MFC}}, and some applications might choose completely non-blocking flow control, e.g. {{UFC_NB}} or {{MFC_NB}}, and blocking in {{UNICAST3}} or {{NAKACK2}} would move part of the blocking/non-blocking aspect away from the flow control protocols. Measure the impact on performance. Table is a critical class used by NAKACK2 and UNICAST3, and is battle tested. Do this only if the benefits trump the risk. was: Table does allocate memory on resizing or compaction; whereas RingBuffer doesn't. Replacing Table with RingBuffer might bring memory allocation rates even further down. However, using RingBuffer as message store means that the capacity is fixed; when the RingBuffer is full, messages would get dropped. This should not be a big issue as they will get retransmitted anyway, and flow control should actually kick in to throttle senders (this is done now, to prevent Table from growing out of bounds). Measure the impact on performance. Table is a critical class used by NAKACK2 and UNICAST3, and is battle tested. Do this only if the benefits trump the risk. > Replace Table with RingBuffer in UNICAST3 and NAKACK2 > ----------------------------------------------------- > > Key: JGRP-2140 > URL: https://issues.jboss.org/browse/JGRP-2140 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.x > > > Table does allocate memory on resizing or compaction; whereas RingBuffer doesn't. Replacing Table with RingBuffer might bring memory allocation rates even further down. > However, using RingBuffer as message store means that the capacity is fixed; when the RingBuffer is full, sender threads would have to block as messages cannot be dropped. Blocking is actually something that should be done in a flow control protocol, such as {{UFC}} or {{MFC}}, and some applications might choose completely non-blocking flow control, e.g. {{UFC_NB}} or {{MFC_NB}}, and blocking in {{UNICAST3}} or {{NAKACK2}} would move part of the blocking/non-blocking aspect away from the flow control protocols. > Measure the impact on performance. Table is a critical class used by NAKACK2 and UNICAST3, and is battle tested. Do this only if the benefits trump the risk. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1680) Maven plugin for unmanaged KIE Server deployments

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1680?page=com.atlassian.jira.plugi... ] Maciej Swiderski reassigned DROOLS-1680: ---------------------------------------- Assignee: Maciej Swiderski (was: Edson Tirelli) > Maven plugin for unmanaged KIE Server deployments > ------------------------------------------------- > > Key: DROOLS-1680 > URL: https://issues.jboss.org/browse/DROOLS-1680 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 7.1.0.Final > Reporter: Michael Reynolds > Assignee: Maciej Swiderski > Priority: Minor > > It would be nice to be able to manage KIE Server deployments to unmanaged KIE servers via a Maven plugin. At the moment you need to rely on bash scripts and/or ant tasks to use the REST API. > It would be very helpful for when deployments are required to be done via a CI/CD pipeline in Jenkins etc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9143) Don't override global operations unless operation transformer was actually defined

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9143?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-12399 to WFLY-9143: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9143 (was: JBEAP-12399) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 11.0.0.Alpha1 (was: 7.1.0.ER2) > Don't override global operations unless operation transformer was actually defined > ---------------------------------------------------------------------------------- > > Key: WFLY-9143 > URL: https://issues.jboss.org/browse/WFLY-9143 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > This was requested by [~ctomc]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9142) Smoke failover test for modcluster subsystem

by Matus Madzin (JIRA)

Matus Madzin created WFLY-9142: ---------------------------------- Summary: Smoke failover test for modcluster subsystem Key: WFLY-9142 URL: https://issues.jboss.org/browse/WFLY-9142 Project: WildFly Issue Type: Enhancement Components: mod_cluster, Test Suite, Web (Undertow) Affects Versions: 11.0.0.Alpha1 Reporter: Matus Madzin Assignee: Matus Madzin Priority: Critical Add smoke fail over test for modcluser subsystem and undertow which is not covered at the moment in AS TS. Basic test scenario which shows that modcluster works which should be a part of this testsuite. One balancer + two workers and check whether request is redirected to the second node when the original node stops responding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-974) Update JBoss Negotiation SCM information

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-974?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-974. --------------------------------------- Resolution: Done > Update JBoss Negotiation SCM information > ---------------------------------------- > > Key: SECURITY-974 > URL: https://issues.jboss.org/browse/SECURITY-974 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_5_CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-973) Update License Information

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-973?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-973. --------------------------------------- Resolution: Done > Update License Information > -------------------------- > > Key: SECURITY-973 > URL: https://issues.jboss.org/browse/SECURITY-973 > Project: PicketBox > Issue Type: Task > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_3_0_5_CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-974) Update JBoss Negotiation SCM information

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-974: ----------------------------------------- Summary: Update JBoss Negotiation SCM information Key: SECURITY-974 URL: https://issues.jboss.org/browse/SECURITY-974 Project: PicketBox Issue Type: Task Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_3_0_5_CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-152) Ensure we have a LICENSE.txt in the root of the project and specified in the pom

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-152?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-152. ------------------------------------- Resolution: Done > Ensure we have a LICENSE.txt in the root of the project and specified in the pom > -------------------------------------------------------------------------------- > > Key: REMJMX-152 > URL: https://issues.jboss.org/browse/REMJMX-152 > Project: Remoting JMX > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-152) Ensure we have a LICENSE.txt in the root of the project and specified in the pom

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-152: --------------------------------------- Summary: Ensure we have a LICENSE.txt in the root of the project and specified in the pom Key: REMJMX-152 URL: https://issues.jboss.org/browse/REMJMX-152 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.CR2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-151) Bring dependencies in-line with WildFly Core

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-151?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-151. ------------------------------------- Resolution: Done > Bring dependencies in-line with WildFly Core > -------------------------------------------- > > Key: REMJMX-151 > URL: https://issues.jboss.org/browse/REMJMX-151 > Project: Remoting JMX > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 July 2017