Handler `/var/task/Bref\LaravelBridge\Queue\QueueHandler` doesn't exist #111

dnl4 · 2023-04-15T02:57:58Z

dnl4
Apr 15, 2023

The docs example bellow give me an error:

constructs:
    jobs:
        type: queue
        worker:
            handler: Bref\LaravelBridge\Queue\QueueHandler
            runtime: php-81
            timeout: 60 # seconds

Error:

Unknown application error occurred
Runtime.Unknown

Then I changed it to

constructs:
    jobs:
        type: queue
        worker:
            handler: Bref\LaravelBridge\Queue\QueueHandler
            runtime: php-81-fpm
            timeout: 60 # seconds

Now I get the error:
Handler /var/task/Bref\LaravelBridge\Queue\QueueHandler doesn't exist

mnapoli · 2023-04-15T08:22:18Z

mnapoli
Apr 15, 2023
Maintainer

Can you make sure you are using the latest versions of Bref and the Laravel bridge?

This should be the first version btw, not the second.

0 replies

dnl4 · 2023-04-15T13:50:57Z

dnl4
Apr 15, 2023
Author

I'm using:

"bref/bref": "^2.0",
"bref/laravel-bridge": "^2.1",

I've just tested again with this code:

constructs:
    teste:
        type: queue
        worker:
            handler: Bref\LaravelBridge\Queue\QueueHandler
            runtime: php-81
            timeout: 60 # seconds

Then I've fetched the logs with serverless logs --function testeWorker:
Here is the full logs:

Running "serverless" from node_modules
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
INFO  Configuration cached successfully.
INFO  Configuration cached successfully.
INFO  Configuration cached successfully.
INFO  Configuration cached successfully.
Bref\LaravelBridge\Queue\QueueHandler
INFO  Configuration cached successfully.
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 328.26 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 311.14 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 351.30 ms Memory Used: 66 MB
START
Unknown application error occurred
Runtime.Unknown
END Duration: 355.62 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 374.54 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 690.82 ms Memory Used: 95 MB
START
Unknown application error occurred
Runtime.Unknown
END Duration: 746.28 ms Memory Used: 95 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 711.99 ms Memory Used: 95 MB
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
Bref\LaravelBridge\Queue\QueueHandler
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
START
Unknown application error occurred
Runtime.Unknown
END Duration: 726.31 ms Memory Used: 95 MB
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 846.64 ms Memory Used: 95 MB
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
INIT_START Runtime Version: provided:al2.v17    Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:f35635a04216ba4e6a0e74d3c2db080d443709a8f3f2e71fedf54a4f8756705d
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 337.55 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 358.56 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 325.59 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 392.41 ms Memory Used: 66 MB
Bref\LaravelBridge\Queue\QueueHandler
START
Unknown application error occurred
Runtime.Unknown
END Duration: 321.54 ms Memory Used: 66 MB

0 replies

dnl4 · 2023-04-15T15:24:01Z

dnl4
Apr 15, 2023
Author

Does this information help?

InvalidArgumentException
Invalid configuration value provided for "token". Expected Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable, but got string(884) "IQoJb3J******************"
token: (Aws\Token\TokenInterface|Aws\CacheInterface|array|bool|callable)
Specifies the token used to authorize requests. Provide an
Aws\Token\TokenInterface object, an associative array of "token", and an
optional "expiration" key, `false` to use a null token, or a callable token
provider used to fetch a token or return null. See Aws\Token\TokenProvider
for a list of built-in credentials providers. If no token is provided, the
SDK will attempt to load one from the environment.
at vendor/aws/aws-sdk-php/src/ClientResolver.php:431

0 replies

dnl4 · 2023-04-15T17:20:30Z

dnl4
Apr 15, 2023
Author

All the problems above were solved after downgrading aws-sdk-php from 3.263.11 to 3.244.0

https://github.com/aws/aws-sdk-php/issues/2567

0 replies

