[jira] [Reopened] (OFBIZ-11954) Expiring Daemon because JVM heap space is exhausted

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Reopened] (OFBIZ-11954) Expiring Daemon because JVM heap space is exhausted

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-11954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacques Le Roux reopened OFBIZ-11954:
-------------------------------------

I reopen because, [as explained in my last message in dev ML|https://markmail.org/message/vn4kibqtr7skczat] increasing {{org.gradle.jvmargs}} did not work for me. As I don't need failing daemons, I locally use {{org.gradle.daemon=false}}.

I'm not sure it's due to Gradle 6.5 version as suggested James, but it seems. I'll ask on dev ML if it's OK to commit {{org.gradle.daemon=false}} as a temporary workaround, waiting for a Gradle fix or upgrade. Only trunk would be concerned.

An alternative is to revert the commits below. But as it was hard to handle conflicts by hand, I'd like to avoid that.


> Expiring Daemon because JVM heap space is exhausted
> ---------------------------------------------------
>
>                 Key: OFBIZ-11954
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11954
>             Project: OFBiz
>          Issue Type: Bug
>          Components: Gradle
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 18.12.01
>
>
> Today I got this in log out of the blue:
> {quote}
> Daemon will be stopped at the end of the build after running out of JVM memory
> Expiring Daemon because JVM heap space is exhausted
> {quote}
> I checked there was no OutOfMemoryError exception. And apart that in log the applications were running well
> The most relevant articles I found on the Net were:
> https://stackoverflow.com/questions/56075455/expiring-daemon-because-jvm-heap-space-is-exhausted
> https://medium.com/@tiwarishani/expiring-daemon-because-jvm-heap-space-is-exhausted-in-react-native-e17c2248c8af
> I'm not sure this issue will reproduce (why just now?). I'll discuss this on dev ML before increasing
> org.gradle.jvmargs



--
This message was sent by Atlassian Jira
(v8.3.4#803005)