nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

scheduled deployment didnt start

CRB

hello,
on OD 6.1 w2k3... we have this everyday schedule, and somehow couple nights, back the deployments didnt kick off as scheduled... and there wasnt anything in the logs that shows that OD was shut down or that a deployment failed... it simpll seems like there wasnt anything scheduled... but i still see them scheduled and active... so i had to just "recreate" the schedule... just by editing starting date or time and save it and now it s working properly... so i was wondering if the schedule got corrupted or something, i never seen this before? anybody had this happen before? or a guess to cause the deployment to not start as scheduled.

Find more posts tagged with

Comments

Adam Stoller

hello,
on OD 6.1 w2k3... we have this everyday schedule, and somehow couple nights, back the deployments didnt kick off as scheduled... and there wasnt anything in the logs that shows that OD was shut down or that a deployment failed... it simpll seems like there wasnt anything scheduled... but i still see them scheduled and active... so i had to just "recreate" the schedule... just by editing starting date or time and save it and now it s working properly... so i was wondering if the schedule got corrupted or something, i never seen this before? anybody had this happen before? or a guess to cause the deployment to not start as scheduled.

Are you using the OOTB db for the scheduler - or have you replaced it with a (real) DB?

The OOTB scheduler database is more of a POC and not really intended to be used for production purposes - one of the OD manuals describes how to configure a (real) DB for use by the scheduler process.

CRB

i didnt do any extra configuration, i am using whatever comes with OD 6.1 by default... so i assume that i am using the OOTB...if that s wht i am using... does it cause problems to scheduled deployments like what happend to me?because we have been using the same thing for months and months. and i never had a deployment tht didnt start on time.

Adam Stoller

i didnt do any extra configuration, i am using whatever comes with OD 6.1 by default... so i assume that i am using the OOTB...if that s why i am using... does it cause problems to scheduled deployments like what happend to me?because we have been using the same thing for months and months. and i never had a deployment tht didnt start on time.

It sounds like the kind of thing that can happen with the OOTB scheduler DB - though feel free to check with Support.

John742

Fish,
IN RE to using a RDBMS, are you referring to this specifically for OD 6.1.x ? It has been IWOV's stance in the past 6.0.X and prior, that anything other than the OOTB of scheduler is NOT supported. I do 100% agree that an RDBMS is the way to go and that the manual and the comments in the XML config files lend to the belief that it should be supported. Just be aware that Interwoven's best suggested practice is the OOTB implementation of scheduler and all is considered unsupported. Can it be done? Yes. Are there outstanding issues? Yes (ie connection pooling is error proned)

Adam Stoller

Fish,
IN RE to using a RDBMS, are you referring to this specifically for OD 6.1.x ? It has been IWOV's stance in the past 6.0.X and prior, that anything other than the OOTB of scheduler is NOT supported. I do 100% agree that an RDBMS is the way to go and that the manual and the comments in the XML config files lend to the belief that it should be supported. Just be aware that Interwoven's best suggested practice is the OOTB implementation of scheduler and all is considered unsupported. Can it be done? Yes. Are there outstanding issues? Yes (ie connection pooling is error proned)

Hmm - this is news to me. The OOTB is a Hypersonic DB which I recall being stated as *not* intended to be used for production purposes (though maybe that was just for event reporting?) - however there's an entire section in the manual for defining the scheduler DB which goes over the steps that need to be done for using a 3rd party DB....

John742

I 100% agree. HSQL is called out as not supported for Event Subsystem, but IWOV estimates that since scheduler is low turnover, HSQL is worthy of a prod setup. We have scheduler setup within an oracle instance, but it has issues reconnecting after connection interruptions. OD must be restarted and all is well. If I find a fix for this I will add to this thread.