[Messenger] Add AMQP adapter #26632

sroze · 2018-03-22T09:21:10Z

Q	A
Branch?	master
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Tests pass?	ø
License	MIT

Depends on the Messenger component [Messenger] Add a new Messenger component #24411
Add tests once we are all happy about the structure

In order to give a great DX for simple needs such as sending messages through an AMQP broker such as RabbitMq, we should ship an AMQP adapter for the Messenger component within Symfony Core. It should be as simple as this proposal. We don't need to handle more specific use-cases nor brokers as other adapters such as the enqueue adapter can also be used.

Configuring the adapter is as simple as the following configuration:

# config/packages/messenger_adapters.yaml
framework:
    messenger:
        adapter: "%env(MESSENGER_DSN)%"

With the given .env for example:

MESSENGER_DSN=amqp://guest:guest@localhost:5672/%2f/messages

Keep in mind that after having configured the adapter, developers have to route their messages to the given adapter.

# config/packages/messenger_routes.yaml
framework:
    messenger:
        routing:
producer).
            'App\Message\Command\CreateNumber': messenger.default_sender

Additionally, multiple adapters can be created and messages routed to these ones.

# config/packages/messenger_routes.yaml
framework:
    messenger:
        adapters:
            commands: "amqp://guest:guest@localhost:5672/%2f/commands"
            maintenance: "amqp://guest:guest@localhost:5672/%2f/maintenance"
        routing:
producer).
            'App\Message\Command\CreateNumber': messenger.commands_sender
            'App\Message\Command\MaintenanceSpecificCommand': messenger.maintenance_sender

nicolas-grekas · 2018-03-22T09:54:42Z

Shouldn't this be inside the Messenger component?

javiereguiluz · 2018-03-22T09:49:00Z

src/Symfony/Bridge/PhpAmqp/AmqpReceiver.php