harshal-ringe · 2023-08-17T09:54:25Z

harshal-ringe
Aug 17, 2023

We are using PHP 7.3 and can't migrate to PHP 8 soon. The compatible versions for PHP 7.3 are "bref/bref": "1.7.34", "bref/laravel-bridge": "^1.2.3".

As per the documentation, in serverless.yml, we have to provide handler: Bref\LaravelBridge\Queue\QueueHandler but QueueHandler.php file is not present inside vendor/bref/laravel-bridge folder. So I have provided a handler: Bref\LaravelBridge\Queue\LaravelSqsHandler
But still, I'm getting this error: Handler /var/task/Bref\LaravelBridge\Queue\LaravelSqsHandler doesn't exist.

below is my serverless.yml file
service: web-serverless

provider:
name: aws
region: us-west-2
environment:
APP_ENV: dev

package:
# Directories to exclude from deployment
patterns:
- '!node_modules/'
- '!public/storage'
- '!resources/assets/'
- '!storage/'
- '!tests/'

functions:
# This function runs the Laravel website/API
web:
handler: public/index.php
timeout: 28 # in seconds (API Gateway has a timeout of 29 seconds)
layers:
- ${bref:layer.php-73-fpm}
events:
- httpApi: '*'
# This function lets us run artisan commands in Lambda
artisan:
handler: artisan
timeout: 120 # in seconds
layers:
- ${bref:layer.php-73} # PHP
- ${bref:layer.console} # The "console" layer

constructs:
jobs:
type: queue
worker:
handler: Bref\LaravelBridge\Queue\LaravelSqsHandler
layers:
- ${bref:layer.php-73}
timeout: 60 # seconds

plugins:
# We need to include the Bref plugin
- ./vendor/bref/bref
- serverless-lift

What could be the issue?

2 replies

mnapoli Aug 17, 2023
Maintainer

@harshal-ringe you are using an older version of this package, you should follow the old versions of the documentation.

harshal-ringe Aug 28, 2023

Thanks @mnapoli for your reply, I have migrated the project to the latest PHP and Bref versions and now the error has gone but the exceptions inside the workers are not getting logged on Cloudwatch. If there is any error worker, the job directly fails without logging the actual exception/error in Cloudwatch. It only logs production.INFO: Job failed Error executing "SendMessage" on "https://sqs.us-west-2.amazonaws.com/serverless-jobs.fifo". What changes I would have to make to log exceptions?

steverhoades · 2023-10-08T15:47:53Z

steverhoades
Oct 8, 2023

@dnl4 I am seeing the same issue migration from bref v1. to v2. How did downgrading the PHP SDK help here, the page you linked returns a 404. Thanks!

Bref: 2.1.3
Laravel Bridge: 2.1.3

4 replies

steverhoades Oct 8, 2023

Here is the error I am receiving. Definitely looks like some wires are being crossed as it's looking for a file location and not a class name?

serverless.yml

functions:
  worker:
    handler: Bref\LaravelBridge\Queue\QueueHandler
    ...

