windows - Evoke a nack in publisher confirm mode -
what possible reasons nack occur in publisher confirm mode, , can nack reliably produced testing, short of pulling cable disk or other hardware-based actions?
e.g. sending non-existing exchange not lead nack. leads channel close, in non-confirm mode.
btw rabbit cluster running on windows boxes, might matter, file system works quite differently in unix world.
one way generate nacks to
- create virtual hard disk
- configure environment variable
rabbitmq_mnesia_base
point folder on drive - reinstall rabbitmq service changed mnesia base dir picked up
- restart service
- take virtual hard disk offline while enqueueing messages
a test confirmed that result in nack.
Comments
Post a Comment