[
https://issues.apache.org/jira/browse/OFBIZ-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421594#comment-15421594 ]
Taher Alkhateeb commented on OFBIZ-7951:
----------------------------------------
Hi Jacques, yeah those are createOfbizBackgroundCommandTask and spawnProcess. These two functions use the java ProcessBuilder API to fork a new process with output redirected to /runtime/logs/console.log and this is how OFBiz is started in the background. In fact, what happens exactly is that Gradle calls Gradle but in a new process.
Anyway, I tried a few more tests on my computer and I think it is relatively stable now. Thank you again for catching the bug and reporting it, and a few more tests would be great if you can spare some.
> remove ofbizSecure and ofbizBackgroundSecure targets from the gradle build script
> ---------------------------------------------------------------------------------
>
> Key: OFBIZ-7951
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7951> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Upcoming Branch
> Reporter: Taher Alkhateeb
> Assignee: Taher Alkhateeb
> Fix For: Upcoming Branch
>
>
> The tasks ofbizSecure and ofbizBackgroundSecure utilize the notsoserial API in the JVM arguments. However, given that this has no effect on system performance, we should make all tasks secure by default (ofbiz, ofbizDebug, ofbizBackground) and remove the secure tasks. This has the benefit of reducing the number of tasks users need to be aware of.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
