[JBoss JIRA] Created: (JBRULES-3073) Saliance is not working for 5.1.1 with fusion
by Richard Ambridge (JIRA)
Saliance is not working for 5.1.1 with fusion
---------------------------------------------
Key: JBRULES-3073
URL: https://issues.jboss.org/browse/JBRULES-3073
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.1.1.FINAL
Environment: Ubuntu
Reporter: Richard Ambridge
Assignee: Mark Proctor
Priority: Blocker
Attachments: DroolsRuleTest.java, Item.java, rule1.drl
Using drools with time based rules and saliance, the saliance is not used when firing the rules
This only happens when multiple objects update at the same time.
e.g. Rule 1 is
salience 1000
dialect "mvel"
when
$i : Item(val==10)
Item(val==11, this after [0s, 1m] $i)
Rule 2 is
salience 1000
dialect "mvel"
when
$i : Item(val==10)
not( Item(val==11, this after [0s,1m] $i))
Rule3 is
salience 100
when
$i : Item(val==11)
Then we insert 3 items with val==10
Rule2 is activated 3 times...
Then we insert an item with val==11
Note, with a val==10 and val==11 in the memory, Rule 1 will activate, and Rule 3 will activate
However, Rule1 should fire first.. as its saliance is high
For the first item it does, but then the Rule 3 fires before 2nd item does.
Audit log is attached, but summary is
Object inserted (1), Item: val==10
Activation created: Rule 2 (1)
Object inserted (2), Item: val==10
Activation created: Rule 2 (2)
Object inserted (3), Item: val==10
Activation created: Rule 2 (3)
Object inserted (4), Item: val==11
Activation created: Rule 1 (1)
Activation created: Rule 1 (2)
Activation created: Rule 1 (3)
Activation created: Rule 3 (4)
Activation cancelled: Rule 2 (1)
Activation cancelled: Rule 2 (2)
Activation cancelled: Rule 2 (3)
.. here we have 4 activations, 3 for Rule1 (saliance 1000), 1 for Rule3(saliance 100)
Activation executed Rule 1 (1)
Activation executed Rule 3 (4) //WRONG
Activation cancelled: Rule 1 (2)
Activation cancelled: Rule 1 (3)
Activation created: Rule 2 (2)
Activation created: Rule 2 (3)
Note, this works fine in Drools 5.0
In Drools 5.2.0 CR1 a null pointer is thrown (another issue will be logged for that)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBRULES-3064) dialect "mvel" flouts generic paramters
by Wolfgang Laun (JIRA)
dialect "mvel" flouts generic paramters
---------------------------------------
Key: JBRULES-3064
URL: https://issues.jboss.org/browse/JBRULES-3064
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.CR1
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.0
Given the rule
=============================================
rule x
dialect "mvel"
when
then
List<Integer> l = new ArrayList<Integer>();
end
=============================================
we get the error
=============================================
Unable to Analyse Expression List x = new ArrayList<Integer>();
[Error: Failed to compileShared: 1 compilation error(s):
- (1,23) could not resolve class: ArrayList<Integer>]
[Near : {... List x = new ArrayList<Integer>(); ....}]
^
[Line: 1, Column: 23]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JGRP-1338) MERGE2: ConcurrentModificationException
by Bela Ban (JIRA)
MERGE2: ConcurrentModificationException
---------------------------------------
Key: JGRP-1338
URL: https://issues.jboss.org/browse/JGRP-1338
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.12.2, 3.1
2011-06-23 16:54:04,826 DEBUG [org.jgroups.protocols.pbcast.GMS] (testng-.SyncDistLockingTest) exception=java.util.ConcurrentModificationException, retrying
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:810)
at java.util.HashMap$KeyIterator.next(HashMap.java:845)
at java.util.AbstractSet.removeAll(AbstractSet.java:174)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:163)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:343)
at org.jgroups.protocols.FD.down(FD.java:285)
at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:70)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:634)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:443)
at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:309)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:599)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:519)
at org.jgroups.protocols.pbcast.ClientGmsImpl.installView(ClientGmsImpl.java:246)
at org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:180)
at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:38)
at org.jgroups.protocols.pbcast.GMS.down(GMS.java:925)
at org.jgroups.protocols.FC.down(FC.java:435)
at org.jgroups.protocols.FRAG2.down(FRAG2.java:155)
at org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:324)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1081)
at org.jgroups.JChannel.downcall(JChannel.java:1680)
at org.jgroups.JChannel.connect(JChannel.java:425)
at org.jgroups.JChannel.connect(JChannel.java:388)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:158)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.start(JGroupsTransport.java:149)
at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:911)
at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:709)
at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:611)
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:176)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:171)
at org.infinispan.CacheImpl.start(CacheImpl.java:366)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:559)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:455)
at org.infinispan.test.MultipleCacheManagersTest.createClusteredCaches(MultipleCacheManagersTest.java:277)
at org.infinispan.replication.SyncReplLockingTest.createCacheManagers(SyncReplLockingTest.java:64)
at org.infinispan.test.MultipleCacheManagersTest.callCreateCacheManagers(MultipleCacheManagersTest.java:95)
at org.infinispan.test.MultipleCacheManagersTest.createBeforeMethod(MultipleCacheManagersTest.java:104)
at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:494)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121)
at org.testng.TestRunner.runWorkers(TestRunner.java:909)
at org.testng.TestRunner.privateRun(TestRunner.java:618)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBAS-9264) BoundedQueueThreadPoolService provides Executor instead of ExecutorService
by Paul Ferraro (JIRA)
BoundedQueueThreadPoolService provides Executor instead of ExecutorService
--------------------------------------------------------------------------
Key: JBAS-9264
URL: https://issues.jboss.org/browse/JBAS-9264
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Ferraro
Currently, there is no thread service that provides a j.u.c.ExecutorService using a bounded queue thread pool.
The existing BoundedQueueThreadPoolService only provides a j.u.c.Executor, instead of the far more useful j.u.c.ExecutorService. The exposed j.u.c.Executor cannot even be cast to an j.u.c.ExecutorService, since the underlying QueueExecutor is wrapped by a decorator that does not implement j.u.c.ExecutorService.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBRULES-3124) Compiler should be able to report warnings
by Mikael Lönneberg (JIRA)
Compiler should be able to report warnings
------------------------------------------
Key: JBRULES-3124
URL: https://issues.jboss.org/browse/JBRULES-3124
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.2.0.Final
Reporter: Mikael Lönneberg
Assignee: Mark Proctor
Fix For: FUTURE
1) add warnings list to packagebuilder
2) add hasWarnings and getWarnings, in mirror of errors.
3) allow hashWarnings and getWarnings to take positive/negative warnings. i.e. ignore duplicate resource (hasWarnings would return false), report duplicate file (is returned in list). This should be some sort of chainable or compositable filter, with sane defaults.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (AS7-1209) Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented
by Heiko Rupp (JIRA)
Xa-datasource:add requires a non-empty map "xa-data-source-properties", which is not documented
-----------------------------------------------------------------------------------------------
Key: AS7-1209
URL: https://issues.jboss.org/browse/AS7-1209
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.CR1
Reporter: Heiko Rupp
Assignee: Brian Stansberry
[domain@localhost:9999 subsystem=datasources] ./xa-data-source=xa-ds:read-operation-description(name=add)
does not list a (required) property "xa-data-source-properties", but when this is not provided, adding a xa-datasource fails and console shows
[Server:server-two] 15:25:52,983 WARN [org.jboss.as.controller] (pool-1-thread-35) Operation ("add") failed - address: ([
[Server:server-two] ("subsystem" => "datasources"),
[Server:server-two] ("xa-data-source" => "postgres")
[Server:server-two] ]): java.lang.IllegalArgumentException
Adding an empty xa-data-source-properties map also makes the :add fail. It only works when this property is present and some (dummy!) values are given.
1) the requirement for this xa-da.. should be documented
2) it should be optional
3) an empty map should be allowed (if no xa-props are needed)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months