Running master.bat on Windows 2003, I often encounter a situation where a job is declared "Finished" in the log yet it does not leave the queue. The debug logs do not indicate anything unusual.

When I try to delete the job from the queue, it does not go away. When I exit the application, a message box says that a spawned job will be forcefully stopped. However, after the application has exited, it's apparent from Task Manager that 24x7's instance of javaw.exe is still runnning.

After this type of dirty exit, it's common to have a preference-file-related exception on the next startup.

Any thoughts on what is happening here?

What kind of job is that? Can you see it in the Task Manager?
Which version of 24x7 are you running?

: Running master.bat on Windows 2003, I often encounter a situation where a job
: is declared "Finished" in the log yet it does not leave the
: queue. The debug logs do not indicate anything unusual.

: When I try to delete the job from the queue, it does not go away. When I exit
: the application, a message box says that a spawned job will be forcefully
: stopped. However, after the application has exited, it's apparent from
: Task Manager that 24x7's instance of javaw.exe is still runnning.

: After this type of dirty exit, it's common to have a preference-file-related
: exception on the next startup.

: Any thoughts on what is happening here?

: What kind of job is that?

A JavaScript job that executes a Process.runAndWait, which runs a Java command-line app. I've tried "Run Program" mode too, using the OS command for the Java app--same result.

: Can you see it in the Task Manager?

I cannot see the Java app in the Task Manager after it is done, although it remains in the queue.

: Which version of 24x7 are you running?

Multiplatform Java Edition, version 4.0, build 215

Let's test 2 simple things:

1. Create a new JavaSCript job with the following code
Scheduler.pause(10);

Run and check if it also gets stuck in the queue.

2. Let's modify your other job and change RunAndWait to Run. Also please remove the timeout parameter. Run only needs 2 parameters as compared to RunAndWait.

Run and check if it also gets stuck in the queue.

Please let us know what you get there.

: A JavaScript job that executes a Process.runAndWait, which runs a Java
: command-line app. I've tried "Run Program" mode too, using the
: OS command for the Java app--same result.

: I cannot see the Java app in the Task Manager after it is done, although it
: remains in the queue.

: Multiplatform Java Edition, version 4.0, build 215

: 1. Create a new JavaSCript job with the following code
: Scheduler.pause(10);

This does not get stuck.

: 2. Let's modify your other job and change RunAndWait to Run. Also please
: remove the timeout parameter. Run only needs 2 parameters as compared to
: RunAndWait.

This still gets stuck.

FYI, for the sake of eliminating other possible causes, I simplified the script down to just calling run().

Ok, we can conclude the following: starting a process from JavaScripts leads to job hanging in the queue.

Please enable the tracing option in the Tools/Options menu Log page. And run the job again. This should produce debug.log file when the job runs. Please let us know if you get any exceptions in that file.

Also please let us know how the job is setup to run: detached/non-detached, asynchronous/synchronous

: This does not get stuck.

: This still gets stuck.

: FYI, for the sake of eliminating other possible causes, I simplified the
: script down to just calling run().