+use Symfony\Component\Messenger\Transport\Serialization\DecoderInterface;
+
+/**
+ * Symfony Message receiver to get messages from AMQP brokers using PHP's AMQP extension.


Symfony Message -> Symfony Messenger ?

javiereguiluz · 2018-03-22T09:49:57Z

src/Symfony/Bridge/PhpAmqp/AmqpSender.php

+use Symfony\Component\Messenger\Transport\Serialization\EncoderInterface;
+
+/**
+ * Symfony Message sender to send messages to AMQP brokers using PHP's AMQP extension.


Here too: Message -> Messenger

javiereguiluz · 2018-03-22T09:50:15Z

src/Symfony/Bridge/PhpAmqp/AmqpSender.php

+    {
+        $encodedMessage = $this->messageEncoder->encode($message);
+
+        $this->connection->publish(


This should probably go in one line.

javiereguiluz · 2018-03-22T09:51:23Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+ */
+class Connection
+{
+    private $amqpConnectionCredentials;


Rename this to $amqpCredentials to be consistent with the other vars? $amqpChannel, $amqpExchange, etc.

Or maybe $connectionCredentials ? All the variables prefixed by amqp (except this one) actually contains objects coming from PHP's AMQP library.

javiereguiluz · 2018-03-22T09:54:06Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+     */
+    private $amqpQueue;
+
+    public function __construct(array $amqpConnectionCredentials, string $exchangeName, string $queueName, bool $debug = false)


Given how we use classes for everything in this component (and it's great!) what if we replace this PHP array to store credentials by a proper AMQPCredentials class?

As we are directly passing it to the \AMQPConnection object, I believe that it's better not to enforce any constraint on what can be in these "credentials". IMHO there is no point of maintaining an object mapping all the options available for the \AMQPConnection constructor coming from PHP's AMQP library.

javiereguiluz · 2018-03-22T09:55:15Z

src/Symfony/Bridge/PhpAmqp/composer.json

+    "license": "MIT",
+    "authors": [
+        {
+            "name": "Samuel Rozé",


If your surname is spelled Rozé ... you need to update the PHPdoc of all classes where you spell it as Roze 😄

Yeah... ASCII destroyed my surname ages ago. I gave up on the é so will revert to e 😛

javiereguiluz · 2018-03-22T09:56:33Z

src/Symfony/Bundle/PhpAmqpBundle/PhpAmqpBundle.php

+/**
+ * @author Samuel Roze <samuel.roze@gmail.com>
+ */
+class PhpAmqpBundle extends Bundle


Here we spell AMQP as Amqp ... which I think it's the official policy of Symfony code syntax. So, in all other classes, we should replace AMQP by Amqp -> e.g. AMQPEnvelope -> AmqpEnvelope

Unfortunately the \AMQP* classes such as AMQPEnvelope are coming from PHP's AMQP library 🤷‍♂️

You can use aliased imports ;)

sroze · 2018-03-22T10:12:07Z

Shouldn't this be inside the Messenger component?

That's a good question. I took the outside approach but it's debatable as the "inside" approach is basically the Cache component's approach.

Cons of having them inside are:

You don't want to download an AMQP client when you get the component to use it as a message bus, or when you use another adapter.
It will be harder to draw the line of what's "inside" or "outside" regarding the adapters created by the community.

The pros of having them inside:

As I foresee many other adapters (for example an "HTTP" adapter - ApiPlatform or not - in order to send/receive messages via HTTP), if we decide that this one should be outside the component, it means more maintenance "cost" for us to add more "official" ones (i.e. creating packages, recipes, bundles, etc...)

With years of having many adapters within the Cache component, what is your PoV? Was that a good choice?

nicolas-grekas · 2018-03-22T10:14:59Z

You don't want to download an AMQP client

We shouldn't care for extra files. We're talking about 500 lines here, LICENSE included.
We just need to make ext-amqp a suggestion instead.

sroze · 2018-03-22T10:25:18Z

@nicolas-grekas you are just quoting a small part of my answer here. I understand your answer to my question about Cache Component's choice is "yes, definitely".

Therefore, let's say we go with the adapter bundled inside, how would you have a similar DX than this one that we can have with another bundle?

composer req amqp
Change AMQP_DSN environment variable (if needed)
Configure the routing of your message in config/packages/framework.yaml

nicolas-grekas · 2018-03-22T10:27:20Z

@sroze we'll just ship with a default config based on e.g. PDO. Or no default config if none are available.

sroze · 2018-03-22T11:02:36Z

we'll just ship with a default config based on e.g. PDO

What do you mean? Where would you see this configuration to be tweaked by the developer? Could you give me a bullet-list example compared to what I described above as I don't get how it could be simple for the developer?

nicolas-grekas · 2018-03-22T11:06:28Z

Where would you see this configuration to be tweaked by the developer

in a recipe

theofidry · 2018-03-22T11:20:49Z

@nicolas-grekas but if you do composer req amqp and you don't have the extension installed it won't be able to pick it up if those things are handled by the recipe whereas if it's outside you can put the extension as a requirement upfront.

xabbuh · 2018-03-22T11:34:02Z

@theofidry There can be a pack that also defines the dependeny on the amqp extension and we can then provide a recipe for the pack.

theofidry · 2018-03-22T11:44:04Z

But shouldn’t that bridge be also usable from outside of Symfony?

…

On Thu 22 Mar 2018 at 11:34, Christian Flothmann ***@***.***> wrote: @theofidry <https://github.com/theofidry> There can be a pack that also defines the dependeny on the amqp extension and we can then provide a recipe for the pack. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE76gfvSvIYfsAOSfGbI2pQ5FTx2wcKXks5tg4w6gaJpZM4S2sxP> .

sroze · 2018-03-22T11:46:47Z

But shouldn’t that bridge be also usable from outside of Symfony?

Well, there is no point of this adapter/bridge without the Messenger component anyway, isn't it? 😉

Nyholm · 2018-03-22T11:48:38Z

Shouldn't this be inside the Messenger component?

I would say no.

If it is inside the Messanger component, then why shouldn't we also add a php-amqplib/php-amqplib adapter? And a php-enqueue adapter? And an adapter for Kafka, Redis etc etc etc. Where do you draw the line?

One could argue that we should just have the one, but I think that the AMQP adapter is just a implementation detail (not a core thing) of the component.

nicolas-grekas · 2018-03-22T11:57:14Z

This needs to be in the Messenger component IMHO. We don't ship components that require third-party code, because then we cannot enforce our policies for BC/FC, deprecations, etc.

Where do you draw the line?

Exactly where our policies need to be enforced so that we can provide the Symfony guarantees.

Nyholm · 2018-03-22T12:00:25Z

We don't ship components that require third-party code

That is the thing. The messanger component does not need any AMQP library/extension. That is just an extra feature.

@makasim 👍

nicolas-grekas · 2018-03-22T12:02:02Z

@Nyholm ??? yes it needs a store, as soon as you need async.

sroze · 2018-03-22T12:07:42Z

Where do you draw the line?

@Nyholm That question is valid regardless of having adapters inside or outside the component: which ones becomes a symfony/ package and which ones are living somewhere else... I agree with @nicolas-grekas here, it's a must-have in terms of DX for most of the users. And does not cost anything (except few KBs) for others :)

Let developers to choose what they want to use

@makasim that's exactly what we are doing by exposing all these extension points (i.e. the Sender/Receiver and Encoder/Decoder interfaces). That's exactly why I've built the Enqueue adapter. The point here is what should be shipped directly within Symfony Core.

Nyholm · 2018-03-22T12:11:30Z

yes it needs a store, as soon as you need async.

Yes, but it is not obvious that you need async.

I would still like to see that the adapters is not part of the component package. But if we really feel we want to ship some: lets do php-enqueue and ext-amqp as our "adapters shipped with the component"

dunglas · 2018-03-22T12:34:57Z

I'm for storing adapters directly in the component.
It's easier to discover for the end user, and it's consistent with what is done for Cache and PropertyInfo (we provide an adapter for phpDocumentator's ReflectionDocBlock, and it's inside the component directly).

Nyholm · 2018-03-22T12:42:17Z

But what about all external dependencies that different adapters use? We would still need ask the user to download third party code.

throw new \Exception('To use the XXX adapter you need to download XXX/library');

dunglas · 2018-03-22T12:41:17Z

src/Symfony/Bridge/PhpAmqp/AmqpReceiver.php

+    public function receive(): iterable
+    {
+        while (true) {
+            if (null === ($message = $this->connection->waitAndGet())) {


Useless parenthesis.

dunglas · 2018-03-22T12:43:04Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+        $this->debug = $debug;
+    }
+
+    public static function fromDsn(string $dsn, bool $debug = false)


dunglas · 2018-03-22T12:43:26Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+
+    public static function fromDsn(string $dsn, bool $debug = false)
+    {
+        if (false === ($parsedUrl = parse_url($dsn))) {


Useless parenthesis

dunglas · 2018-03-22T12:44:51Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+            throw new \InvalidArgumentException(sprintf('The given AMQP DSN "%s" is invalid.', $dsn));
+        }
+
+        $pathParts = explode(trim($parsedUrl['path'] ?? '', '/'), '/');


What about $pathParts = isset($parsedUrl['path'])) ? explode(trim($parsedUrl['path'], '/'), '/') : [];?

Don't mind to change so did it 😉

dunglas · 2018-03-22T12:45:55Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+        }
+
+        $this->exchange()->publish($body, null, AMQP_NOPARAM, array(
+            'headers' => $headers,


Can be inlined

dunglas · 2018-03-22T12:46:25Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+        $message = null;
+
+        try {
+            $this->queue()->consume(function (\AMQPEnvelope $envelope) use (&$message) {


function (\AMQPEnvelope $envelope) use (&$message): bool

dunglas · 2018-03-22T12:46:36Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+                return false;
+            });
+        } catch (\AMQPQueueException $e) {
+            if (404 == $e->getCode()) {


dunglas · 2018-03-22T12:47:18Z

src/Symfony/Bridge/PhpAmqp/Connection.php

+
+    private function channel(): \AMQPChannel
+    {
+        if (null === $this->amqpChannel) {


What about a guard clause instead to reduce the complexity?

if (null !== $this->amqpChannel) { return $this->amqpChannel; } $connection = new \AMQPConnection($this->amqpConnectionCredentials); if (false === $connection->connect()) { throw new \AMQPException('Could not connect to the AMQP server. Please verify the provided DSN.'); } return $this->amqpChannel = new \AMQPChannel($connection);

I would do the same for all other methods in this file.

dunglas · 2018-03-22T12:51:09Z

src/Symfony/Bundle/PhpAmqpBundle/DependencyInjection/Configuration.php

+    /**
+     * {@inheritdoc}
+     */
+    public function getConfigTreeBuilder()


: TreeBuilder?

dunglas · 2018-03-22T12:52:28Z

src/Symfony/Bundle/PhpAmqpBundle/DependencyInjection/PhpAmqpExtension.php

+            $container->getParameter('kernel.debug'),
+        )))->setFactory(array(Connection::class, 'fromDsn'));
+
+        $container->setDefinitions(array(


I suggest to call $container->register several times instead for readability.

joelwurtz · 2018-03-22T12:53:55Z

The main problem with the approach of storing adapter in the component is for versioning purpose, let's imagine there is a new version of the amqp extension with a different API. When you update this adapter it will become a problem, sure you can add a conflict version, but you may have other libs depending on the old extension (and not updated).

Also people would not be able to profit for new features / bug fix unless they update their extension (although it's an implementation detail)

However having an adapter outside this component you would just need to create a new one with the new API and maintain the old one in parallelel (or create some deprecation policy to allow people upgrading to the new one)

dunglas · 2018-03-22T15:47:40Z

Versionning isn’t an issue. We can create bridges for both versions of the dep (we did that for Reflection DocBlock in Prophecy for instance).

Regarding extra packages, we’ll add adapters dependencies in the suggest section. And we can always create metapackages such as message-amp for DX of suggesting isn’t enough.

sroze · 2018-03-22T19:43:25Z

I agree that the best option is actually to package the AMQP adapter within the Messenger component. This will simplify the maintenance and ease the discoverability of the adapter. In order to integrate it properly with Symfony it, therefore, requires works on the messenger section of the FrameworkBundle, like the following:

framework:
    messenger:
        adapters:
            default: "amqp://guest:guest@localhost:5672/%2f/messages"

@fabpot to prevent conflicts, it seems like the best idea is to wait for the Messenger PR to be merged within master :)

Nyholm

I've reviewed the changes and I like it. I've not tested it and played around with the implementation yet.

Nyholm · 2018-04-04T08:37:44Z

src/Symfony/Bundle/FrameworkBundle/Resources/config/schema/symfony-1.0.xsd

+        <xsd:sequence>
+            <xsd:element name="option" type="messenger_adapter_option" minOccurs="0" maxOccurs="unbounded" />
+        </xsd:sequence>
+


Remove blank line

Nyholm · 2018-04-04T08:40:02Z

src/Symfony/Component/Messenger/Adapter/Factory/AdapterInterface.php

+use Symfony\Component\Messenger\Transport\SenderInterface;
+
+/**
+ * @author Samuel Roze <samuel.roze@gmail.com>


I would really like a line or two on this interface to explain what it does.

ogizanagi · 2018-04-04T16:40:15Z

src/Symfony/Bundle/FrameworkBundle/DependencyInjection/Configuration.php

@@ -970,12 +970,21 @@ private function addMessengerSection(ArrayNodeDefinition $rootNode)
                ->arrayNode('messenger')
                    ->info('Messenger configuration')
                    ->{!class_exists(FullStack::class) && class_exists(MessageBusInterface::class) ? 'canBeDisabled' : 'canBeEnabled'}()
+                    ->validate()
+                        ->ifTrue(function ($v) { return isset($v['adapter']) && isset($v['adapters']); })
+                        ->thenInvalid('"adapter" and "adapters" cannot be used together.')


Did you removed an adapter key at some point? This seems useless now.

DX-wise, the adapter key would have been interesting to me though, as projects with multiple adapters might not be so common. So the Messenger recipe would have been:

parameters: env(MESSENGER_ADAPTER_DSN): null framework: messenger: # Provide the "MESSENGER_ADAPTER_DSN" env var value to enable a "default" adapter. adapter: "%env(MESSENGER_ADAPTER_DSN)%"

and just have to uncomment the var in .env. (We should allow null as framework.adapter value and consider there is no adapter).

True, I removed it. It appears that DX-wise, it does not change anything actually thanks to the recipe (i.e. framework.messenger.adapters.default configured by default - maybe commented). And if we put framework.messenger.adapter in the recipe, it's less obvious they can use multiple adapters.

ogizanagi · 2018-04-04T17:11:00Z

src/Symfony/Bundle/FrameworkBundle/Tests/DependencyInjection/Fixtures/yml/messenger_adapter.yml

+            customised:
+                dsn: 'amqp://localhost/%2f/messages?exchange_name=exchange_name'
+                options:
+                    queue_name: Queue


Missing newline

ogizanagi · 2018-04-04T17:21:00Z

src/Symfony/Bundle/FrameworkBundle/Tests/DependencyInjection/FrameworkExtensionTest.php

@@ -543,6 +544,33 @@ public function testMessengerValidationDisabled()
        $this->assertFalse($container->hasDefinition('messenger.middleware.validator'));
    }

+    public function testMessengerAdapter()
+    {
+        $container = $this->createContainerFromFile('messenger_adapter');


So, the messenger key can be enabled even if the component is not part of the composer.json dev reqs?
I suspect the FrameworkExtension is missing something like:

if (!class_exists(MessageBusInterface::class)) { throw new LogicException('Messenger cannot be enabled as the Messenger component is not installed.'); }

😄

Good catch, will handle that in another PR 😉

You fixed it in #26816, thank you :)

ogizanagi · 2018-04-04T17:22:39Z

src/Symfony/Bundle/FrameworkBundle/Tests/DependencyInjection/FrameworkExtensionTest.php

+        $senderArguments = $container->getDefinition('messenger.customised_sender')->getArguments();
+
+        $this->assertEquals(array(new Reference('messenger.adapter_factory'), 'createSender'), $senderFactory);
+        $this->assertEquals(2, count($senderArguments));


assertCount ? (same for other occurrences)

ogizanagi · 2018-04-04T17:24:59Z

src/Symfony/Bundle/FrameworkBundle/DependencyInjection/FrameworkExtension.php

@@ -1470,6 +1470,24 @@ private function registerMessengerConfiguration(array $config, ContainerBuilder
        } else {
            $container->removeDefinition('messenger.middleware.validator');
        }
+
+        foreach ($config['adapters'] as $name => $adapter) {
+            $container->setDefinition('messenger.'.$name.'_sender', (new Definition(SenderInterface::class))->setFactory(array(


Usually, it's 'messenger.sender.'.$name rather than 'messenger.'.$name.'_sender'. Same for receivers.

Happy to change but... What do you mean by "usually"? :)

I mean that's AFAIK what most service factories will choose as format for their ids (see security listeners concrete instances or user_checkers named after firewalls, workflows, Monolog handlers, ...) but also what we do anyway to gather similar services under an identifiable "namespaces".

Fair enough. Changed.

ogizanagi · 2018-04-04T17:41:03Z

src/Symfony/Component/Messenger/Adapter/Factory/AdapterFactoryInterface.php

+
+    public function createSender(string $dsn, array $options): SenderInterface;
+
+    public function supports(string $dsn, array $options): bool;


Just asking: it's admitted any adapter factory will provide both sender and receiver factories?
What if I only need a sender? I'd rather create the sender service myself and tag it?

Tbh, you can skip the AdapterFactoryInterface if you don't want the developers to use the DSN to create your senders/receivers. Registering and tagging the sender/receiver still works. Also, you could create a NullSender or NullAdapter.

ogizanagi · 2018-04-04T17:46:40Z

src/Symfony/Component/Messenger/Adapter/PhpAmqp/AmqpFactory.php

+ * file that was distributed with this source code.
+ */
+
+namespace Symfony\Component\Messenger\Adapter\PhpAmqp;


👍 for AmqpExt

ogizanagi · 2018-04-04T18:09:59Z

src/Symfony/Component/Messenger/Adapter/PhpAmqp/AmqpReceiver.php

+                throw $e;
+            }
+
+            if (function_exists('pcntl_signal_dispatch')) {


Not in a finally? Not needed?

That's a good shot, this could be in the finally. I don't know if it's really needed but doesn't cost :)

davidbarratt · 2018-04-08T03:36:16Z

Any chance on this getting merged soon? Thanks! :)

davidbarratt · 2018-04-08T15:29:47Z

src/Symfony/Component/Messenger/Adapter/AmqpExt/AmqpFactory.php

+
+    public function createQueue(\AMQPChannel $channel): \AMQPQueue
+    {
+        return new \AMQPQueue($channel);


I think these \AMQP classes are only in the amqp pecl extension? if so, it should be a requirement in composer.json
https://getcomposer.org/doc/04-schema.md#package-links
something like

"ext-amqp": "^1.0.0"

unless there's an alternative?

That's correct. We can't add the requirement in this composer.json file as it's not a requirement for the entire component, but for its AMQP adapter only. Though you are right in pointing that we don't handle properly the case when the extension is not installed: we can add a nice exception message when trying to create the adapter while the extension does not exist.

good to know! I'm not going to hold up the train for that, but probably a good idea to add at some point.

This PR was squashed before being merged into the 4.1-dev branch (closes #26632). Discussion ---------- [Messenger] Add AMQP adapter | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | ø | License | MIT - [x] Depends on the Messenger component #24411 - [x] Add tests once we are all happy about the structure --- In order to give a great DX for simple needs such as sending messages through an AMQP broker such as RabbitMq, we should ship an AMQP adapter for the Messenger component within Symfony Core. It should be as simple as this proposal. We don't need to handle more specific use-cases nor brokers as other adapters such as the [enqueue adapter](https://github.com/sroze/enqueue-bridge) can also be used. Configuring the adapter is as simple as the following configuration: ```yaml # config/packages/messenger_adapters.yaml framework: messenger: adapter: "%env(MESSENGER_DSN)%" ``` With the given `.env` for example: ``` MESSENGER_DSN=amqp://guest:guest@localhost:5672/%2f/messages ``` Keep in mind that after having configured the adapter, developers have to route their messages to the given adapter. ```yaml # config/packages/messenger_routes.yaml framework: messenger: routing: producer). 'App\Message\Command\CreateNumber': messenger.default_sender ``` --- Additionally, multiple adapters can be created and messages routed to these ones. ```yaml # config/packages/messenger_routes.yaml framework: messenger: adapters: commands: "amqp://guest:guest@localhost:5672/%2f/commands" maintenance: "amqp://guest:guest@localhost:5672/%2f/maintenance" routing: producer). 'App\Message\Command\CreateNumber': messenger.commands_sender 'App\Message\Command\MaintenanceSpecificCommand': messenger.maintenance_sender ``` Commits ------- 798c230 [Messenger] Add AMQP adapter

sroze force-pushed the add-amqp-adapter branch from dfd8442 to eede0ed Compare March 22, 2018 09:21

sroze changed the title ~~[AMQP] Add AMQP adapter for Message component~~ [AMQP] Add AMQP adapter for Messenger component Mar 22, 2018

javiereguiluz reviewed Mar 22, 2018

View reviewed changes

carsonbot added the Status: Needs Work label Mar 22, 2018

dunglas previously requested changes Mar 22, 2018

View reviewed changes

nicolas-grekas added this to the 4.1 milestone Mar 22, 2018

chalasr added Feature Messenger labels Mar 23, 2018

sroze force-pushed the add-amqp-adapter branch 2 times, most recently from 7fe4a37 to 8a8c32a Compare April 4, 2018 07:51

soyuka approved these changes Apr 4, 2018

View reviewed changes

Nyholm approved these changes Apr 4, 2018

View reviewed changes

sroze force-pushed the add-amqp-adapter branch from 487b763 to d6c046a Compare April 4, 2018 10:18

ogizanagi reviewed Apr 4, 2018

View reviewed changes

sroze force-pushed the add-amqp-adapter branch from 47e2a1d to d9bf597 Compare April 5, 2018 07:46

sroze force-pushed the add-amqp-adapter branch 4 times, most recently from 5a90272 to 8dc5162 Compare April 8, 2018 10:24

carsonbot added Status: Needs Work and removed Status: Reviewed labels Apr 8, 2018

davidbarratt suggested changes Apr 8, 2018

View reviewed changes

dunglas approved these changes Apr 8, 2018

View reviewed changes

carsonbot added Status: Reviewed and removed Status: Needs Work labels Apr 8, 2018

davidbarratt approved these changes Apr 8, 2018

View reviewed changes

ogizanagi approved these changes Apr 8, 2018

View reviewed changes

sroze mentioned this pull request Apr 12, 2018

Symfony 4.1 Messenger component: Unrecognized option "adapters" under "framework.messenger" #26897

Closed

[Messenger] Add AMQP adapter

798c230

sroze force-pushed the add-amqp-adapter branch from 8dc5162 to 798c230 Compare April 12, 2018 08:17

sroze merged commit 798c230 into symfony:master Apr 12, 2018

javiereguiluz mentioned this pull request Apr 20, 2018

[Messenger] Added a AMQP adapter symfony/symfony-docs#9633

Closed

fabpot mentioned this pull request May 7, 2018

Release v4.1.0-BETA1 #27181

Merged

makasim mentioned this pull request Feb 21, 2019

[Messenger] Consumers not showing in RabbitMQ admin?! #30259

Closed

symfony deleted a comment from sroze Mar 17, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Messenger] Add AMQP adapter #26632

[Messenger] Add AMQP adapter #26632


		public function createSender(string $dsn, array $options): SenderInterface;

		public function supports(string $dsn, array $options): bool;

[Messenger] Add AMQP adapter #26632

[Messenger] Add AMQP adapter #26632

Conversation

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment