Connecting different Yii2 apps to the same queue

What steps will reproduce the problem?

On the producer:

        'queue' => [
            'class' => \yii\queue\db\Queue::class,
            'mutex' => \yii\mutex\PgsqlMutex::class,
            'strictJobType' => false,
            'serializer' => \yii\queue\serializers\JsonSerializer::class,
        ],

On the consumer:

        'queue' => [
            'class' => \yii\queue\db\Queue::class,
            'mutex' => \yii\mutex\PgsqlMutex::class,
            'strictJobType' => false,
            'serializer' => \yii\queue\serializers\JsonSerializer::class,
            'on beforeExec' => function ($ev) {
                print_r($ev);
                $ev->handled = true;
            },
        ],

Then, in the producer:

\Yii::$app->queue->push(['foobar' => 12345]);

What's expected?

Unserialized job data easily accessible somehow to the consumer.

What do you get instead?

Impossible to get direct access to the unserialized job data.

Looking into unserializeMessage() (see below) we see that the unserialized job is returned only if it is a JobInterface object, which obviously it is not (i.e. it is a PHP array just unserialized from a JSON string).

https://github.com/yiisoft/yii2-queue/blob/ee28f5725ee687f2cd1ef35b8662962d51cf37e0/src/Queue.php#L265-L281

The only way I could manage to access the data is to get the (serialized) JSON string using $ev->error->getSerialized(), and then decode it. That does not look right to me.

Not sure of it is a bug, or design decision. However, this issue makes it very difficult to (ironically) two Yii2 apps that do not share the same codebase to communicate.

Additional info

• As you can see from the examples, I am using Postgres+DB driver, but I guess this an issue common to all drivers.

Start with src/Queue.php around unserializeMessage(), using the linked lines and the producer and consumer configurations in the issue. Reproduce the DB queue flow with the JSON serializer and inspect the beforeExec event. Done means the consumer can access the unserialized array directly when the producer and consumer do not share job classes, with behavior covered by an appropriate regression test.