June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 week, 3 days

2
3
0 / 0

[JBoss JIRA] (ELY-776) Eliminate reference to "slot" from module configurations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-776?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-776: ------------------------------------ Assignee: Darran Lofthouse > Eliminate reference to "slot" from module configurations > -------------------------------------------------------- > > Key: ELY-776 > URL: https://issues.jboss.org/browse/ELY-776 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta15 > > > The final version of our client XSD should accept a name for modules but no slot. Instead, either the new name-only APIs should be used or a ModuleIdentifier created via that class's "fromString" method. Module slots are deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

1 month

2
1
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

6 months

3
10
0 / 0

[JBoss JIRA] (WFCORE-3036) Upgrade JBoss Remoting to 5.0.0.CR4

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3036?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-3036: -------------------------------- Summary: Upgrade JBoss Remoting to 5.0.0.CR4 (was: Upgrade JBoss Remoting to 5.0.0.CR3) > Upgrade JBoss Remoting to 5.0.0.CR4 > ----------------------------------- > > Key: WFCORE-3036 > URL: https://issues.jboss.org/browse/WFCORE-3036 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 3.0.0.Beta28 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1644) Create/document basic requirements

by Lance Leverich (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1644?page=com.atlassian.jira.plugi... ] Lance Leverich updated DROOLS-1644: ----------------------------------- Description: This task is a placeholder to gather up the requirements for creating the ability to use PMML files as resources. Initial thoughts and feedback will be expressed in the comments below, with the end results being a documented set of objectives/goals. > Create/document basic requirements > ---------------------------------- > > Key: DROOLS-1644 > URL: https://issues.jboss.org/browse/DROOLS-1644 > Project: Drools > Issue Type: Sub-task > Reporter: Lance Leverich > Assignee: Lance Leverich > > This task is a placeholder to gather up the requirements for creating the ability to use PMML files as resources. Initial thoughts and feedback will be expressed in the comments below, with the end results being a documented set of objectives/goals. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1644) Create/document basic requirements

by Lance Leverich (JIRA)

Lance Leverich created DROOLS-1644: -------------------------------------- Summary: Create/document basic requirements Key: DROOLS-1644 URL: https://issues.jboss.org/browse/DROOLS-1644 Project: Drools Issue Type: Sub-task Reporter: Lance Leverich Assignee: Edson Tirelli -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1644) Create/document basic requirements

by Lance Leverich (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1644?page=com.atlassian.jira.plugi... ] Lance Leverich reassigned DROOLS-1644: -------------------------------------- Assignee: Lance Leverich (was: Edson Tirelli) > Create/document basic requirements > ---------------------------------- > > Key: DROOLS-1644 > URL: https://issues.jboss.org/browse/DROOLS-1644 > Project: Drools > Issue Type: Sub-task > Reporter: Lance Leverich > Assignee: Lance Leverich > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1551) Implement FEEL/DMN value marshaller

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1551?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1551: ---------------------------------- Priority: Critical (was: Major) > Implement FEEL/DMN value marshaller > ----------------------------------- > > Key: DROOLS-1551 > URL: https://issues.jboss.org/browse/DROOLS-1551 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Affects Versions: 7.0.0.CR3 > Reporter: Edson Tirelli > Assignee: Edson Tirelli > Priority: Critical > > Some value types in FEEL/DMN require special formatting when marshalling/unmarshalling. For instance: > {quote} > So it seems that ISO 8601 does not define negative intervals. I.e., ISO 8601 only supports things like "PT1H". XPath extends that with a leading optional sign, like "+PT1H" and "-PT1H". Java extends that allowing the sign to be used in each of the units in the duration like, "PT+1H", "PT-1H", besides the leading sign "-PT1H". > The FEEL spec on page 113 seems to follow the XPath lexical definition, so the leading sign "-PT1H" seems to be the correct format. > {quote} > Implement an object marshaller for DMN/FEEL that is capable of marshalling/unmarshalling objects. Most object types are straightforward, but a few of them (like durations) need special handling. In particular: > * negative duration should use a leading - sign instead of having the sign in the unit numbers > * durations need to be normalized before marshalled: > {quote} > A days and time duration in the semantic domain is a sequence of numbers for the days, hours, minutes, and seconds of duration, normalized such that the sum of these numbers is minimized. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1487) Parallel agenda cycles itself or throws NPE

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1487?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1487: -------------------------------- Sprint: 2017 Week 26-27 > Parallel agenda cycles itself or throws NPE > ------------------------------------------- > > Key: DROOLS-1487 > URL: https://issues.jboss.org/browse/DROOLS-1487 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta7 > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Labels: parallel-agenda, reported-by-qe > Fix For: 7.1.0.Final > > > Running AdvOperatorsExpertBenchmark benchmarks from our kie-benchmarks suite with parallel agenda option, the benchmark either cycles itself or throws NPE [1]. I created a "reproducer" here[2]. Be aware that this is failing nondeterministically, so with high probability it is a nasty race condition. > I tried to debug this a bit and this is the output of some variables that is available on this line [3]: > Returned fire count: 0 > Head: null > Group: AgendaGroup 'MAIN' > Group is auto deactivate: true > Limit reached: false > IsInternalFire: false > IsFiring: true > [1] http://pastebin.com/sjLjQwgX > [2] https://github.com/kiegroup/kie-benchmarks/pull/8/files > [3] https://github.com/kiegroup/drools/blob/3038a1b9287978069bcb2765dc684f696... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9037) Cluster topology updates are lossy

by David Lloyd (JIRA)

David Lloyd created WFLY-9037: --------------------------------- Summary: Cluster topology updates are lossy Key: WFLY-9037 URL: https://issues.jboss.org/browse/WFLY-9037 Project: WildFly Issue Type: Bug Components: Clustering Reporter: David Lloyd Assignee: Paul Ferraro Priority: Blocker Fix For: 11.0.0.Beta1 EJB code is not getting a complete cluster topology. In AssociationImpl, we register cluster topology listeners by adding a {{RegistryCollector.Listener<String, List<ClientMapping>>}}. Because this listener will only receive updates relative to the time it was registered, we also iterate all the values of the original {{RegistryCollector<String, List<ClientMapping>>}} by using its {{getRegistries()}} method at this time. However, this iteration always seems to come up empty, or else we're missing notifications some other way. So we end up with an incomplete cluster view and client invocations fail because of a perceived lack of node availability. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 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 June 2017