
March 27th, 2005, 12:45 AM
|
|
Registered User
|
|
Join Date: Mar 2005
Location: San Diego
Posts: 1
Time spent in forums: 4 m 47 sec
Reputation Power: 0
|
|
|
Process Execution Problem
I'm currently writing a Java program that has two parts. A client side and a server side. The client side program sends a command across the network to the server. Based on the commands the server will launch a different program.
To make it simple, I'll just let you know that I'm starting different dedicated game servers. I'm using Runtime exec() to launch a process object of my dedicated game server. I also then use the client side program to initiate a command to shutdown the dedicated game server.
Everything works.....except: no one can connect to the game server. I have come across this interesting observation: While my Java program is running (and thus the JVM) the program cannot be interfaced with from the "outside" world. As soon as I force my Java program to quit, still leaving the dedicated game server running, the game can be "found".
It appears that as long as the JVM that spawned the process is running, nobody can interface with it (e.g. administration, playing, etc.). It doesn't even "appear" that it's running. But once the JVM is quit, and the process continues on its own, everything works fine.
I was just wondering if anyone knows about this and a possible way to work around it. I'm not too versed in the technical operations of Java since I do this as a hobby, but any assistance that you'd be willing to provide I would GREATLY appreciate. Thx in advance.
Kyle // SeniorQuico
|