> Next point is that you say you don't acknowledge and you expect a
> redelivery of that message. If you want to force that programmatically,
> e.g. if you catch a DBMS exception, then use session.recover() in that
> case. Same effect is when you close the session. Then all previously
> delivered and unacknowledged messages are being redelivered the next
> time you start a consumer on that specific destination. That works only
> for durable subscribers and queues, not for non-durable subscribers.
A nack() method would be more obvious to me.
but, as long it works with session.recover...
/Jon
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
