Releases: kaliop-uk/kueueingbundle-sqs
0.10.1
0.10.0
-
NEW: the bundle is now compatible with FIFO queues
In order to send messages to a FIFO queue, set themessage_group_id
in the queue_options configuration -
NEW: it is now possible to set custom parameters for the
sendMessage
call via the Producer'spublish
method
0.9.0
0.8.0
-
NEW: it is now possible to set more configuration options for consumers via settings:
max_messages_per_request
,request_timeout
,polling_interval
andgc_probability
-
FIXED: removed one leftover echo debug statement
-
FIXED: the Consumer does now honour the requestTimeout and requestBatchSize parameters when the
consume()
method is called with a max amount of messages to retrieve and/or max time to run.
In version 0.7, passing non-0 values for those parameters would force the consumer to use long polling with 20 secs timeout and 10 messages batch-size per call.
0.7.0
FIXED: Issue #3 Consumer process does not allow to use a long timeout interval
It is now possible to use both a long timeout and/or a big number ofmessages to be consumed in calls to consume
.
The client will take care not to exceed in any case the AWS limits (20 secs timeout, 10 messages per call), and
keep polling as long as one of the limits is reached
0.6.0
-
FIXED: Issue #1 Memory leak when running a Consumer process
The Consumer will now trigger the php garbage collector every few iterations of themaybeStopConsumer
method.
This should avoid the known memory leaks in the AWS SDK from blowing up your server.
As is tradition in php, the frequency with which the garbage collection is triggered is configured via a percentage setting. -
FIXED: Issue #2 consume() method does not respect the $amount parameter and returns immediately if there are no messages
The Consumer did not wait to receive 10 messages whenconsumer(10, 0)
was called and there were fewer than 10 messages in the queue.