Handling JVM thrown exceptions during initialization

Question

I have one java process starting another java process with JMX support enabled in the following way

java -Dcom.sun.management.jmxremote.port=8088 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -jar app.jar

My problem is if the port 8088 is in use, the jvm of spawned process will throw BindException and the JVM will exit normally. There is no way for me to report back to the process that spawned process did not start because of bind exception. How can I catch/handle the BindException thrown by JVM so that the spawned process can do a System.exit(VALID_ERROR_CODE)? This exception happens even before any control is passed to the user code, so I guess it wouldn't be possible to handle it in the user code.

Any idea as how to handle this use case?

Does that get logged to stderr (System.err)? If so, you can have the launching process look for that and report the error. — BillRobertson42
– BillRobertson42, Commented Jan 5, 2012 at 0:35
If I remember correctly, due to this BindException your jvm shouldn't start in first place, then why do you need to call System.exit(...)? — kosa
– kosa, Commented Jan 5, 2012 at 5:44

Community · Accepted Answer · 2017-05-23 12:29:04Z

2

You should redirect stderr (and maybe also stdout) from your subprocess to the parent process or to System.err (System.out). Look on https://stackoverflow.com/a/1570269/1137529 for more details.

edited May 23, 2017 at 12:29

CommunityBot

11 silver badge

answered Jan 9, 2012 at 18:51

alexsmail

5,8239 gold badges41 silver badges57 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

64BitBob · Accepted Answer · 2012-01-09 18:56:04Z

0

Is it feasible to check if the port is open before launching the child process? i.e. Try listening on the port and if your socket fails, you know that port is unavailable. The advantage to this solution is that you could generate a new port number and keep testing until you find an open port. Once you have a valid port, you can modify the call to launch the child JVM with the available port.

answered Jan 9, 2012 at 18:56

64BitBob

3,1101 gold badge18 silver badges23 bronze badges

Collectives™ on Stack Overflow

Handling JVM thrown exceptions during initialization

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related