-
Notifications
You must be signed in to change notification settings - Fork 22
queue_url => null #38
Comments
ping @basz, you did tell you tested the new version didn't you? Can you please have a look? :) |
what does |
|
Okay, so I've been playing with this a bit more -- just to ensure I don't have Aws misconfigured. When I manually run:
I get expected output (after defining the appropriate version, either in configuration with ['aws' => ['Sqs' => ['version' => 'latest']]) or with the #37 approach (closing and not merging since the configuration way works just as well). So ... that seems to just leave the plugin manager not passing the right 'name' in. Also, If I get rid of the manually defined queue_url section and name the 'queue' to be consistent with the actual queue name on AWS the issue persists ... so neither manual configuration, nor automagic discovery resolves to the right Queue. Output from echoing the exception:
If I add in:
I get:
|
Yeah, I think I see what’s going on… But, I can’t seem to configure SQS permissions correctly for a test project…. Keep getting Annoying… I’ll keep trying a bit more |
IAM Policy sample: works if you DIRECTLY use the SqsClient from AWS.
Otherwise you get the non-existent queue problem if you're working inside of the SlmQueueSQS module. |
could you change https://github.com/juriansluiman/SlmQueueSqs/blob/master/src/SlmQueueSqs/Factory/SqsQueueFactory.php#L46 into
|
Yep, that fixes it up quite nicely! |
i'll submit a PR |
My Bad. Great! Should only affect servicemanager 2.* ping bakura10 to tag a hotfix (no commit rights pour moi :-) ) when your done... |
Okay, please ping me on the PR :). |
I'm going to squash first, so hold up a sec :-) |
In my tests i notice that for SQS the MaxPollingFrequencyStrategy is nessescary. However, I would assume it should only wait when there are no jobs on the queue. It does not do that. It processes a job and then waits a bit, next job, wait, next.... If I change it to listen to the Idle Event then waits with polling only when there are no jobs... Can you (@bakura10) confirm that that would be the desired behaviour? |
btw. used for test purposes https://github.com/basz/sim-queue-test-application |
Sorry for the commit spam here -- the latest squashed one has the formatting changes I made in documentation looking better. |
Just tagged as 0.6.1! :) |
After issue #37 is integrated that resolves the missing version number, another error arises.
To summarize, it seems like the $name being passed in to SlmQueueSqs\Queue\SqsQueue __construct method is
"SlmQueueSqs\Queue\SqsQueue" rather than the expected queue name. Furthermore, this leaves the queue_url as being null (queueUrl in $this->queueOptions).
I haven't yet narrowed down where the issue is at ... but something seems amiss when one defined the following:
inside my factory, I have the following (works with the AWS v2 and Slm 0.4 side of things):
I'm thinking there's an issue with either SlmQueue's plugin manager ... or the SlmQueueSQS plugin manager that for some reason isn't getting the right name passed in.
The text was updated successfully, but these errors were encountered: