You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this could be an issue but I cannot find any information about it, neither on the apache-php nor the laravel forums.
I'm running a job using your bundle and it takes about 5-6 seconds to complete. This job is just a loop of about 20 requests of an URI which returns a simple json response each time is called. Then I parse every response in turn.
Well, the problem is that while this job is running I can't make any concurrent request to any page of my laravel-based site. Actually, I can make the request but
I have to wait until the job has finished to get a response to the concurrent request.
I have tested in different environments (dev, production) and servers (apache, laravel built-in server) and the problem remains the same.
Thank you for any information or direction you can provide.
The text was updated successfully, but these errors were encountered:
thanks for your request. This issue sounds really strange and I will try to help you. Since PHP can handle multiple requests, running jobs and calling the website has to work at the same time. Somewhere in your code has to be something which doesn't work asynchronous. How do you make the 20 requests to the URI? Can you provide us an code snippet? And please remove Cron for a test: Just call your 20 requests to the URIs directly without Cron in a Route definition and test if you can make a request to any page of your laravel site. If this doesn't work either, it would not be a problem with Cron. But in this case, I will still try to help you.
Yes you are right. This problem is not related to your bundle. I've programmed the same job with crontab and it works flawlessly. Moreover, I've tested with two simple web pages (one with a loop taking a very long time) which are requested at almost the same time (first the one with the big loop) and the second request must wait to be processed.
It seems that Laravel is locking the session somehow and thus serializing the execution of multiple parallel requests. I'm trying with a different session driver (memcached) but I still can't figure out what is going on.
Thanks for your help and sorry for any inconvenience.
Hi!
I'm not sure if this could be an issue but I cannot find any information about it, neither on the apache-php nor the laravel forums.
I'm running a job using your bundle and it takes about 5-6 seconds to complete. This job is just a loop of about 20 requests of an URI which returns a simple json response each time is called. Then I parse every response in turn.
Well, the problem is that while this job is running I can't make any concurrent request to any page of my laravel-based site. Actually, I can make the request but
I have to wait until the job has finished to get a response to the concurrent request.
I have tested in different environments (dev, production) and servers (apache, laravel built-in server) and the problem remains the same.
Thank you for any information or direction you can provide.
The text was updated successfully, but these errors were encountered: