[
https://issues.apache.org/jira/browse/SOLR-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618150#comment-17618150
]
Kevin Risden commented on SOLR-8803:
------------------------------------
[~elyograg] your Gradle behavior sounds like an issue w/ the Gradle Daemon - I
personally turn it off. The daemon can sometimes be helpful, but in a lot of
cases it can hang and cause weird behavior. you may even want to check if there
are Gradle Daemons still running you want to disable.
{code:java}
cat .gradle/gradle.properties
org.gradle.daemon=false
{code}
{quote}I have no experience running a Java program inside a debugger. I use
eclipse for editing Java source code.
I had a test version log all the sysprops and did not see the errorfile in any
of it. If it is available, it is probably a dedicated method somewhere. I
haven't gotten a reply on my question from the openjdk mailing list.{quote}
I'll see if I can poke around a little bit.
> OOM killer for Windows
> ----------------------
>
> Key: SOLR-8803
> URL: https://issues.apache.org/jira/browse/SOLR-8803
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 9.0
> Reporter: Binoy Dalal
> Assignee: Shawn Heisey
> Priority: Minor
> Labels: OOM, oom
> Fix For: 9.2
>
> Attachments: SOLR-8803-1.patch, SOLR-8803-2.patch, SOLR-8803-3.patch,
> SOLR-8803-4.patch, SOLR-8803-5.patch, SOLR-8803-6.patch, SOLR-8803-7.patch,
> SOLR-8803.patch, oom_win.cmd, solr-8803-build-transcript.txt
>
>
> Solr on windows does not currently have a script to kill the process on OOM
> errors.
> The idea is to write a batch script that works like the OOM kill script for
> Linux and kills the solr process on OOM errors while creating an OOM log file
> like the one on Linux systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
