gocept.amqprun 0.13.0

Writing

gocept.amqprun provides a quick way to set up a handler that writes incoming messages as individual files to a given directory, using the <amqp:writefiles> ZCML directive. You need the writefiles extra to enable this directive:

<configure xmlns="http://namespaces.zope.org/zope"
           xmlns:amqp="http://namespaces.gocept.com/amqp">

  <include package="gocept.amqprun" file="meta.zcml" />

  <amqp:writefiles
    routing_key="test.data"
    queue_name="test.queue"
    directory="/path/to/output-directory"
    />
</configure>

All messages with routing key ‘test.data’ would then be written to ‘output-directory’, two files per message, one containing the body and the other containing the headers (in zope.xmlpickle format). (Note that in the buildout example above, you would need to put the writefiles directive into the [zcml] section, not the [config] section.)

You can specify multiple routing keys separated by spaces:

<amqp:writefiles
  routing_key="test.foo test.bar"
  queue_name="test.queue"
  directory="/path/to/output-directory"
  />

You can configure the way files are named with the pattern parameter, for example:

<amqp:writefiles
  routing_key="test.data"
  queue_name="test.queue"
  directory="/path/to/output-directory"
  pattern="${routing_key}/${date}/${msgid}-${unique}.xml"
  />

pattern performs a string.Template substitution. The following variables are available:

date:

The date the message arrived, formatted %Y-%m-%d

msgid:

The value of the message-id header

xfilename:

The value of the X-Filename header

routing_key:

The routing key of the message

unique:

A token that guarantees the filename will be unique in its directory

The default value for pattern is ${routing_key}-${unique}.

To support zc.buildout, {variable} is accepted as an alternative syntax to ${variable}. (zc.buildout uses ${} for its own substitutions, but unfortunately does not support escaping them.)

If pattern contains slashes, intermediate directories will be created below directory, so in the example, messages would be stored like this:

/path/to/output-directory/example.route/2011-04-07/asdf998-1234098791.xml

Just like the declare decorator, the <amqp:writefiles> ZCML directive also supports an optional arguments parameter that is passed to the AMQP queue_declare call to, e.g., support RabbitMQ mirrored queues:

<amqp:writefiles
  routing_key="test.foo test.bar"
  queue_name="test.queue"
  directory="/path/to/output-directory"
  arguments="
  x-ha-policy = all
  "
  />

Reading

You can also set up a thread to read files from a directory and publish them onto the queue, using the <amqp:readfiles> ZCML directive (the filename will be transmitted in the X-Filename header). You need the readfiles extra to enable this directive:

<configure xmlns="http://namespaces.zope.org/zope"
           xmlns:amqp="http://namespaces.gocept.com/amqp">

  <include package="gocept.amqprun" file="meta.zcml" />

  <amqp:readfiles
    directory="/path/to/input-directory"
    routing_key="test.data"
    />
</configure>

The input-directory is expected to be a Maildir, i.e. files to be read should appear in input-directory/new` which will be polled every second. After the files have been published to the given routing key, they will be moved to ``input-directory/cur.

0.13.0 (2014-04-16)

• Introduce IResponse for transaction-integrated exception handling.

• Fix timing bug: when the remote side closes the socket and at the same time a channel switch is triggered, this used to break down (since the socket is closed). We now ignore the channel switch attempt and simply wait for the reconnect, which opens a new channel anyway.

0.12.2 (2014-02-20)

• Add xfilename variable to the <amqp:writefiles pattern=""> setting.

0.12.1 (2014-02-20)

• Add safeguard that two handlers cannot bind to the same queue.

0.12 (2014-02-13)

• Include <amqp:writefiles> into the transaction handling, i.e. write to file only on commit. Previously, when an error occurred e.g. inside the MessageStored event, duplicate files would be written (each time the message was processed again on retry after the error).

0.11 (2014-01-21)

• Crash the process on filesystem errors for <amqp:readfiles>. Previously only the file reading thread crashed, but the process kept running, unaware that it now was not doing its job anymore, since the thread had died.

0.10 (2013-05-28)

• Support more than one Server in a single process.

• Introduce setup_handlers parameter for Server so clients can disable setting up handlers.

• Fix a bug in the <amqp:readfiles> transaction implementation that caused crash when aborting a transaction (#12437).

• Allow test server to take longer time for startup on slow computers.

0.9.5 (2013-04-16)

• Refactor Session / DataManager responsibilities (#9988).

0.9.4 (2012-09-07)

• Fix IDataManager implementation: abort() may be called multiple times, regardless of transaction outcome. Only release the channel refcount once.

0.9.3 (2012-09-07)

• Improve logging of IDataManager.

0.9.2 (2012-09-07)

• Improve logging of IChannelManager.acquire/release.

0.9.1 (2012-09-06)

• Fix IDataManager implementation: tpc_abort() may also be called without a prior tpc_begin() (happens for errors in savepoints, for example).

• Fix method signature of Connection.close().

0.9 (2012-08-31)

• Introduce optional integration with zope.security: handlers can declare a principal id with which an interaction will be created.

• Use a separate channel for sending messages that are not a response to a received message.

• Introduce SETTINGS_LAYER for tests relying on ISettings.

0.8 (2012-04-04)

• Fix race condition that caused messages to be acknowledged on a different channel than they were received on (#10635).

• Fix race condition that caused attempts at sending messages before the server was started properly (#10620).

0.7 (2012-03-22)

• Fix race condition between getting the current channel in the DataManager and switching the current channel in the Server (#10521).

• Make AMQP server configurable for tests (#9232).

0.6.1 (2012-02-23)

• Fixed bug in creating references header when parent message has no references (#10478).

0.6 (2012-02-22)

0.5.1 (2012-01-09)

• Bugfix to support unicode arguments for queue declaration as pika only supports bytestrings here.

• Bugfix to make arguments parameter of amqp:writefiles work (#10115).

0.5 (2011-12-08)

0.4.2 (2011-08-23)

• Add helper methods for dealing with header files to FileWriter (for #9443).

0.4.1 (2011-08-22)

• Log Message-ID.

0.4 (2011-07-25)

• The message id of outgoing messages is set.

• The correlation id of outgoing messages is set to the incoming message’s message id (if set).

• A custom header references is set to the incoming message’s reference header + the incomming message’s message id (like References in RFC5322).

• Fixed broken tests.

• Allow upper case in settings keys.

• Extend AMQP server configuration for FileStoreReader to include credentials and virtual host.

• Allow specifying multiple routing keys (#9326).

• Allow specifying a filename/path pattern (#9327).

• The FileWriter stores the headers in addition to the body (#9328).

• FileWriter sends IMessageStored event (#9335).

0.3 (2011-02-05)

• Renamed decorator from handle to declare.

• Added helper method wait_for_response to MainTestCase.

• Added an IProcessStarting event which is sent during startup.

• Added the <amqp:writefiles/> directive that sets up a handler that writes incoming messages into files.

• Added handling of <logger> directives

0.2 (2010-09-14)

• Added a decorator gocept.amqprun.handler.handle(queue_name, routing_key).

0.1 (2010-08-13)

• first release.