[JBoss JIRA] (DROOLS-2409) Memory Leak in sliding window
by Srinivas ev (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2409?page=com.atlassian.jira.plugi... ]
Srinivas ev edited comment on DROOLS-2409 at 9/18/18 9:36 AM:
--------------------------------------------------------------
Hi Mario,
For your comment -
>> The problem there is that inserting events in a so tight loop has the effect of overwhelming the engine not giving it a chance of getting any job done.
I have a similar case where in my application, the load may go up to 100 events per second and there will be a possibility of getting the same load for long hours. As per your statement regarding overwhelming the engine, the engine may fail to execute the rules for incoming events or eviction.
What solutions I can assume for this problem. When I did the experiment last time for my project, I observed drools engine at some stage(when the number of events in drools stateful session crossed ~20 lakh) consuming all the events into it without performing any operation regarding rule evaluations/persistence timers execution( for example).
I can share the reproducer in case needed. Thanks,
was (Author: ev.srinivas):
Hi Mario,
For your comment -
>> The problem there is that inserting events in a so tight loop has the effect of overwhelming the engine not giving it a chance of getting any job done.
I have a similar case where in my application, the load may go up to 100 events per second and there will be a possibility of getting the same load for long hours. As per your statement regarding overwhelming the engine, the engine may fail to execute the rules for incoming events or eviction.
What solutions I can assume for this problem. When I did the experiment last time for my project, I observed drools engine consuming all the events into it without performing any operation regarding rule evaluations/persistence timers execution( for example).
I can share the reproducer in case needed. Thanks,
> Memory Leak in sliding window
> -----------------------------
>
> Key: DROOLS-2409
> URL: https://issues.jboss.org/browse/DROOLS-2409
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.6.0.Final
> Environment: Mac with Java 1.8 using Spring Boot (see attached demo project)
> Reporter: Mike Baranski
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: complete.tar.gz
>
>
> See attached project.
> `gradle test` causes an out of memory exception on my machine after ~2.6 million events. Events should be released for GC after 1 second, but that does not appear to be happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11035) ejb-remote quickstart fat client jar is not multi-release
by Michal Jurc (JIRA)
Michal Jurc created WFLY-11035:
----------------------------------
Summary: ejb-remote quickstart fat client jar is not multi-release
Key: WFLY-11035
URL: https://issues.jboss.org/browse/WFLY-11035
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Affects Versions: 14.0.0.Final
Reporter: Michal Jurc
Assignee: Eduardo Martins
Priority: Critical
The quickstart client application's instructions in section {{Build and Run The Quickstart as an Executable JAR}} currently don't seem to work on JDK11 as running the executable jar results in CNFE:
{code:title=[mjurc@tigris client]$ java -jar target/ejb-remote-client-jar-with-dependencies.jar
}Sep 17, 2018 12:02:01 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.9.Final
Sep 17, 2018 12:02:01 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.6.0.Final
Sep 17, 2018 12:02:01 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Sep 17, 2018 12:02:01 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Sep 17, 2018 12:02:01 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.2.Final
Sep 17, 2018 12:02:02 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.8.Final
Sep 17, 2018 12:02:02 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 4.0.11.Final
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/marshalling/JDKSpecific$1
at org.jboss.marshalling.JDKSpecific.<clinit>(JDKSpecific.java:35)
at org.jboss.marshalling.FieldSetter.get(FieldSetter.java:217)
at org.jboss.ejb.client.EJBMethodLocator.<clinit>(EJBMethodLocator.java:43)
at org.jboss.ejb.client.EJBProxyInformation$1.doCompute(EJBProxyInformation.java:140)
at org.jboss.ejb.client.EJBProxyInformation$1.computeValue(EJBProxyInformation.java:72)
at org.jboss.ejb.client.EJBProxyInformation$1.computeValue(EJBProxyInformation.java:66)
at java.base/java.lang.ClassValue.getFromHashMap(ClassValue.java:226)
at java.base/java.lang.ClassValue.getFromBackup(ClassValue.java:208)
at java.base/java.lang.ClassValue.get(ClassValue.java:114)
at org.jboss.ejb.client.EJBProxyInformation.forViewType(EJBProxyInformation.java:242)
at org.jboss.ejb.client.EJBLocator.getProxyInformation(EJBLocator.java:375)
at org.jboss.ejb.client.EJBLocator.getProxyConstructor(EJBLocator.java:370)
at org.jboss.ejb.client.EJBLocator.createProxyInstance(EJBLocator.java:387)
at org.jboss.ejb.client.EJBClient.createProxy(EJBClient.java:161)
at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:163)
at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:84)
at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.lookupRemoteStatelessCalculator(RemoteEJBClient.java:141)
at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:53)
at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:40)
Caused by: java.lang.ClassNotFoundException: org.jboss.marshalling.JDKSpecific$1
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 21 more{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11035) ejb-remote quickstart fat client jar is not multi-release
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/WFLY-11035?page=com.atlassian.jira.plugin... ]
Michal Jurc reassigned WFLY-11035:
----------------------------------
Assignee: Michal Jurc (was: Eduardo Martins)
> ejb-remote quickstart fat client jar is not multi-release
> ---------------------------------------------------------
>
> Key: WFLY-11035
> URL: https://issues.jboss.org/browse/WFLY-11035
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 14.0.0.Final
> Reporter: Michal Jurc
> Assignee: Michal Jurc
> Priority: Critical
>
> The quickstart client application's instructions in section {{Build and Run The Quickstart as an Executable JAR}} currently don't seem to work on JDK11 as running the executable jar results in CNFE:
> {code:title=[mjurc@tigris client]$ java -jar target/ejb-remote-client-jar-with-dependencies.jar
> }Sep 17, 2018 12:02:01 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.9.Final
> Sep 17, 2018 12:02:01 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.6.0.Final
> Sep 17, 2018 12:02:01 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Sep 17, 2018 12:02:01 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Sep 17, 2018 12:02:01 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.2.Final
> Sep 17, 2018 12:02:02 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.8.Final
> Sep 17, 2018 12:02:02 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.11.Final
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/marshalling/JDKSpecific$1
> at org.jboss.marshalling.JDKSpecific.<clinit>(JDKSpecific.java:35)
> at org.jboss.marshalling.FieldSetter.get(FieldSetter.java:217)
> at org.jboss.ejb.client.EJBMethodLocator.<clinit>(EJBMethodLocator.java:43)
> at org.jboss.ejb.client.EJBProxyInformation$1.doCompute(EJBProxyInformation.java:140)
> at org.jboss.ejb.client.EJBProxyInformation$1.computeValue(EJBProxyInformation.java:72)
> at org.jboss.ejb.client.EJBProxyInformation$1.computeValue(EJBProxyInformation.java:66)
> at java.base/java.lang.ClassValue.getFromHashMap(ClassValue.java:226)
> at java.base/java.lang.ClassValue.getFromBackup(ClassValue.java:208)
> at java.base/java.lang.ClassValue.get(ClassValue.java:114)
> at org.jboss.ejb.client.EJBProxyInformation.forViewType(EJBProxyInformation.java:242)
> at org.jboss.ejb.client.EJBLocator.getProxyInformation(EJBLocator.java:375)
> at org.jboss.ejb.client.EJBLocator.getProxyConstructor(EJBLocator.java:370)
> at org.jboss.ejb.client.EJBLocator.createProxyInstance(EJBLocator.java:387)
> at org.jboss.ejb.client.EJBClient.createProxy(EJBClient.java:161)
> at org.jboss.ejb.client.EJBRootContext.lookupNative(EJBRootContext.java:163)
> at org.wildfly.naming.client.AbstractContext.lookup(AbstractContext.java:84)
> at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:144)
> at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.lookupRemoteStatelessCalculator(RemoteEJBClient.java:141)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:53)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:40)
> Caused by: java.lang.ClassNotFoundException: org.jboss.marshalling.JDKSpecific$1
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 21 more{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2409) Memory Leak in sliding window
by Srinivas ev (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2409?page=com.atlassian.jira.plugi... ]
Srinivas ev commented on DROOLS-2409:
-------------------------------------
Hi Mario,
For your comment -
>> The problem there is that inserting events in a so tight loop has the effect of overwhelming the engine not giving it a chance of getting any job done.
I have a similar case where in my application, the load may go up to 100 events per second and there will be a possibility of getting the same load for long hours. As per your statement regarding overwhelming the engine, the engine may fail to execute the rules for incoming events or eviction.
What solutions I can assume for this problem. When I did the experiment last time for my project, I observed drools engine consuming all the events into it without performing any operation regarding rule evaluations/persistence timers execution( for example).
I can share the reproducer in case needed. Thanks,
> Memory Leak in sliding window
> -----------------------------
>
> Key: DROOLS-2409
> URL: https://issues.jboss.org/browse/DROOLS-2409
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.6.0.Final
> Environment: Mac with Java 1.8 using Spring Boot (see attached demo project)
> Reporter: Mike Baranski
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: complete.tar.gz
>
>
> See attached project.
> `gradle test` causes an out of memory exception on my machine after ~2.6 million events. Events should be released for GC after 1 second, but that does not appear to be happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4109) Bump the kernel management API version to 9.0.0 and the xsd to 9.0
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4109?page=com.atlassian.jira.plugi... ]
Jeff Mesnil commented on WFCORE-4109:
-------------------------------------
EAP 7.2.0 mixed domain uses WildFLy 14.0.0.Final as a placeholder until EAP 7.2.0 is released.
The DomainHostExcludes720TestCase is expecting that WildFly 14 is a valid value from the host-release type that needs to be updated.
> Bump the kernel management API version to 9.0.0 and the xsd to 9.0
> ------------------------------------------------------------------
>
> Key: WFCORE-4109
> URL: https://issues.jboss.org/browse/WFCORE-4109
> Project: WildFly Core
> Issue Type: Task
> Components: Management
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Fix For: 7.0.0.Alpha1
>
>
> We know there are going to be API changes in WF Core 7, so we need to get the API version bumped so that when those changes happen appropriate transformers can be written to transform to the previous version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-10629) Server startup wrongly deploys all xml files and never stops
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10629?page=com.atlassian.jira.plugin... ]
David Lloyd resolved WFLY-10629.
--------------------------------
Assignee: (was: Jason Greene)
Resolution: Rejected
> Server startup wrongly deploys all xml files and never stops
> ------------------------------------------------------------
>
> Key: WFLY-10629
> URL: https://issues.jboss.org/browse/WFLY-10629
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Arnie Morein
>
> I have downloaded WF 12 and 13, then imported each into Eclipse (Oxygen.3a Release (4.7.3a)), OS is Win 7/x64; then used add-user to set up admin user. Then from both the command line and from within Eclipse, when the software starts up all of the xml configuration files get deployed at the same time despite the fact that the --server-config=standalone.xml parameter is present in either environment. What's worse, it starts versioning them and re-deploying them over and over and over again.
> {quote}
> 15:45:42,229 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
> 15:45:42,319 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:45:42,320 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml")
> 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml")
> 15:45:42,325 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml")
> 15:45:42,326 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml")
> 15:45:42,407 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> 15:45:42,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 6285ms - Started 549 of 746 services (326 se
> rvices are lazy, passive or on-demand)
> 15:45:42,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:42,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml")
> 15:45:42,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml")
> 15:45:42,724 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:45:42,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml")
> 15:45:42,726 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml")
> 15:45:47,921 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 28ms
> 15:45:47,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:47,930 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml")
> 15:45:47,982 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 55ms
> 15:45:47,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:48,059 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"
> 15:45:53,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 13ms
> 15:45:53,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:45:53,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:45:53,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 15ms
> 15:45:53,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:45:53,340 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:45:53,341 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:45:53,342 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months