[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
2 weeks, 5 days
[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10796:
-----------------------------
Description:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
was:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present.
> Warning about JSF version 'NONE' is shown in logs
> --------------------------------------------------
>
> Key: WFLY-10796
> URL: https://issues.jboss.org/browse/WFLY-10796
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
>
> Following warning is shown in log upon server start:
> {code}
> 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
> {code}
> Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
1 month, 2 weeks
[JBoss JIRA] (DROOLS-3464) Revised Unit-first Kie API
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3464:
--------------------------------------
Summary: Revised Unit-first Kie API
Key: DROOLS-3464
URL: https://issues.jboss.org/browse/DROOLS-3464
Project: Drools
Issue Type: Task
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
Short spike to sketch a new API that revolves around use of Units for Rules, Processes, etc. Implemented as a separate branch, for display purposes only (it will not be necessarily merged)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-3463) Add support for two-valued logic versions of built-in functions
by Edson Tirelli (Jira)
Edson Tirelli created DROOLS-3463:
-------------------------------------
Summary: Add support for two-valued logic versions of built-in functions
Key: DROOLS-3463
URL: https://issues.jboss.org/browse/DROOLS-3463
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Affects Versions: 7.15.0.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
FEEL considers null part of the value type domain. Also, most aggregate functions like all(), any(), sum(), etc will return null if any of the elements in the input are null.
This ticket requests the implementation of alternate aggregate functions that ignore null values in the input. The goal is to support CQL (1) semantics as well as make it easier for users that deal with sparse inputs.
(1) CQL reference: https://cql.hl7.org/09-b-cqlreference.html#aggregate-functions
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-11548) RemoteExceptions and subclasses treated as ApplicationExceptions
by Omar Hefnawi (Jira)
[ https://issues.jboss.org/browse/WFLY-11548?page=com.atlassian.jira.plugin... ]
Omar Hefnawi updated WFLY-11548:
--------------------------------
Steps to Reproduce: I honestly think the git branch gives you the best idea on how to recreate it, it's a small change, but it requires you to somewhat violate the spec by extending a RemoteException with one of your own. This bug happens in CMTTxInterceptor.java:239 in conjunction with EJBComponent.java:266 (was: I honestly think the Pull Request gives you the best idea on how to recreate it, it's a small change, but it requires you to somewhat violate the spec by extending a RemoteException with one of your own. This bug happens in CMTTxInterceptor.java:239 in conjunction with EJBComponent.java:266)
> RemoteExceptions and subclasses treated as ApplicationExceptions
> ----------------------------------------------------------------
>
> Key: WFLY-11548
> URL: https://issues.jboss.org/browse/WFLY-11548
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 13.0.0.Final
> Environment: - Windows
> - Wildfly 13 final
> - Java sdk 1.8
> Reporter: Omar Hefnawi
> Priority: Major
>
> Remote Exceptions should be treated as if they are System Exceptions
> So in very old projects where they used to extend RemoteException for their own exceptions, code was written under the assumption that when one of these is caught in the container, the transaction should be rolled back as per the spec (system exceptions cause a rollback).
> Currently if an ejb method throws a remote exception, this will be translated to be an Application Exception (on line 275 in EJBComponent.java) and transactions that are currently happening will no longer be rolled back; which was against the old spec, I'm unsure of what ejb 3.X says about this, but currently I felt it would make sense to mimic what happened in older application containers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months