[JBoss JIRA] Created: (JBRULES-3075) window:length windows retaining events when they shouldnt
by Radai Rosenblatt (JIRA)
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and a fire a long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it should fire after the 3rd such event).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-1293) JNDI Binding service
by Quanlin Chen (JIRA)
JNDI Binding service
--------------------
Key: AS7-1293
URL: https://issues.jboss.org/browse/AS7-1293
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.0.0.Final
Reporter: Quanlin Chen
Priority: Critical
I was just been told that so far it's impossible to bind arbitrary objects into JNDI in JBOSS 7, so would you be able to create a common binding service so that it could be working the same way as using JMX in previous AS versions?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBAS-9106) In domain mode, prevent end-user access to and visibility of most configuration write operations
by Brian Stansberry (JIRA)
In domain mode, prevent end-user access to and visibility of most configuration write operations
------------------------------------------------------------------------------------------------
Key: JBAS-9106
URL: https://issues.jboss.org/browse/JBAS-9106
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta4
In domain mode most (almost certainly all) server level operations that update the persistent configuration should not be directly accessible by the end user and should not appear in the results of the read-resource-description, read-operation-names or read-operation-description operations if executed against a server-level resource. They can only be invoked by the host controller that is responsible for the server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months