Hi all ! We have a little problem with our cms in production. The problem is for the workflow and quartz scheduling publications. So, we have deploy the same cms on 2 differents hosts (felton and toppfer) that connect to the same database for the workflow and quartz. Everyone cms have his repository that also connect to the same database. But the repositories are in cluster and then I think it's not a problem. (Right ?)
When I schedule a publication. I can see in the workflow tables the taskID assigned for my document (os_propertyentry). I see also a record in the quartz tables for the assigned task (qrtz_triggers). When the trigger is launch, no publication occur but I see that the record on qrtz_triggers is deleted. I see also the taskID is not removed of the os_propertyentry table for this document. I think the problem come from the configuration of the cms. So each cms have in sites.xconf <domain>hippocms.smals-mvm.be</domain>. But in the qrtz_scheduler_state, I see 2 records (one for each server) but, the instance_name field contain felton and toppfer (the real name of the host). I made the same test (same CMS, same workflow) on our test server (only one host), and we have not this problem ! The documents are published Any ideas and remarks are welcome ! Many thanks for your answers. P.S. I have nothing in log files. ___________________________________________ Sébastian Molle SmalS - Web Content Management Nouveau Numero : +32 2 787 4614 ___________________________________________ ______________________________________________________________________________________________ Smals sluit elke aansprakelijkheid uit in verband met de juistheid, de volledigheid of het tijdig toekomen van de informatie in deze e-mail. Aan deze e-mail kunnen geen rechten worden ontleend en deze e-mail houdt in geen geval een erkenning van welkdanige aansprakelijkheid in. Dit bericht is alleen bestemd voor de geadresseerde. Indien dit bericht niet voor u bestemd is, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Smals décline toute responsabilité quant à l'exactitude, à l'exhaustivité et au délai de transmission des informations contenues dans cet e-mail. Aucun droit ne peut être revendiqué sur cet e-mail et cet e-mail n'implique en aucun cas une reconnaissance de responsabilité, quelle qu'elle soit. Ce message s'adresse uniquement au destinataire. Si ce message ne vous est pas destiné, nous vous prions de nous le signaler immédiatement et de détruire le message. ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
