Thanks to visit codestin.com
Credit goes to github.com

Skip to content

warning about using swiftmail with file spool and lazy loading #7104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

warning about using swiftmail with file spool and lazy loading #7104

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c0d84b9
add warning about the limitation on using swiftmail with file spool a…
nykopol Oct 31, 2016
88c5eed
more precision on class name, and lazy service
nykopol Oct 31, 2016
d608213
Fixed minor syntax issues and typos
javiereguiluz Nov 2, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions email/spool.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,3 +141,21 @@ You can also set the time limit in seconds:
Of course you will not want to run this manually in reality. Instead, the
console command should be triggered by a cron job or scheduled task and run
at a regular interval.

.. caution::

When you create a message with SwiftMailer, it generates a ``Swift_Message``
class. If the ``swiftmailer`` service is lazy loaded, it generates instead a
proxy class named ``Swift_Message_<someRandomCharacters>``.

If you use the memory spool, this change is transparent and has no impact.
But when using the filesystem spool, the message class is serialized in
a file with the randomized class name. The problem is that this random
class name changes on every cache clear. So if you send a mail and then you
clear the cache, the message will not be unserializable.

On the next execution of ``swiftmailer:spool:send`` an error will raise because
the class ``Swift_Message_<someRandomCharacters>`` doesn't exist (anymore).

The solutions are either to use the memory spool or to load the
``swiftmailer`` service without ``lazy`` option (see :doc:`/service_container/lazy_services`).