Logs show agent contacted, scheduler logs show nothing

And just so you know there is another bug i need to report. The software things a jab is running when its not. When i go to shut down the Master it says i will have to kill a spawned job but, there is now spawned job. Its the job i show up in a few post. The system thinks the Jobs is running and isnt and when you look at the begud log it shows i cant kill the job beacuse its not really running.

Here is the debug log on the agent after i tell the master to kill spawned jobs and restart. I cannot propmote this scheduler into a production environment if its going to just lose track of jobs running . I checked the queue and monitor and nothing was running when i restarted the Master. Please help

Its only when I run the job asynch here is a log i let it run asynch and nothing, restarted master to kill the "spawned job" that doesnt show up in the queue or monitor. I then scheduled the exact same job to run in a seperate queue and Bingo it worked.
31-Mar-2008 13:12:51 datablaster-at 46 reporttable extract Finish message sent.
31-Mar-2008 13:12:44 datablaster-at 46 reporttable extract Remote job finished.
31-Mar-2008 13:12:09 datablaster-at 46 reporttable extract Agent "IAT" contacted.
31-Mar-2008 13:12:01 datablaster-at 46 reporttable extract Start message sent.
31-Mar-2008 13:11:51 datablaster-at 46 reporttable extract Remote job started.
31-Mar-2008 13:10:56 datablaster-at -- 24x7 Scheduler 24x7 Scheduler starting...
31-Mar-2008 13:06:52 datablaster-at 46 reporttable extract Agent "IAT" contacted.
31-Mar-2008 13:06:44 datablaster-at 46 reporttable extract Start message sent.
31-Mar-2008 13:06:35 datablaster-at 46 reporttable extract Remote job started.

Does it happen to any async job or just to some of them? If some jobs are special in this sense, what kind of jobs are they?

/bin/sh -c ./ei_bat_reporttable_extract.php

Thats the command line im running. I set in a queue to run every hour and it did all night long without issue. As soon as i turn it on as asynch and let it run it doesnt work. I have two jobs that when i select to run asynch just dont work. The Master scheduler says they have started but nothing after that happens and we dont actually see them starting on agent side.

I think i see a problem. If i check the taskmanger when i have problems running asynch jobs it shows javaw.exe running multiple times. It should only be running once. It looks like it spawning the application and running multiple threads. I am not sure why or whats causing it but im almost 100% sure javaw.exe should only be running once. On some occasions the asynch jobs are running in a seperate JVM and never reporting to the agent\master. When it is only running once asynch jobs run when muliple javaw.exe processes are running they dont.

It is running asynch now but I guess what we need to figure out is why is javaw.exe starting multiple times

There could be multiple instances indeed. It is spawning a separate instance for every detached process. In other words, every detached job process is run as a separate process, to prevent any problems that can occur in that process to crash the entire system or affect other jobs directly.

The reason you see javaw instead of java is because you run the scheduler in graphical mode. If you run it without GUI it will use java instead of javaw and it will require less system resources and generically will be a lot faster.

In regard to async jobs not running, I will try to reproduce this on a Linux system using build 4.1.247.

Last edited by SysOp on Tue Apr 01, 2008 1:39 pm; edited 1 time in total

Ok , that makes sense then if its running in a seperate (detached) process but why even with a timeout it never finishes doesnt make sense. I had 4 javaw.exe process's running and nothing was showing running in monitor or the background queue. I am going to upgrade the hardware as well. It starting the process but doesnt make it to th agent , doesnt show in the queue but, shows the process spawned.

Please wait for 4.1.255. I guess, it will be released tomorrow. As for 4.1.247 and async jobs, I will get back to you on this shortly.