[JBoss JIRA] (JBRULES-3573) Concurrency related exceptions when using entry-points and sliding windows
by Edson Tirelli (JIRA)
Edson Tirelli created JBRULES-3573:
--------------------------------------
Summary: Concurrency related exceptions when using entry-points and sliding windows
Key: JBRULES-3573
URL: https://issues.jboss.org/browse/JBRULES-3573
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Affects Versions: 5.4.0.Final
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 5.4.1.Final, 5.5.0.Beta1
There are several concurrency related exceptions being raised when using multiple threads, entry-points and sliding windows in 5.4.x+.
E.g.:
org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.reteoo.PropagationQueuingNode$PropagateAction@4de8b671
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:979)
at org.drools.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1423)
at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:755)
at org.drools.common.AbstractWorkingMemory.fireUntilHalt(AbstractWorkingMemory.java:731)
at org.drools.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:247)
at org.drools.integrationtests.MultithreadTest$4.call(MultithreadTest.java:169)
at org.drools.integrationtests.MultithreadTest$4.call(MultithreadTest.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.NoSuchElementException
at java.util.LinkedList.remove(LinkedList.java:805)
at java.util.LinkedList.removeFirst(LinkedList.java:151)
at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:344)
at org.drools.reteoo.PropagationQueuingNode$AssertAction.execute(PropagationQueuingNode.java:404)
at org.drools.reteoo.PropagationQueuingNode.propagateActions(PropagationQueuingNode.java:280)
at org.drools.reteoo.PropagationQueuingNode$PropagateAction.execute(PropagationQueuingNode.java:563)
at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:977)
... 14 more
--
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, 9 months
[JBoss JIRA] (AS7-3536) Review the inter-module dependencies directly relating to domain security
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-3536:
-------------------------------------
Summary: Review the inter-module dependencies directly relating to domain security
Key: AS7-3536
URL: https://issues.jboss.org/browse/AS7-3536
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
The domain-management module containing a lot of the Remoting/SASL security services was added after a lot of the other inter-module dependencies had been established, now before the next major phase of development need to review the resulting dependencies and clean up.
Most notably the API/SPI aspect of the security classes should be better separated from the domain operations acting on them - there are numerous places where access to the API is required or other services need to implement an SPI interface but the close coupling of management operations causes cyclic dependency issues.
--
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, 9 months
[JBoss JIRA] (AS7-5153) Add sun.awt to sun.jdk module
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-5153?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated AS7-5153:
-----------------------------
Summary: Add sun.awt to sun.jdk module (was: Add sun.awt. to list of systemPackages)
> Add sun.awt to sun.jdk module
> -----------------------------
>
> Key: AS7-5153
> URL: https://issues.jboss.org/browse/AS7-5153
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Class Loading
> Environment: When using Oracle jre
> Reporter: Michael Procopio
> Assignee: David Lloyd
>
> We have code which extends sun.awt.DisplayChangedListener, and yes we know that it is documented by Oracle as a internal only interface; however, our developers maintain they have no other way to make their code run properly. Since sun.awt is not considered a system package our users run into problems when using Jboss 7.1. And yes we realize that the user can code Djboss.modules.system.pkgs in her conf file; however, that's one more thing to keep track of. And sun.awt really is a system package when using the Oracle JRE.
>
--
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, 9 months
[JBoss JIRA] (AS7-5153) Add sun.awt. to list of systemPackages
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-5153?page=com.atlassian.jira.plugin.s... ]
David Lloyd moved MODULES-139 to AS7-5153:
------------------------------------------
Project: Application Server 7 (was: JBoss Modules)
Key: AS7-5153 (was: MODULES-139)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: 1.1.1.GA)
Component/s: Class Loading
(was: core)
> Add sun.awt. to list of systemPackages
> --------------------------------------
>
> Key: AS7-5153
> URL: https://issues.jboss.org/browse/AS7-5153
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Class Loading
> Environment: When using Oracle jre
> Reporter: Michael Procopio
> Assignee: David Lloyd
>
> We have code which extends sun.awt.DisplayChangedListener, and yes we know that it is documented by Oracle as a internal only interface; however, our developers maintain they have no other way to make their code run properly. Since sun.awt is not considered a system package our users run into problems when using Jboss 7.1. And yes we realize that the user can code Djboss.modules.system.pkgs in her conf file; however, that's one more thing to keep track of. And sun.awt really is a system package when using the Oracle JRE.
>
--
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, 9 months