[JBoss JIRA] (DROOLS-1516) GAV names are not coming properly when running the tomcat SSL
by Arunraj SRM (JIRA)
Arunraj SRM created DROOLS-1516:
-----------------------------------
Summary: GAV names are not coming properly when running the tomcat SSL
Key: DROOLS-1516
URL: https://issues.jboss.org/browse/DROOLS-1516
Project: Drools
Issue Type: Feature Request
Components: kie server
Affects Versions: 6.5.0.Final
Environment: Windows
Reporter: Arunraj SRM
Assignee: Edson Tirelli
Priority: Blocker
Attachments: gav_issue.png
Deploy Drools Work Bench and KIE Server in Tomcat Server configured with SSL and started via service. All the artifacts populated under the GAV are displaying as
<undetermined>:<undetermined>:<undetermined>
instead of actual path including the guvnor
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1169) Running drools with OpenJDK9 (10 May 2016) gives "type java.lang.Object cannot be resolved" and "java.io.Serializable cannot be resolved" due to ECJ 2.5
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1169?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1169:
------------------------------------------
ECJ 4.6.1 is out, we should try it out to see if it fixes this issue.
> Running drools with OpenJDK9 (10 May 2016) gives "type java.lang.Object cannot be resolved" and "java.io.Serializable cannot be resolved" due to ECJ 2.5
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1169
> URL: https://issues.jboss.org/browse/DROOLS-1169
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Labels: java9
>
> The code below runs perfectly with OpenJDK 8 (and even 6 and 7).
> To reproduce, use JDK 9 ( https://jdk9.java.net/download/ ) and in optaplanner-core, run XStreamXmlSolverFactoryTest [1] (or mostly any other test that builds a DRL file) to get this error:
> {code}
> 15:56:40.229 [main] ERROR o.d.c.k.b.impl.AbstractKieModule - Unable to build KieBaseModel:defaultKieBase
> Rule Compilation error : [Rule name='Conflict']
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (1:0) : The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (1:0) : The type java.io.Serializable cannot be resolved. It is indirectly referenced from required .class files
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (3:337) : Implicit super constructor Object() is undefined for default constructor. Must define an explicit constructor
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (6:569) : java.lang.Exception cannot be resolved to a type
> java.lang.IllegalStateException: There are errors in a score DRL:
> Error Messages:
> Message [id=1, level=ERROR, path=org/optaplanner/core/api/solver/testdataScoreRules.drl, line=31, column=0
> text=Rule Compilation error The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> The type java.io.Serializable cannot be resolved. It is indirectly referenced from required .class files
> Implicit super constructor Object() is undefined for default constructor. Must define an explicit constructor
> java.lang.Exception cannot be resolved to a type]
> {code}
> That tests builds this DRL:
> {code}
> package org.optaplanner.core.api.solver;
> dialect "java"
> import org.optaplanner.core.api.score.buildin.simple.SimpleScoreHolder;
> import org.optaplanner.core.impl.testdata.domain.TestdataValue;
> import org.optaplanner.core.impl.testdata.domain.TestdataEntity;
> global SimpleScoreHolder scoreHolder;
> // ############################################################################
> // Constraints
> // ############################################################################
> rule "Conflict"
> when
> TestdataEntity(value != null, $leftValue : value)
> TestdataEntity(value == $leftValue)
> then
> scoreHolder.addConstraintMatch(kcontext, -1);
> end
> {code}
> Not sure where the Object constructor reference comes from... This might be a JDK 9 upstream issue.
> Note: don't build drools with OpenJDK9 as that will fail sooner :)
> [1] https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-core/sr...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-1169) Running drools with OpenJDK9 (10 May 2016) gives "type java.lang.Object cannot be resolved" and "java.io.Serializable cannot be resolved" due to ECJ 2.5
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1169?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1169:
-------------------------------------
Comment: was deleted
(was: ECJ 4.6.1 is out, we should try it out to see if it fixes this issue.)
> Running drools with OpenJDK9 (10 May 2016) gives "type java.lang.Object cannot be resolved" and "java.io.Serializable cannot be resolved" due to ECJ 2.5
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1169
> URL: https://issues.jboss.org/browse/DROOLS-1169
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Labels: java9
>
> The code below runs perfectly with OpenJDK 8 (and even 6 and 7).
> To reproduce, use JDK 9 ( https://jdk9.java.net/download/ ) and in optaplanner-core, run XStreamXmlSolverFactoryTest [1] (or mostly any other test that builds a DRL file) to get this error:
> {code}
> 15:56:40.229 [main] ERROR o.d.c.k.b.impl.AbstractKieModule - Unable to build KieBaseModel:defaultKieBase
> Rule Compilation error : [Rule name='Conflict']
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (1:0) : The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (1:0) : The type java.io.Serializable cannot be resolved. It is indirectly referenced from required .class files
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (3:337) : Implicit super constructor Object() is undefined for default constructor. Must define an explicit constructor
> org/optaplanner/core/api/solver/Rule_Conflict903142795.java (6:569) : java.lang.Exception cannot be resolved to a type
> java.lang.IllegalStateException: There are errors in a score DRL:
> Error Messages:
> Message [id=1, level=ERROR, path=org/optaplanner/core/api/solver/testdataScoreRules.drl, line=31, column=0
> text=Rule Compilation error The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files
> The type java.io.Serializable cannot be resolved. It is indirectly referenced from required .class files
> Implicit super constructor Object() is undefined for default constructor. Must define an explicit constructor
> java.lang.Exception cannot be resolved to a type]
> {code}
> That tests builds this DRL:
> {code}
> package org.optaplanner.core.api.solver;
> dialect "java"
> import org.optaplanner.core.api.score.buildin.simple.SimpleScoreHolder;
> import org.optaplanner.core.impl.testdata.domain.TestdataValue;
> import org.optaplanner.core.impl.testdata.domain.TestdataEntity;
> global SimpleScoreHolder scoreHolder;
> // ############################################################################
> // Constraints
> // ############################################################################
> rule "Conflict"
> when
> TestdataEntity(value != null, $leftValue : value)
> TestdataEntity(value == $leftValue)
> then
> scoreHolder.addConstraintMatch(kcontext, -1);
> end
> {code}
> Not sure where the Object constructor reference comes from... This might be a JDK 9 upstream issue.
> Note: don't build drools with OpenJDK9 as that will fail sooner :)
> [1] https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-core/sr...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-8525) Add capabilities to mail subsystem
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8525?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar moved JBEAP-10184 to WFLY-8525:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8525 (was: JBEAP-10184)
Issue Type: Task (was: Bug)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Mail
(was: Mail)
Affects Version/s: (was: 7.1.0.DR8)
> Add capabilities to mail subsystem
> ----------------------------------
>
> Key: WFLY-8525
> URL: https://issues.jboss.org/browse/WFLY-8525
> Project: WildFly
> Issue Type: Task
> Components: Mail
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Priority: Minor
>
> When I try to create imap server in mail subsystem, I can provide nonexistent reference to {{outbound-socket-binding-ref}}:
> {code}
> [standalone@localhost:9990 /] /subsystem=mail/mail-session=default/server=imap:add(outbound-socket-binding-ref=nonexistent)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> {code}
> operation is successful and requires reload of server configuration. During configuration reload server complains that 'nonexistent' binding does not exist:
> {code}
> 12:30:42,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "mail"),
> ("mail-session" => "default")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.outbound-socket-binding.nonexistent"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.mail-session.default is missing [jboss.outbound-socket-binding.nonexistent]"]
> }
> {code}
> When I try similar action e.g. in Undertow subsystem, I get error rightaway during the add operation:
> {code}
> [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=moje:add(socket-binding=nonexistent)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0369: Required capabilities are not available:
> org.wildfly.network.socket-binding.nonexistent; There are no known registration points which can provide this capability.",
> "rolled-back" => true
> }
> {code}
> I like Undertow's approach much more as user is directly warned that particular reference is not available. It would be nice if the same approach could be used also in mail subsystem. This applies on all three mail server types {{imap}}, {{pop3}} and {{smtp}} during both {{add}} operation and also {{write-attribute}} operation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-784) Missing dependency - Uberfire workbench
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-784?page=com.atlassian.jira.plugin... ]
Tibor Zimányi commented on DROOLS-784:
--------------------------------------
Is this still relevant? If not, we should probably close this.
> Missing dependency - Uberfire workbench
> ---------------------------------------
>
> Key: DROOLS-784
> URL: https://issues.jboss.org/browse/DROOLS-784
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.Final
> Reporter: Matt Sinton-Hewitt
> Assignee: Michael Anstis
> Priority: Blocker
>
> On downloading Drools Workbench from http://www.drools.org/download/download.html
> It appears to be missing:
> <groupId>org.uberfire</groupId>
> <artifactId>uberfire-workbench</artifactId>
> various imports complain as being missing, e.g.
> import org.uberfire.client.mvp.AbstractWorkbenchPerspectiveActivity;
> import org.uberfire.client.mvp.PlaceManager;
> The service still starts but I get errors all the time:
> SEVERE: Editor model couldn't be loaded from path: default://master@testRepo/TestProject/src/main/java/com/flybe/testproject/TestObj.java.
> org.kie.workbench.common.screens.datamodeller.service.ServiceException: Data model couldn't be loaded, path: PathImpl{uri='default://master@testRepo/TestProject', fileName='TestProject', attrs={}}, projectPath: PathImpl{uri='default://master@testRepo/TestProject', fileName='TestProject', attrs={}}.
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.loadModel(DataModelerServiceImpl.java:342)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.constructContent(DataModelerServiceImpl.java:251)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.constructContent(DataModelerServiceImpl.java:121)
> at org.kie.workbench.common.services.backend.service.KieService.loadContent(KieService.java:73)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.loadContent(DataModelerServiceImpl.java:191)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl$Proxy$_$$_WeldClientProxy.loadContent(DataModelerServiceImpl$Proxy$_$$_WeldClientProxy.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.errai.bus.server.io.AbstractRPCMethodCallback.invokeMethodFromMessage(AbstractRPCMethodCallback.java:48)
> at org.jboss.errai.bus.server.io.ValueReplyRPCEndpointCallback.callback(ValueReplyRPCEndpointCallback.java:22)
> at org.jboss.errai.bus.server.io.RemoteServiceCallback.callback(RemoteServiceCallback.java:54)
> at org.jboss.errai.cdi.server.CDIExtensionPoints$2.callback(CDIExtensionPoints.java:396)
> at org.jboss.errai.bus.server.DeliveryPlan.deliver(DeliveryPlan.java:47)
> at org.jboss.errai.bus.server.ServerMessageBusImpl.sendGlobal(ServerMessageBusImpl.java:293)
> at org.jboss.errai.bus.server.SimpleDispatcher.dispatchGlobal(SimpleDispatcher.java:46)
> at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:97)
> at org.jboss.errai.bus.server.service.ErraiServiceImpl.store(ErraiServiceImpl.java:114)
> at org.jboss.errai.bus.server.servlet.DefaultBlockingServlet.doPost(DefaultBlockingServlet.java:142)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.uberfire.ext.security.server.SecureHeadersFilter.doFilter(SecureHeadersFilter.java:53)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.uberfire.ext.security.server.SecurityIntegrationFilter.doFilter(SecurityIntegrationFilter.java:64)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
> at org.kie.integration.tomcat.JACCValve.invoke(JACCValve.java:101)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423)
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079)
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620)
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.RuntimeException: com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.kie.workbench.drools.client.perspectives.M2RepoPerspective annotated with interface org.eclipse.sisu.inject.TypeArguments$Implicit was bound.
> at org.eclipse.sisu.wire.LocatorWiring
> 2) No implementation for org.kie.workbench.drools.client.perspectives.DroolsAuthoringNoContextNavigationPerspective annotated with interface org.eclipse.sisu.inject.TypeArguments$Implicit was bound.
> at org.eclipse.sisu.wire.LocatorWiring
> 3) No implementation for org.kie.workbench.drools.client.perspectives.AdministrationPerspective annotated with interface org.eclipse.sisu.inject.TypeArguments$Implicit was bound.
> at org.eclipse.sisu.wire.LocatorWiring
> 4) No implementation for org.kie.workbench.drools.client.perspectives.DroolsAuthoringPerspective annotated with interface org.eclipse.sisu.inject.TypeArguments$Implicit was bound.
> at org.eclipse.sisu.wire.LocatorWiring
> 4 errors
> at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:44)
> at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:35)
> at org.kie.scanner.ArtifactResolver.getResolverFor(ArtifactResolver.java:100)
> at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:68)
> at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:30)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.getProjectClassLoader(DataModelerServiceImpl.java:1214)
> at org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl.loadModel(DataModelerServiceImpl.java:315)
> ... 48 more
> Caused by: com.google.inject.CreationException: Guice creation errors:
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-682) Build and deploy option required in Standalone mode editors
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-682?page=com.atlassian.jira.plugin... ]
Tibor Zimányi commented on DROOLS-682:
--------------------------------------
Is this still relevant? If not, we should probably close this.
> Build and deploy option required in Standalone mode editors
> -----------------------------------------------------------
>
> Key: DROOLS-682
> URL: https://issues.jboss.org/browse/DROOLS-682
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Environment: JDK 1.8 / Wildfly 8.1 / Drools Work bench 6.1 Final
> Reporter: Ramesh C
> Assignee: Michael Anstis
> Priority: Blocker
>
> Integration of an asset editor to edit in external application is works well
> for an asset. if user edits and saves the asset it only saves the editor.
> As of now It does not builds the project and deploys the code into local repository and work bench repository. So,it is not possible to use the work bench in standalone mode effectively in production.
> kindly provide build and deploy button in standalone mode asset editors.
> So, Admins can edit, build and deploy the changes to repository and in the application, it will be read dynamically using ReleaseId mechanism or Scan mechanism. In this way, it will help for rules editing and building
> without restarting the application servers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-496) Rules in Drools 6.x cannot use more than 64 patterns
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-496?page=com.atlassian.jira.plugin... ]
Tibor Zimányi commented on DROOLS-496:
--------------------------------------
Is this still relevant? If not, we should probably close this.
> Rules in Drools 6.x cannot use more than 64 patterns
> ----------------------------------------------------
>
> Key: DROOLS-496
> URL: https://issues.jboss.org/browse/DROOLS-496
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.Beta1
> Reporter: Jörgen Risholt
> Assignee: Mark Proctor
> Priority: Blocker
> Attachments: drools-test_5.6.0.tar, drools-test_6.0.1.tar
>
>
> When trying a script as shown below we can not get it to work with 6.0.1 but with 5.6.0. There seems to be some relation to the number of facts, the more facts the higher probablity that the 6.0.1 version do not trigger. We have made two simple singelthreaded scenarios that I can upload if wanted.
> The examle has a lot of facts, but we notice that from about 50 it seems that the problam may occur.
> rule "TestRule"
> Person(name == "Name0")
> Person(name == "Name1")
> ....
> Person(name == "Name1000")
> then
> System.out.println("Successfully trigged");
> end
> This is the testcode for 5.6.0.Final (work always):
> package drools_test;
> import org.drools.KnowledgeBase;
> import org.drools.builder.KnowledgeBuilder;
> import org.drools.builder.KnowledgeBuilderFactory;
> import org.drools.builder.ResourceType;
> import org.drools.io.ResourceFactory;
> import org.drools.runtime.StatefulKnowledgeSession;
> import drools_test.data.Person;
> public class App {
> private final static int NUMBER_OF_PERSONS = 3000;
> public static void main(String[] args) {
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newClassPathResource("rules.drl",
> App.class), ResourceType.DRL);
> KnowledgeBase kb = kbuilder.newKnowledgeBase();
> StatefulKnowledgeSession session = null;
> try {
> session = kb.newStatefulKnowledgeSession();
> for (int i = 0; i < NUMBER_OF_PERSONS; ++i) {
> session.insert(new Person(String.format("Name%s", i)));
> session.fireAllRules();
> }
> session.fireAllRules();
> } finally {
> if (session != null) {
> session.dispose();
> }
> }
> }
> }
> And this is the same code for 6.0.1.Final which always fails:
> package drools_test;
> import org.kie.api.KieServices;
> import org.kie.api.runtime.KieContainer;
> import org.kie.api.runtime.KieSession;
> import drools_test.data.Person;
> public class App
> {
> private final static int NUMBER_OF_PERSONS = 3000;
> public static void main(String[] args)
> {
> KieServices kieServices = KieServices.Factory.get();
> KieContainer kContainer = kieServices.getKieClasspathContainer();
> KieSession session = null;
> try {
> session = kContainer.newKieSession();
> for (int i = 0; i < NUMBER_OF_PERSONS; ++i) {
> session.insert(new Person(String.format("Name%s", i)));
> session.fireAllRules(); // Comment out this line and the rule will fire.
> }
> session.fireAllRules();
> } finally {
> if (session != null) {
> session.dispose();
> }
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (DROOLS-263) Possible memory leak insliding temporal windows
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-263?page=com.atlassian.jira.plugin... ]
Tibor Zimányi commented on DROOLS-263:
--------------------------------------
Is this still relevant? If not, we should probably close this.
> Possible memory leak insliding temporal windows
> ------------------------------------------------
>
> Key: DROOLS-263
> URL: https://issues.jboss.org/browse/DROOLS-263
> Project: Drools
> Issue Type: Bug
> Affects Versions: 5.5.0.Final
> Reporter: Davide Sottara
> Assignee: Mark Proctor
> Priority: Blocker
>
> When an event is asserted and a temporal window is present, it will be cached in the window's memory and then propagated (usually to an accumulate) by a propagationQuquingNode.
> If the even expires before it participates in a tuple (in a multi-threading environment), the WM retraction will not reach the window node due to the lack of tuples. BUT, it will set the fact handle's ID to -1
> When the fact is considered for expiration from the sliding window, its changed ID will 1) disrupt the local event queue and 2) prevent it from being removed from the node memory.
> Memory leaks and NPEs will arise randomly
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months