{
    "message": "Handler `/var/task/Bref\\LaravelBridge\\Queue\\QueueHandler` doesn't exist",
    "type": "Bref\\Runtime\\HandlerNotFound",
    "stackTrace": [
        "#0 /var/task/vendor/bref/bref/src/FunctionRuntime/Main.php(26): Bref\\Runtime\\FileHandlerLocator->get('Bref\\\\LaravelBri...')",
        "#1 /opt/bref/bootstrap.php(17): Bref\\FunctionRuntime\\Main::run()",
        "#2 {main}"
    ]
}```

It would appear that the Bref container is falling back to just the FileHandlerLocator, it's unclear at this point why this is happening.

steverhoades Oct 8, 2023

It would appear that the laravel-bridge bref-init isn't being executed thus the container isn't updated on the bref side.

mnapoli Oct 9, 2023
Maintainer

@steverhoades thanks for investigating, any idea why that file is not loaded? That is weird, Composer should automatically load it 🤔

Could you try running composer dump-autoload to see if it changes things?

steverhoades Oct 9, 2023

@mnapoli I'll look into this again ASAP. I will say that reverting back to my v1 configuration works (explicit handler files).

Mesuva · 2023-11-02T11:02:44Z

Mesuva
Nov 2, 2023

I'm hitting this issue at the moment and it has completely stumped me.

What's really strange is that I have SQS queues working fine on another project with the same setup, and very similar versions of laravel/bref and laravel-bridge. I've compared these projects, as far as doing diffs on files like serverless-state.json, and the config of the queues really appears the same.

I can successfully put a job on to the queue, but then when it gets processed I see in the Cloudwatch logs:

{"message":"Bref\\LaravelBridge\\Queue\\QueueHandler","type":"Illuminate\\Container\\EntryNotFoundException","stackTrace":["#0 \/var\/task\/vendor\/bref\/laravel-bridge\/src\/HandlerResolver.php(46): Illuminate\\Container\\Container->get('Bref\\\\LaravelBri...')","#1 \/var\/task\/vendor\/bref\/bref\/src\/FunctionRuntime\/Main.php(26): Bref\\LaravelBridge\\HandlerResolver->get('Bref\\\\LaravelBri...')","#2 \/opt\/bref\/bootstrap.php(17): Bref\\FunctionRuntime\\Main::run()","#3 {main}"]}

So it doesn't get as far as looking at my job, it can't find QueueHandler.
I've checked /vendor/composer, and can see QueueHandler referenced in autoload_static.php, path looks fine
I'm on bref 2.1.5, laravel-bridge 2.1.3, and the latest Laravel v10. But I've also tried winding some of those back to the specific locked versions on the working project, with no luck
I've even tried using the specific version of Laravel itself from the working project.

I'm pretty sure bref-init.php is running, as the logs include before the error Running 'php artisan config:cache' to cache the Laravel configuration, and that appears to be an output from that script. We then get a INFO Configuration cached successfully.

The error message refers in the stack trace to Bref\LaravelBridge\HandlerResolver, so it appears that LaravelBridge is being picked up and has been autoloaded. (I think that's set up in bref-init.php too)
My queue is configured in serverless.yml as per the docs:

constructs:
  jobs:
    type: queue
    worker:
      handler: Bref\LaravelBridge\Queue\QueueHandler
      runtime: php-81
      timeout: 60 # seconds

in my deployment script, I'm using composer install --optimize-autoloader --no-dev
I'm running PHP8.1

The rest of the application in general is working fantastically in production. I'm doing this work on a staging copy, but the setup is pretty much identical (and the staging application works fine too, it's just the queue handling).

I can't think what else to check/upgrade/compare.
@mnapoli - I'd be very interested to pay for further enterprise support, even if it's just for more ideas of what to investigate!

7 replies

Mesuva Nov 2, 2023

Howdy Matthieu, I really appreciate your thoughts here!

I thought about the double escaping too, and did try putting quotes around the handler, but no luck there. I've even thought about weird unicode characters from a cut and paste.
I had checked the handler in Lambda, looks fine. Code is too big to edit, but overall the application works fine. If something else was corrupt more broadly with composer I reckon the app would be breaking in other places.
not deploying via Docker, but I did try just in normal controller doing something like:

   $container = app();
   $handler = $container->get( 'Bref\LaravelBridge\Queue\QueueHandler' );

That throws an error, whilst I can target other classes within Laravel Bridge without error.. (but I admit I'm not sure if it's supposed to work or not)

I am already running on this project a database based queue, but for testing I've just changed QUEUE_CONNECTION to 'ses', but only one SES queue as such. My goal is to run both, sending some jobs to the database one, and some to this new SES one.
Running on mac, and deploying 6 other Laravel/bref apps serverless from my machine. Nothing unusual I can think of!
I've updated composer, but not thought to check serverless itself. Will check that.
I do have two more files in /bootstrap/cache, which are livewire-components.php and events.php. But I have both of those in my working project as well.
I'm planning to try something similar by adding a queue to another project I'm working on

The only 'unusual' thing about this project I guess is that it's one I've worked on over quite some time, maybe a year and a half, and updated along the way. There must be some little override or config somewhere I've missed.

Going to test this process on my other project next.

Mesuva Nov 2, 2023

Just updated to serverless 3.36.0, no change.

Also just tried a SQS queue on a new project, worked as expected!

mnapoli Nov 2, 2023
Maintainer

Oh, that's good at least.

Here is what the Laravel-Bref bridge is doing:

        $this->app->when(QueueHandler::class)
            ->needs('$connection')
            ->giveConfig('queue.default');

Maybe try adding that into your own ServiceProvider? That's not ideal, but maybe it will be enough?

Maybe the project is old enough that some automatic registration (service provider? service class?) that has been added in Laravel since isn't happening.

Also I would indeed expect this to work in a controller, so there's definitely something wrong:

   $container = app();
   $handler = $container->get( 'Bref\LaravelBridge\Queue\QueueHandler' );

Mesuva Nov 2, 2023

Well, I've got it working.

And it's probably the most frustrating mistake I've made in the last year. It's almost comical.

What made it hard to pick up was that the EntryNotFoundException exception is very misleading, it's more of a fall back exception, than something that's true.

What I did was edit /laravel/framework/src/Illuminate/Container/Container.php, and adjust the get() function there, to just throw $e as soon as it was caught. Otherwise the specific exception is ignored, and you get a EntryNotFoundException.

When I did that, I got:

Fatal error: InvalidArgumentException: The [ses] queue connection has not been configured. in /var/task/vendor/laravel/framework/src/Illuminate/Queue/QueueManager.php:159

Spot the issue?

In my severless.yml file, I accidentally set QUEUE_CONNECTION to 'ses', and not 'sqs'.
I didn't spot it, as I set some variables like this:
QUEUE_CONNECTION: ${self:custom.environments.QUEUE_CONNECTION.${sls:stage}}

So ONE letter mistake, has cost me a day or so's worth of debugging.
At least I dug through the code a fair bit and have a better understanding of how it all works!
What a doofus.

Thanks again for the suggestions for debugging, I owe you another 🍺 @mnapoli !

The only issue now I'm hitting is that I doesn't look like I can set the default to the database connection, but send to the SQS queue. It looks like you have to set the SQS as the default for this to work. I may have to try it the other way around, where I specifically send jobs to the database queue. (or I rework that and just use SQS)

LewisW Mar 16, 2024

@Mesuva Don't worry, you are not the only careless developer out there.... I had made the same mistake and you saved me a lot of pain! Thank you.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Handler `/var/task/Bref\LaravelBridge\Queue\QueueHandler` doesn't exist #111

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 7 comments 13 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Handler /var/task/Bref\LaravelBridge\Queue\QueueHandler doesn't exist #111

Replies: 7 comments · 13 replies

mnapoli Apr 15, 2023 Maintainer

dnl4 Apr 15, 2023 Author

dnl4 Apr 15, 2023 Author

dnl4 Apr 15, 2023 Author

mnapoli Aug 17, 2023 Maintainer

mnapoli Oct 9, 2023 Maintainer

mnapoli Nov 2, 2023 Maintainer

Handler `/var/task/Bref\LaravelBridge\Queue\QueueHandler` doesn't exist #111

Replies: 7 comments 13 replies

mnapoli
Apr 15, 2023
Maintainer

dnl4
Apr 15, 2023
Author

dnl4
Apr 15, 2023
Author

dnl4
Apr 15, 2023
Author

mnapoli Aug 17, 2023
Maintainer

mnapoli Oct 9, 2023
Maintainer

mnapoli Nov 2, 2023
Maintainer