[JBoss JIRA] (JBRULES-3564) Sliding window filters not applied correctly
by Edson Tirelli (JIRA)
Edson Tirelli created JBRULES-3564:
--------------------------------------
Summary: Sliding window filters not applied correctly
Key: JBRULES-3564
URL: https://issues.jboss.org/browse/JBRULES-3564
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.5.0.Beta1
REPORTED BY WOLFGANG
--------------------------------
It should be pretty obvious that the rule should not fire after the
insertion of a single fact.
{code:title=Sample.drl}declare MyEvent
@role(event)
end
rule FaultsCoincide
when
f1 : MyEvent( key == "type1" ) over window:length( 1 )
f2 : MyEvent( key == "type2" ) over window:length( 1 )
then
System.out.println( ">>> f1=" + f1 + " f2=" + f2 );
if( f2.getKey().equals( "type1" ) ) System.out.println( "*** BUG ***" );
end{code}
{code}insert MyEvent<type1,ALARM>
>>> f1=MyEvent<type1,ALARM> f2=MyEvent<type1,ALARM>
*** BUG ***
insert MyEvent<type2,ALARM>
>>> f1=MyEvent<type2,ALARM> f2=MyEvent<type2,ALARM>
>>> f1=MyEvent<type2,ALARM> f2=MyEvent<type1,ALARM>
*** BUG ***{code}
--
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
13 years, 10 months
[JBoss JIRA] (SECURITY-664) jndi lookups for a security domain should be cached
by Tom Fonteyne (JIRA)
Tom Fonteyne created SECURITY-664:
-------------------------------------
Summary: jndi lookups for a security domain should be cached
Key: SECURITY-664
URL: https://issues.jboss.org/browse/SECURITY-664
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: JBossSecurity_2.0.4.SP8
Reporter: Tom Fonteyne
Assignee: Anil Saldhana
In certain scenarios, there are many JNDI lookups being done, which are taking up to 10-20% of performance.
org/ jboss/ security/ plugins/ DefaultSecurityManagement.java
Should instead of creating new instances all the time be changed to cache per security domain.
Quote from the customer:
------------------------
The getter methods in the default security management have a factory method character. The instances change after creation (actually) no more, because security domain does not change in context. Therefore, I think it is better if the instances AuditManager, AuthenticationManager, AuthorizationManager, IdentityManager, TrustManager and MappingManager are stored in the JBossSecurityContext instance itself.
Also in the same time the jndi lookup java:/policyRegistration is performed. I have not found the code location where the lookup is performed. But this source code should also be changed.
------------------------
The customer did quite some investigation, there are more details in the case notes.
--
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
13 years, 10 months