Andreas, That did the trick. It is working. Thanks a lot. Brasil.
Thanks a lot Andreas !! I got confused on what exactly the documentantion meant with jobscheduler.master.auth.users { jobscheduler_prod = "plain:secret" } and I did not replace the string :( my bad. I will try today. Regards.
Hi, Version -> 1.13.5 I have started from scratch just in case I had missing anything from this documentation provided. https://kb.sos-berlin.com/display/PKB/JOC+Cockpit+-+HTTPS+Authentication I have used pkcs12 for both keystores joc and scheduler master ... but joc does not communicate with scheduler (sos). JOC-400 / 401 JOC stderrout.log 2020-08-27T13:44:38,886 INFO qtp1635756693-30 c.s.j.c.JOCDefaultResponse - REQUEST: ./jobstreams/isalive PARAMS: {"jobschedulerId":"Tupi_40444","limit":10000}...
Uwe, I feel stupid. The clean cache of firefox worked. Abusing your time ... the installation process of JOC let's me choose a new oracle driver but it does not use it. I checked on the logs and still using oracle 6 driver. That causes a problem with Oracle 19c when joc tries to open session with dbms. Job scheduler took the oracle 8 driver. Not a show stopper as for now I moved to MariaDB. Best regards.
Hi, I went back to 1.13.3 as I plan to check the newest version. Issue is attached.
Hi, I went back to 1.13.3 as I plan to check the newest version. Issue is attached.
Uwe, Yes. I mentioned the switch to mariaDB as it is the only change I did other then reinstalling the product. All jobs are listed correctly on the JOC GUI jobs tab, but all the job chains are empty, including the ones delivered with the product. I will post the stderrout.log in a minute
It does not seem to be related with new version. I reinstalled old version and job chains also don't display job.chain jobs. I replaced Oracle with MariaDB as I could not get "joc" to use ojdbc8.jar I selected during the installation. JOC logs show it still using ojdcb6 driver which locks the user when accessing Oracle 19c. jobscheduler worked fine with ojdbc8.jar. I don't think it is related with MariaDB as all the objects are plain xml on disk. Thanks.