rabbitmq-tests/src/test/java/com/datastax/oss/starlight/rabbitmqtests/javaclient/functional/Confirm.java
@Test
  public void queueDelete() throws IOException, InterruptedException, TimeoutException {
    publishN("", "confirm-test-noconsumer", true, false);

    channel.queueDelete("confirm-test-noconsumer");

    channel.waitForConfirmsOrDie(60000);
  }
/* For testQueueDelete and testQueuePurge to be
   * relevant, the msg_store must not write the messages to disk
   * (thus causing a confirm).  I'd manually comment out the line in
   * internal_sync that notifies the clients. */
For testQueueDelete and testQueuePurge to be
relevant, the msg_store must not write the messages to disk
(thus causing a confirm).  I'd manually comment out the line in
internal_sync that notifies the clients.
For testQueueDelete and testQueuePurge to be relevant the msg_store must not write the messages to disk ( thus causing a confirm ) . I ' d manually comment out the line in internal_sync that notifies the clients .
@Test
  public void queueDelete() throws IOException, InterruptedException, TimeoutException {
    publishN("", "confirm-test-noconsumer", true, false);
    channel.queueDelete("confirm-test-noconsumer");
    channel.waitForConfirmsOrDie(60000);
  }
@ Test public void queueDelete ( ) throws IOException , InterruptedException , TimeoutException { publishN ( "" , "confirm-test-noconsumer" , true , false ) ; channel . queueDelete ( "confirm-test-noconsumer" ) ; channel . waitForConfirmsOrDie ( 60000 ) ; }
For testQueueDelete and testQueuePurge to be
 relevant, the msg_store must not write the messages to disk
 (thus causing a confirm).
For testQueueDelete and testQueuePurge to be relevant the msg_store must not write the messages to disk ( thus causing a confirm ) .