java cli default argument -Xss8G causes a crash

[iharsuvorau]

@Mcamargo85

On macOS 11.4 with java:

java version "15.0.1" 2020-10-20
Java(TM) SE Runtime Environment (build 15.0.1+9-18)
Java HotSpot(TM) 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)

running python simod_console.py fails with:

 -- Mining Process Structure --
Invalid thread stack size: -Xss8G
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
[Errno 2] No such file or directory: 'outputs/20210701_8512596F_0181_4932_89A5_87F7430B474D/PurchasingExample.bpmn'

Java tool failed because of -Xss8G. Changing it to a smaller number -Xms1024M works okay.

[Mcamargo85]

Issue solved with the java parameters update

[iharsuvorau]

@Mcamargo85

Yes, issue is solved when you manually change java parameters in code, but should we expect every user to do so before the run? Should we mention it in the documentation? Is it possible to recognize this parameter depending on the environment?

[Mcamargo85]

I think that for the moment, you can leave default parameters depending on the environment. However, this should not be a problem in the future because it is related to the java virtual machine, and precisely the idea is to remove the dependency with java. From: Ihar Suvorau ***@***.***> Sent: Thursday, July 1, 2021 4:09 PM To: AdaptiveBProcess/Simod ***@***.***> Cc: Manuel Alejandro Camargo Chavez ***@***.***>; Mention ***@***.***> Subject: Re: [AdaptiveBProcess/Simod] java cli default argument -Xss8G causes a crash (#13) @Mcamargo85<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMcamargo85&data=04%7C01%7Cma.camargo11%40uniandes.edu.co%7C87add6c3e58c48da4c7508d93c916d9e%7Cfabd047cff48492a8bbb8f98b9fb9cca%7C0%7C0%7C637607417573341580%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2UkyIF46ym5AB624mni4cqgVLQRXLRmtByo%2FrVEuU7A%3D&reserved=0> Yes, issue is solved when you manually change java parameters in code, but should we expect every user to do so before the run? Should we mention it in the documentation? Is it possible to recognize this parameter depending on the environment? - You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAdaptiveBProcess%2FSimod%2Fissues%2F13%23issuecomment-872233421&data=04%7C01%7Cma.camargo11%40uniandes.edu.co%7C87add6c3e58c48da4c7508d93c916d9e%7Cfabd047cff48492a8bbb8f98b9fb9cca%7C0%7C0%7C637607417573351537%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=q90AGEqZ559DyqpLIxlo2aoXyqtVlMnSG%2B1uaZJcRkg%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJEHTC3QA3IHRSHM6XLXTIDTVRSHVANCNFSM47UGH57Q&data=04%7C01%7Cma.camargo11%40uniandes.edu.co%7C87add6c3e58c48da4c7508d93c916d9e%7Cfabd047cff48492a8bbb8f98b9fb9cca%7C0%7C0%7C637607417573351537%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=By1mJe6L%2BGYiiI3JvQ3G8spTwnLiC8YsAyFgvPMxpjI%3D&reserved=0>.

[iharsuvorau]

@Mcamargo85 Great, thanks. Now it's clear.