(Android™) Azure Service Bus - Peek-Lock Message (Non-Destructive Read)

See more Azure Service Bus Examples

Shows how to atomically retrieve and lock a message from a queue or subscription for processing. The message is guaranteed not to be delivered to other receivers (on the same queue or subscription only) during the lock duration specified in the queue/subscription description.

For more information, see https://docs.microsoft.com/en-us/rest/api/servicebus/peek-lock-message-non-destructive-read

Chilkat Android™ Downloads Android™ Java Libraries Android C/C++ Libraries

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    // Note: Requires Chilkat v9.5.0.65 or greater.

    // This requires the Chilkat API to have been previously unlocked.
    // See Global Unlock Sample for sample code.

    // Make the initial connection.
    // A single REST object, once connected, can be used for many Azure Service Bus REST API calls.
    // The auto-reconnect indicates that if the already-established HTTPS connection is closed,
    // then it will be automatically re-established as needed.
    CkRest rest = new CkRest();
    boolean bAutoReconnect = true;
    boolean success = rest.Connect("<yournamespace>.servicebus.windows.net",443,true,bAutoReconnect);
    if (success != true) {
        Log.i(TAG, rest.lastErrorText());
        return;
        }

    // ----------------------------------------------------------------------------------------------
    // The code above this comment could be placed inside a function/subroutine within the application
    // because the connection does not need to be made for every request.  Once the connection is made
    // the app may send many requests..
    // ----------------------------------------------------------------------------------------------

    // Let's load a previously computed SAS token and use it.
    // See Azure Shared Access Signature for an example to genenerate an Azure SAS token.
    CkStringBuilder sbToken = new CkStringBuilder();
    sbToken.LoadFile("qa_data/tokens/serviceBusSas.txt","utf-8");

    // Tell the REST object to use the Azure Shared Access Signature for authorization.
    sbToken.Prepend("SharedAccessSignature ");
    rest.AddHeader("Authorization",sbToken.getAsString());

    // ----------------------------------------------------------------------------------------------

    // Peek-lock a message from the subscription "feedings" in the topic "gilaMonster"
    String topicName = "gilaMonster";
    String subscriptionName = "feedings";

    // Build the path..
    CkStringBuilder sbPath = new CkStringBuilder();
    sbPath.Append("/");
    sbPath.Append(topicName);
    sbPath.Append("/subscriptions/");
    sbPath.Append(subscriptionName);
    sbPath.Append("/messages/head");

    // If peek-locking from a queue, the path would be built like this:
    CkStringBuilder sbQueuePath = new CkStringBuilder();
    sbQueuePath.Append("/");
    sbQueuePath.Append("queueName");
    sbQueuePath.Append("/messages/head");
    // This example will use the sbPath..

    // Add a timeout parameter.
    rest.AddQueryParam("timeout","20");

    // Use the POST HTTP verb to peek-lock the message.
    // Note that the only difference between the destructive Read-and-Delete and the non-destructive Peek-Lock
    // is that the HTTP verb.  (POST is for peek-lock, DELETE is fore read-and-delete.)
    CkStringBuilder sbResponseBody = new CkStringBuilder();
    success = rest.FullRequestNoBodySb("POST",sbPath.getAsString(),sbResponseBody);
    if (success != true) {
        Log.i(TAG, rest.lastErrorText());
        return;
        }

    Log.i(TAG, "Response Status Code = " + String.valueOf(rest.get_ResponseStatusCode()));

    // Check for a success response.
    // CAREFUL: This returns a 201 response instead of a 200 response.  In general, either 200 or 201 should always indicate success.
    if (rest.get_ResponseStatusCode() != 201) {
        Log.i(TAG, rest.lastRequestStartLine());
        Log.i(TAG, rest.lastRequestHeader());
        Log.i(TAG, sbResponseBody.getAsString());
        Log.i(TAG, "Failed.");
        return;
        }

    // The content of the message is returned in the HTTP response body.
    // The HTTP response headers contains extra information.  For example:
    CkJsonObject jsonBrokerProps = new CkJsonObject();
    jsonBrokerProps.Load(rest.responseHdrByName("BrokerProperties"));
    jsonBrokerProps.put_EmitCompact(false);
    Log.i(TAG, jsonBrokerProps.emit());

    // An example of the BrokerProperties JSON that is returned:

    // 	{
    // 	  "DeliveryCount": 2,
    // 	  "EnqueuedSequenceNumber": 3000003,
    // 	  "EnqueuedTimeUtc": "Wed, 07 Dec 2016 17:42:48 GMT",
    // 	  "Label": "M2",
    // 	  "LockToken": "0a13ee8a-be32-4458-89e0-5e1401caa6a0",
    // 	  "LockedUntilUtc": "Wed, 07 Dec 2016 18:13:12 GMT",
    // 	  "MessageId": "7bea513a6ddb49089e07bfbee26d85bd",
    // 	  "SequenceNumber": 3,
    // 	  "State": "Active",
    // 	  "TimeToLive": 922337203685.47754
    // 	}

    // Also the "Location" response header contains the URI of the locked message.
    // This can be used to ulock or delete the message.
    Log.i(TAG, "Location: " + rest.responseHdrByName("Location"));

    // An example of the Location URI:
    // https://chilkat.servicebus.windows.net/gilamonster/subscriptions/feedings/messages/3/0a13ee8a-be32-4458-89e0-5e1401caa6a0

    // If successful, the message is the contents of the response body.
    String message = sbResponseBody.getAsString();
    Log.i(TAG, "Received message: " + message);

    Log.i(TAG, "Success.");

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}