Persistence on one queue but not another

[mackerman]

Hi, does anyone know if it is possible to configure HornetQ to persist messages for one queue in its configuration but not another.  Looking at the documentation, and the schema, it looks like the <persistence-enabled> element is a child of the global configuration, and cannot be set at a queue/topic level.  One of our queues is for high-volume, real-time data, where if a message is not received in short order there is no point keeping it around, and we don't want the overhead of persistence.  Another queue is for low-volume billing data, where we need guarenteed delivery, so persistence would be appropriate.

If it is not possible to do this in a single configuration, can one use multiple configurations?

thanks, Mitchell

[jbertram]

You should be able to set <durable> as true or false on any destination.

Alternatively, you could make sure the producers are sending non-persistent messages.