Out of Memory Error from KieScanner

185 views
Skip to first unread message

Webster Homer

unread,
Jun 20, 2016, 10:14:03 AM6/20/16
to Drools Usage
We have an application using Drools 6.4 hosted in a Wildfly 8.2 app server. The application uses dynamic rules deployment via the KieScanner. I have noticed that after a while the scanner throws an out of memory error. It works find for a while, but eventually I see this:
17:51:21,564 ERROR [stderr] (Timer-1) Exception in thread "Timer-1" java.lang.OutOfMemoryError: GC overhead limit exceeded
17:51:21,601 ERROR [stderr] (Timer-1) at java.util.Properties.load0(Properties.java:345)
17:51:21,601 ERROR [stderr] (Timer-1) at java.util.Properties.load(Properties.java:341)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.TrackingFileManager.read(TrackingFileManager.java:61)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.readRepos(EnhancedLocalRepositoryManager.java:172)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.find(EnhancedLocalRepositoryManager.java:92)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:337)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
17:51:21,601 ERROR [stderr] (Timer-1) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
17:51:21,601 ERROR [stderr] (Timer-1) at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205)
17:51:21,601 ERROR [stderr] (Timer-1) at org.apache.maven.project.DefaultProjectBuilder.resolveDependencies(DefaultProjectBuilder.java:213)
17:51:21,602 ERROR [stderr] (Timer-1) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:186)
17:51:21,602 ERROR [stderr] (Timer-1) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:124)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.embedder.MavenEmbedder.readProject(MavenEmbedder.java:279)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:55)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:49)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.ArtifactResolver.getResolverFor(ArtifactResolver.java:136)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.ArtifactResolver.getResolverFor(ArtifactResolver.java:99)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.KieRepositoryScannerImpl.scanForUpdates(KieRepositoryScannerImpl.java:324)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.KieRepositoryScannerImpl.scanNow(KieRepositoryScannerImpl.java:281)
17:51:21,602 ERROR [stderr] (Timer-1) at org.kie.scanner.KieRepositoryScannerImpl$ScanTask.run(KieRepositoryScannerImpl.java:270)


Mario Fusco

unread,
Jun 21, 2016, 2:42:31 AM6/21/16
to Drools Usage

This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith.

Click http://www.merckgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.

--
You received this message because you are subscribed to the Google Groups "Drools Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-usage...@googlegroups.com.
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-usage/ba867d3f-6212-45fb-9928-b90d55eb9636%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Webster Homer

unread,
Jun 22, 2016, 10:42:03 AM6/22/16
to Drools Usage
thanks

Webster Homer

unread,
Jun 22, 2016, 10:49:19 AM6/22/16
to Drools Usage
Looks like the pull request for the fix was declined. What version will the version will contain the fix? I'd rather not have to apply it manually.


On Tuesday, June 21, 2016 at 1:42:31 AM UTC-5, Mario Fusco wrote:

Mario Fusco

unread,
Jun 22, 2016, 11:00:14 AM6/22/16
to Drools Usage
Sorry but I don't understand why you said that "the pull request for the fix was declined".
I merged my fix into master last Friday https://github.com/droolsjbpm/drools/commit/29cbab3edc3584c21f6aa918a923c772e5608c51
Am I missing something?

Mario

Webster Homer

unread,
Jun 24, 2016, 4:40:36 PM6/24/16
to Drools Usage
My confusion, when I read the Jira and the pull request it said "denied". In any case is there a point release with the fix? How do I get it?
Reply all
Reply to author
Forward
0 new messages