So Mario, First it appears that you mysteriously cannot build where everyone else can. Now you are having mysterious problems with ManifoldCF being able to do basic state transitions. I'm unable to reproduce any of these things. More worrisome, you seem to have the opinion that rather than fix underlying deployment or infrastructure issues, the right solution is just to hack away at the database or the code.
This doesn't work for me. I'd like to help you out here but there's a basic level of cooperation needed for that. The way you do deployments in ManifoldCF that we know will be successful is by starting with one of the distribution examples and (if needed) modifying that to meet your individual needs. If you are having bizarre things take place, almost always it's because you didn't start with one of the examples and therefore you wound up configuring things in a bizarre way. So if you cannot get past your current problem, I STRONGLY recommend you start over: - Checkout a new copy of trunk and build following the instructions I gave in the other email thread. Follow them to the letter please. - Pick your deployment model. - Point it at your database instance. - Start it USING THE SCRIPTS PROVIDED. Your problems should resolve. If not, you should have logging in manifoldcf.log telling you what is going wrong. Karl On Wed, Aug 19, 2020 at 6:40 AM Karl Wright <daddy...@gmail.com> wrote: > You do not see log output. Therefore I need to ask you some questions. > > What deployment model are you using? single process or multi-process? > what is the synchronization method? > > > On Wed, Aug 19, 2020 at 6:38 AM Karl Wright <daddy...@gmail.com> wrote: > >> Usually when you shut down the agents process (or the whole thing) and >> restart it will fix problems like that UNLESS the problem persists because >> a step in the state flow is failing. If it is failing you would see log >> output. Do you see log output? >> >> Karl >> >> >> On Wed, Aug 19, 2020 at 5:40 AM Bisonti Mario <mario.biso...@vimar.com> >> wrote: >> >>> No, I haven’t a notification connector, buti it isn’t the problem. >>> >>> Manifoldcf.log is empty >>> >>> >>> >>> The problemi s that job is on hanging state and I would like to reset >>> its state >>> >>> >>> >>> >>> >>> >>> >>> *Da:* Karl Wright <daddy...@gmail.com> >>> *Inviato:* mercoledì 19 agosto 2020 11:31 >>> *A:* user@manifoldcf.apache.org >>> *Oggetto:* Re: How to reset job status >>> >>> >>> >>> There should be output in your manifoldcf.log file, no? This may be the >>> result of you not having a notification connector's code actually >>> registered so you get no class found errors. The only solution is to put >>> the missing jar in place and restart your agents process. Have a look at >>> the log to confirm. >>> >>> >>> >>> Karl >>> >>> >>> >>> >>> >>> On Wed, Aug 19, 2020 at 4:56 AM Bisonti Mario <mario.biso...@vimar.com> >>> wrote: >>> >>> Hallo >>> >>> I have a job in a status “End notification” that hangs on this state. >>> >>> >>> >>> Is there a way to reset it? >>> >>> >>> >>> I tried the script lock-clean.sh without effect. >>> >>> >>> >>> In thise state I am not able to manage jobs. >>> >>> >>> >>> >>> What could I try, please? >>> >>> >>> >>> >>> Thanks a lot >>> >>> Mario >>> >>>
