October 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 day, 11 hours

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)

3 weeks, 5 days

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

5 months, 3 weeks

3
10
0 / 0

[JBoss JIRA] (DROOLS-2089) Prepare drools-wb-globals-editor module for static code analysis

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2089: ----------------------------------- Summary: Prepare drools-wb-globals-editor module for static code analysis Key: DROOLS-2089 URL: https://issues.jboss.org/browse/DROOLS-2089 Project: Drools Issue Type: Sub-task Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2088) Prepare drools-wb-factmodel-editor module for static code analysis

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2088: ----------------------------------- Summary: Prepare drools-wb-factmodel-editor module for static code analysis Key: DROOLS-2088 URL: https://issues.jboss.org/browse/DROOLS-2088 Project: Drools Issue Type: Sub-task Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2087) Prepare drools-wb-enum-editor module for static code analysis

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2087: ----------------------------------- Summary: Prepare drools-wb-enum-editor module for static code analysis Key: DROOLS-2087 URL: https://issues.jboss.org/browse/DROOLS-2087 Project: Drools Issue Type: Sub-task Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2086) Prepare drools-wb-dtable-xls-editor module for static code analysis

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2086?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2086: -------------------------------- Summary: Prepare drools-wb-dtable-xls-editor module for static code analysis (was: Prepare drools-wb-xls-editor module for static code analysis) > Prepare drools-wb-dtable-xls-editor module for static code analysis > ------------------------------------------------------------------- > > Key: DROOLS-2086 > URL: https://issues.jboss.org/browse/DROOLS-2086 > Project: Drools > Issue Type: Sub-task > Reporter: Jozef Marko > Assignee: Jozef Marko > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2086) Prepare drools-wb-xls-editor module for static code analysis

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2086: ----------------------------------- Summary: Prepare drools-wb-xls-editor module for static code analysis Key: DROOLS-2086 URL: https://issues.jboss.org/browse/DROOLS-2086 Project: Drools Issue Type: Sub-task Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9356) Pointless duplicate execution of DomainHostExcludeXXXTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9356?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9356: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10608 (was: https://github.com/wildfly/wildfly/pull/10524) > Pointless duplicate execution of DomainHostExcludeXXXTestCase > ------------------------------------------------------------- > > Key: WFLY-9356 > URL: https://issues.jboss.org/browse/WFLY-9356 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 12.0.0.Alpha1 > > > The various versions of DomainHostExcludeXXXTestCase each get executed twice because I added them to two different @Suite classes. The execution is identical in each suite so this is pointless. Adds about a minute to a CI run on Linux. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5351) querying TimerService information from CLI fails for canceled timer

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5351?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5351: -------------------------------------- Fix Version/s: 12.0.0.Alpha1 Assignee: Matthieu Brouillard Resolution: Done > querying TimerService information from CLI fails for canceled timer > ------------------------------------------------------------------- > > Key: WFLY-5351 > URL: https://issues.jboss.org/browse/WFLY-5351 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.1.Final, 10.0.0.CR2, 10.0.0.CR4, 10.0.0.CR5 > Environment: probably not relevant but here is my environment > {{Java Version : 1.8.0_60 > Java Vendor : Oracle Corporation > OS Hostname : PAMWX125 > OS Architecture : amd64 > OS Name : Windows 7 > }} > Reporter: Matthieu Brouillard > Assignee: Matthieu Brouillard > Fix For: 12.0.0.Alpha1 > > Attachments: WFLY-5351diff, patch1.diff, timer-cli-failure.zip > > > When (at least) a persistent calendar timer is created then cancelled, querying TimerService information via CLI (script or library) fails when retrieving also runtime information. > We discovered the issue because our arquillian tests are failing due to some code in arquillian that fires the equivalent of the provided CLI command below when remotes tests are executed. > Attached is a proposed patch and a demo project to reproduce in a simple way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 October 2017