August 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

4 days, 19 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)

4 weeks, 1 day

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] (LOGMGR-130) JDK9 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-130?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-130: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > JDK9 Support > ------------ > > Key: LOGMGR-130 > URL: https://issues.jboss.org/browse/LOGMGR-130 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > A few enhancements become possible, desirable, and/or necessary when moving to JDK 9. This is an umbrella parent issue to cover them all. > Note that some of these features may require multi-version JAR building, which Maven cannot yet do. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-113) Create a better way to handle a TCP reconnect policy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-113?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-113: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Create a better way to handle a TCP reconnect policy > ---------------------------------------------------- > > Key: LOGMGR-113 > URL: https://issues.jboss.org/browse/LOGMGR-113 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Fix For: 2.1.0.Alpha4 > > > The audit logger in WildFly uses it's own policy to reconnect a TCP connection for the {{SyslogHandler}}. The current {{org.jboss.logmanager.handlers.TcpOutputStream}} handles a reconnection on it's own unless a deprecated constructor is used. A way to set some kind of policy or enable the reconnection to be turned off should be added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-86) Create an exception filter

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-86?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-86: -------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Create an exception filter > -------------------------- > > Key: LOGMGR-86 > URL: https://issues.jboss.org/browse/LOGMGR-86 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Fix For: 2.1.0.Alpha4 > > > For now this is just a thought so that users can filter messages based on an exception in the stack trace. Currently it's not possible to use a regex filter as the stack trace is not used in when testing for matches and it probably shouldn't be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-82) PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-82?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-82: -------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy > -------------------------------------------------------------------- > > Key: LOGMGR-82 > URL: https://issues.jboss.org/browse/LOGMGR-82 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.0.Alpha4 > > > The rotation tests seem to fail at random days and times. The test {{testPeriodicAndSizeRotate}} needs to be looked at before re-enabling it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-52) Add option to WriterHandler to collapse repeated messages

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-52?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-52: -------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Add option to WriterHandler to collapse repeated messages > --------------------------------------------------------- > > Key: LOGMGR-52 > URL: https://issues.jboss.org/browse/LOGMGR-52 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 2.1.0.Alpha4 > > > The WriterHandler could have a time interval configured wherein a repeated message would be collapsed. > The last message would be stored in a field for comparison along with a nanoTime tag (the timestamp on the message is not adequate because the clock can have skew or be reset completely at any time). If the current message string equals the last message string, and collapsing is enabled, then instead of logging the message, a count is incremented. If the current message is not equal, then the stored message is logged with a tag indicating the number of repeats (i18n?) and then the next submitted message is logged. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-134) Add module name, module version fields to ExtLogRecord

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-134?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-134: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Add module name, module version fields to ExtLogRecord > ------------------------------------------------------ > > Key: LOGMGR-134 > URL: https://issues.jboss.org/browse/LOGMGR-134 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > It will be necessary for ExtLogRecord to carry additional fields for Java 9 module name and module version. The serialization impact should be analyzed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-133) Use StackWalker to get extended log record information

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-133?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-133: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Use StackWalker to get extended log record information > ------------------------------------------------------ > > Key: LOGMGR-133 > URL: https://issues.jboss.org/browse/LOGMGR-133 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > Under Java 9, you can use a StackWalker to efficiently traverse the stack and return information about callers. Using this mechanism should be substantially better-performing than snapshotting the stack to acquire the calling class information for the extended log record class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

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 August 2017