Always app Java end with “Exit 143” Ubuntu

前端 未结 2 750
無奈伤痛
無奈伤痛 2020-12-06 10:19

I have an application in java, which is permanently pulled. Execute it as follows:

nohup ant> log.txt &

The problem is that last ind

相关标签:
2条回答
  • 2020-12-06 10:50

    I ran into a similar issue while using nodejs, and it turned out that it was actually my app and my code that was killing it.

    I had code like this (ok, i don't have function names like that, but you get the point):

    kill_anything_that_is_still_running_from_previous_execution()
    start_a_lot_of_stuff()
    

    The problem was that kill_anything_that_is_still_running_from_previous_execution was async and returned immediately and (due to bad "luck") the actual killing part always ended up happening only after start_a_lot_of_stuff finished running, which is obviously not very great. #spawncamping

    Oh, and in Java Runtime.getRuntime().exec("bash -c \"killall whatever\"") is "async" if you don't wait for it to exit.

    0 讨论(0)
  • 2020-12-06 11:01

    Exit code 143 corresponds to SIGTERM, which is the signal sent by default when you run kill <pid>. Is it possible that another process or user is killing the application? Without more information it's difficult to suggest anything else.

    0 讨论(0)
提交回复
热议问题