[Opensource] Job Control ERROR:System Error

[Michael Rimov]

At 05:23 AM 11/2/2002 +0000, you wrote:
>Is this typical of the job manager operation?

Actually, I get a lot more success than that.  I typically queue and run 
jobs on a regular basis.  However, I'm only running one Job Server, and I'm 
doing it in VM.


>It seems to be a race condition. I have finally got a job to work
>with JCorporate, but I had to do *CHEAT MODE*. Yeh. I remember
>Mike R saying they were threading problems and the front end
>adding new jobs leaves much to be desired.

The typical method right now is to:

1 - Add the job with status NEW
2 - Add all the parameters.
When you're ready,
3 - Update the job status to AVAILABLE.

Although it's clunky, it SHOULD work, and I haven't had problems with it in 
that sense.


>I had to manually enter "com.jcorporate.eforum.job.IndexMessages"
>each and every time on the Admin / Operation. Sigh.
>
>It seems expresso on my laptop crashes every other restart
>
>restart tomcat - ok / compile / edit / deploy new job
>restart tomcat - expresso crashes
>restart tomcat - expresso runs
>+ test application
>+ ok / compile / edit / deploy new job
>restart tomcat - expresso crashes
>+ here we go again.
>
>Looks like job control is set for a overhaul/redesign.


>Error:
>         A com.jcorporate.expresso.core.controller.ControllerException 
> Error occurred at 2002-11-02 05:05:29 in database/context 'default' to 
> user 'Admin'
>         The requested URL was '/expresso/DBMaint.do'
>?dbobj=com.jcorporate.expresso.services.dbobj.JobQueue&state=List'
>         Nested exception message:Unable to execute statement: SELECT 
> COUNT(*) FROM  (com.jcorporate.expresso.services.dbobj.JobQueue, 
> db/context 'default'):

This is the first time, I've seen a stack trace like this.   Can you turn 
on SQL debug and try it, so we can see what order of statements goes out.

There are race conditions in JobQueue...but they shouldn't be THAT 
bad(!!).. ie low CPU stress jobs are unlikely to fail.  I'd like to at 
least track down the particular issue you're coming up against.

Thanks,
                                                         -Mike