I cannot seem to get the 3.6.1 or 3.5.11 versions to actually launch the server. Not a lot in the logs to go on either... Anyone else see this or is it just me?
Removing the "start" from the end there, which comes from "!_APP_ARGS!" gets it alive. So, a quick edit to the start: portion of the .bat file to read:
set CMD="%_JAVACMD%" !_JAVA_OPTS! !JATOS_OPTS! -cp "%APP_CLASSPATH%" %APP_MAIN_CLASS%
It worked for me on a freshly installed Windows 11. No problems, no errors. But do I understand you correctly, you got it going on your machine? I'm not so much a Windows user anymore. Do you think there is a bug in JATOS running on Windows 11? Is there something we can fix?
Comments
FWIW, the loader.bat builds up this command:
"C:\Users\craig\dev\jatos_win_java_361\\jre\win64_jre\bin\java.exe" -Dpidfile.path="C:\Users\craig\dev\jatos_win_java_361\\RUNNING_PID" -Dconfig.file="conf/production.conf" -Dplay.http.secret.key=158401703230831651827500378416063362014791 -Dhttp.port=9000 -Dhttp.address=127.0.0.1 -cp "C:\Users\craig\dev\jatos_win_java_361\\lib\*" play.core.server.ProdServerStart start
Removing the "start" from the end there, which comes from "!_APP_ARGS!" gets it alive. So, a quick edit to the start: portion of the .bat file to read:
set CMD="%_JAVACMD%" !_JAVA_OPTS! !JATOS_OPTS! -cp "%APP_CLASSPATH%" %APP_MAIN_CLASS%
and at least I'm going
Hi,
I didn't try JATOS on Windows 11 yet. Let me grab a copy and come back to you.
Best,
Kristian
It worked for me on a freshly installed Windows 11. No problems, no errors. But do I understand you correctly, you got it going on your machine? I'm not so much a Windows user anymore. Do you think there is a bug in JATOS running on Windows 11? Is there something we can fix?
Best,
Kristian