Goyat Mickael

There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...

There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...

Hello, I have another problem on my docker installation when I run a task, locally or using a local docker I use the same configuration, I have no problem sending the mail, but on sending using docker on a portainer I am no longer locally, I cannot resolve smtp.office365.com. Here is my configuration with my factory.ini. 2021-09-06 20:02:18.520Z [info] Task sos/sendMail/sendMail:718 - Protocol starts in /mnt/jobscheduler/data/scheduler/logs/task.sos,sendMail,sendMail.log 2021-09-06 20:02:18.547Z...

up

Nobody sees where my problem could come from?

Yes, I understood that I had to use postman for my POST request, my question should be more in the sense that I would like to access this kind of url, https://www.sos-berlin.com/JOC/1.13.3/raml-doc/JOC-API, The interface is intuitive while for my part I use Experimental API which has a not great interface.

Here are my container restart logs. At the start we can see that the port is available. Here are also my different containers present on my 3 clusters but none operate port 40444. Node 1: https://i.imgur.com/HpxX6Wq.png Node 2: https://i.imgur.com/aoSSAQY.png Node 3: https://i.imgur.com/BSxNvFH.png

Here are my container restart logs. At the start we can see that the port is available