[Opensource] HELP - JOBS

[Tsanko Stefanov]

Hi Michael,

Thank you for your reply. I needed to make a demo of our system today so I 
went for a Task(Job) Manager of our own. Well it turned out I did a nice job 
and the things are stable and fast. With all my respect to your work I am 
sending you my code just in case.
One can specify the job's timeout as well as the period at which you want to 
run a scheduled job. There is a XML configuration file where you specify the 
scheduled job's parameters. It does not deal with a DB and I think the db 
interaction is the source of all Expresso Job's troubles. I took some stuff 
from core.job.Job but I needed that in order to change my Job's code as 
least as possible - plus I was in a hurry. I guess I am not dealing with the 
Digester the most efficient way but...

Anyway - thank you for your work and devotion to expresso.
Regards,
Tzanko


>From: Michael Rimov <rimovm at centercomp.com>
>Reply-To: opensource at jcorporate.com
>To: opensource at jcorporate.com
>Subject: Re: [Opensource] HELP - JOBS
>Date: Sun, 07 Jul 2002 06:31:08 -0700
>
>Turgay,
>
>At 04:30 PM 7/3/2002 +0000, you wrote:
>>Hi,
>>
>>I do not know what is wrong with the Jobs. Every now and then I get the 
>>following when I start the expresso:
>>ConfigManager: Expresso initialization complete
>>2002-07-03 12:22:52,138 ERROR [Thread-10] utility.JobHandler 
>>(JobHandler.java:73
>>5) - JobHandler unable to start correctly
>>com.jcorporate.expresso.core.db.DBException: No such field as 'StatusCode' 
>>in ob
>>ject 'com.jcorporate.expresso.services.dbobj.JobQueue'
>
>I've seen that happen once in a while before, and it turned out for my case 
>that the DBException wasn't correct.  If you run in a debugger, I'd highly 
>recommend putting a breakpoint at the exception in JobHandler that throws 
>that Exception and see what's really going on.  IIRC I fixed that reporting 
>problem in my batch to check into CVS.
>
>>Well when I restart it things seem fine. However recently my jobs do not 
>>get started any more. What happens is that the status field in the Job 
>>table is set to completed when a job is not created. I have dumps in  my 
>>job constructor and they do not appear. Suddenly things went back to 
>>normal and now again I have the same problem! What could possibly cause 
>>that?
>
>I believe there was a bug in JobHandler where if a Job thew a Throwable 
>(and I think even an Exception) that stack would wind past the run() and 
>the JobHandler would then die.  I've wrapped the Job execution in a 
>try/catch(Throwable) block to see if that would help and so far I've had 
>lots of buggy jobs die and JobHandler seems to keep on ticking. :)  I 
>checked the changelog.xml file and it seems that this fix was in ea-3 so 
>you MIGHT want to give it a try [or wait until ea-4]
>
>HTH, and sorry about the trouble you're having with Jobs, it's getting 
>slowly but surely tracked down.  And I want to especially thank Eddie Lewis 
>for his doc on Jobs and scheduling.  Saves everybody _a lot_ of spelunking 
>code!
>
>                                         -Mike
>
>
>_______________________________________________
>Opensource mailing list
>Opensource at jcorporate.com
>http://mail.jcorporate.com/mailman/listinfo/opensource
>Archives: http://mail.jcorporate.com/pipermail/opensource/




_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ansco_task.zip
Type: application/x-zip-compressed
Size: 7231 bytes
Desc: not available
Url : http://mailman.jcorporate.com/pipermail/opensource/attachments/20020708/dac56bcd/ansco_task-0002.bin