start "BURST" "%%~$path:f" -cp burst.jar;lib\*;conf nxt.Nxt
of course on the server setup we have the PATH set so the parsed code would be
start "BURST" java.exe -cp burst.jar;lib\*;conf nxt.Nxt
A few seconds later a console pops and the NXT code go forward. If it works right, the windows stays there, if not, the console closes and the error is barely seen.....I catch an unknown in parentheses....then it is gone.... the NXT log files is nothing different than a normal run. To find the point where NXT is started and add a pause at the end will mean tearing into the burst.jar and finding what happens. I extracted it and it is pretty deep...not even sure where to start looking in that code.
So, question is this, you open a console and start NXT running...it is going along fine and you want to kill it. CTRL+C works 90%, shutting the console windows is pretty bad, around 30%, Task Manager is not a pretty way to go, same as closing the window and gets a 35% success rate. That code line above uses java.exe. loading burst.jar as a lib and referring to an entry point defined in nxt.Nxt within that lib, yes?
I have seen a launch method for Java that involves a start and stop key, basically passwords in a way and the java program or script is sent to a local TCP port that is not being used.
I did a quick search and could not find it, but I did not the forum here for those things.