How should I solve this problem? Please advise.
when API Start in the first Job, It will automate generate Job in Subsystem , and it still pending for the next Job. i want it automate end when my job finish, How can do i?
or
After calling post API complete, I want this job auto end job. Because now I still see this work on work active job. I want it to end after calling the API to work complete.
Auto end job after call api complete on work active job
-
- New User
- Posts: 16
- Joined: Thu Dec 07, 2017 10:13 pm
- First Name: chatchawan
- Last Name: phuttha
- Company Name: AYCAL
- City: bangkok
- Country: Thailand
- Contact:
Auto end job after call api complete on work active job
- Attachments
-
- fix API.png (174.83 KiB) Viewed 18006 times
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: Auto end job after call api complete on work active job
Hello iclassic,
The IBM HTTP Server (powered by Apache) will attempt to re-use jobs. After a program runs, it does not end the job, but keeps it active so that it can be re-use for subsequent requests. This greatly improves performance.
I think it is important to understand that this is part of the IBM HTTP server, not a part of Profound UI. Our product runs as an application on IBM's server, but changes that we make to our product would not change how the HTTP server keeps jobs active. To change that, you would need to make a request of IBM.
But, before you do that, I would take a moment to think about what you are trying to achieve? Causing these jobs to end would decrease performance. Are they causing a problem for you? Perhaps there's a different solution to that problem that would be better from a performance perspective? If you tell us what problems this is causing, it will make it easier for us to help you.
The IBM HTTP Server (powered by Apache) will attempt to re-use jobs. After a program runs, it does not end the job, but keeps it active so that it can be re-use for subsequent requests. This greatly improves performance.
I think it is important to understand that this is part of the IBM HTTP server, not a part of Profound UI. Our product runs as an application on IBM's server, but changes that we make to our product would not change how the HTTP server keeps jobs active. To change that, you would need to make a request of IBM.
But, before you do that, I would take a moment to think about what you are trying to achieve? Causing these jobs to end would decrease performance. Are they causing a problem for you? Perhaps there's a different solution to that problem that would be better from a performance perspective? If you tell us what problems this is causing, it will make it easier for us to help you.
-
- New User
- Posts: 16
- Joined: Thu Dec 07, 2017 10:13 pm
- First Name: chatchawan
- Last Name: phuttha
- Company Name: AYCAL
- City: bangkok
- Country: Thailand
- Contact:
Re: Auto end job after call api complete on work active job
thank you Scott.
Who is online
Users browsing this forum: No registered users and 3 guests