There can be much more jobs in the list, so once again I guess it’s related to your testing environment. Feel free to give us more details.
On Wed, Aug 29, 2018 at 9:20 AM Ветошкин Владимир en-trance@yandex.ru wrote:
Hi!
Why are there max 7 jobs in the job list? I have tried changing PARALLEL parameter - no effect.
25.08.2018, 22:39, "Ветошкин Владимир" en-trance@yandex.ru:
That seems to be the case. Thanks.
25.08.2018, 22:18, "Christian Grün" christian.gruen@gmail.com:
I see. So this must be an issue with Chrome (and, possibly, requests to localhost).
Ветошкин Владимир en-trance@yandex.ru schrieb am Sa., 25. Aug. 2018, 21:16:
Hmm.. When I request "test" in 2 tabs of chrome - only one job appears. But when I request the first "test" in one tab and the second "test" in another browser (or in incognito tab) - two jobs appears.
25.08.2018, 21:36, "Ветошкин Владимир" en-trance@yandex.ru:
Hi, Christian!
Oh, yes, I test it on an old single-core system :) Is it the reason? In DBA only one job listed. When the first "test" finish, in job list appers the second job.
25.08.2018, 21:15, "Christian Grün" christian.gruen@gmail.com:
Hi Vladimir,
parallel sleep requests will be evaluated in parallel indeed (see the attached screenshot). How did you test this?
If you have an old single-core system, it might happen that only one job will be executed at a time; but all jobs should be listed in the DBA, or when calling jobs:list-details().
Best, Christian
Why do requests to RESTXQ wait for finishing each other? For example: declare %rest:path("/test") %rest:GET function page:test() { prof:sleep(5000) };
If I make 2 requests to /test, the first ends in 5 sec, the second - in 10 sec.
-- С уважением, Ветошкин Владимир Владимирович
-- С уважением, Ветошкин Владимир Владимирович
-- С уважением, Ветошкин Владимир Владимирович
-- С уважением, Ветошкин Владимир Владимирович