For me this usually means that I've got a zombie debugger somewhere occupying port 12121, and I have to find the process and kill it.
Better yet would be to discover exactly why this happens and give the user a helpful message. I can open $SOAR_HOME/SoarJavaDebugger.sh twice, and they are completely separate from one another and run without issue. So why is it that sometimes I have to track down and kill and existing debugger process before I can open another one?
For me this usually means that I've got a zombie debugger somewhere occupying port 12121, and I have to find the process and kill it.
Better yet would be to discover exactly why this happens and give the user a helpful message. I can open $SOAR_HOME/SoarJavaDebugger.sh twice, and they are completely separate from one another and run without issue. So why is it that sometimes I have to track down and kill and existing debugger process before I can open another one?