[JBoss JIRA] Created: (JBRULES-3117) Compiling two functions fails
by Wolfgang Laun (JIRA)
Compiling two functions fails
------------------------------
Key: JBRULES-3117
URL: https://issues.jboss.org/browse/JBRULES-3117
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.1.Final
Compiling these two function together fails:
function boolean isOutOfRange( Object value, int lower ){
return true;
}
function boolean isNotContainedInt( Object object, int[] values ){
return true;
}
[ isNotContainedInt : unable to resolve type while building function ]
If the first one is removed, or its arguments are reduced, the remainder compiles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-790) Subsystem "jms": attributes not writable
by Heiko Braun (JIRA)
Subsystem "jms": attributes not writable
----------------------------------------
Key: AS7-790
URL: https://issues.jboss.org/browse/AS7-790
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "Attribute selector is not writeable"}}}
}
w/o modifications to existing queues/topics are not possible
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBRULES-3111) Regression: constraint comparing nested accessor to true fires when false
by Wolfgang Laun (JIRA)
Regression: constraint comparing nested accessor to true fires when false
---------------------------------------------------------------------------
Key: JBRULES-3111
URL: https://issues.jboss.org/browse/JBRULES-3111
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.Final
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: FUTURE
The .drl file below produces
r3:one false
r2:one false
r1:one true
but only r1 is expected to fire.
Removing all "== true" is one way of showing the correct result.
declare Bool123
bool1 : boolean
bool2 : boolean
bool3 : boolean
end
declare Thing
name : String
bool123 : Bool123
end
rule kickOff
when
then
insert( new Thing( "one", new Bool123( true, false, false ) ) );
insert( new Thing( "two", new Bool123( false, false, false ) ) );
insert( new Thing( "three", new Bool123( false, false, false ) ) );
end
rule r1
when
$t: Thing( bool123.bool1 == true )
then
System.out.println( "r1:" + $t.getName() + " " + $t.getBool123().isBool1() );
end
rule r2
when
$t: Thing( bool123.bool2 == true )
then
System.out.println( "r2:" + $t.getName() + " " + $t.getBool123().isBool2() );
end
rule r3
when
$t: Thing( bool123.bool3 == true )
then
System.out.println( "r3:" + $t.getName() + " " + $t.getBool123().isBool3() );
end
~
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (AS7-1142) Exception when starting OSGi in AS7
by David Bosschaert (JIRA)
Exception when starting OSGi in AS7
------------------------------------
Key: AS7-1142
URL: https://issues.jboss.org/browse/AS7-1142
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Priority: Minor
When starting the OSGi Framework with Start Level 2 or higher, the following exception sometimes appears. It seems harmless though...
13:17:02,289 WARN [/] (CM Configuration Updater (ManagedService Update: pid=org.apache.felix.webconsole.internal.servlet.OsgiManager)) org.ops4j.pax.web.service.spi.model.ServletModel-2: unbindHttpService: Failed unregistering Servlet: java.lang.IllegalStateException: ServletModel{id=org.ops4j.pax.web.service.spi.model.ServletModel-2,name=org.ops4j.pax.web.service.spi.model.ServletModel-2,urlPatterns=[/system/console/*],alias=/system/console,servlet=org.apache.felix.webconsole.internal.servlet.OsgiManager@13dc8ea3,initParams={},context=ContextModel{id=org.ops4j.pax.web.service.spi.model.ContextModel-1,name=,httpContext=org.apache.felix.webconsole.internal.servlet.OsgiManagerHttpContext(a)75187984,contextParams={}}} was not found
at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl.removeServlet(JettyServerImpl.java:230)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl$Started.removeServlet(ServerControllerImpl.java:271)
at org.ops4j.pax.web.service.jetty.internal.ServerControllerImpl.removeServlet(ServerControllerImpl.java:112)
at org.ops4j.pax.web.service.internal.HttpServiceStarted.unregister(HttpServiceStarted.java:205)
at org.ops4j.pax.web.service.internal.HttpServiceProxy.unregister(HttpServiceProxy.java:72)
at org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:772) [OsgiManager.class:]
at org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:660) [OsgiManager$HttpServiceTracker.class:]
at org.osgi.util.tracker.ServiceTracker$Tracked.untrack(ServiceTracker.java:1126) [ServiceTracker$Tracked.class:]
at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:347) [ServiceTracker.class:]
at org.apache.felix.webconsole.internal.servlet.OsgiManager.updateConfiguration(OsgiManager.java:826) [OsgiManager.class:]
at org.apache.felix.webconsole.internal.servlet.ConfigurationListener.updated(ConfigurationListener.java:66) [ConfigurationListener.class:]
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1160)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[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
14 years, 7 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
14 years, 7 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
14 years, 7 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
14 years, 7 months