Microsoft Azure Service Bus Delete operation java.lang.NullPointerException

Document created by aarthi_sridhar Employee on Mar 12, 2018Last modified by sheng_liao462475 on Mar 12, 2018
Version 2Show Document
  • View in full screen mode

The Microsoft Azure Service Bus operation defines what to do with messages: send to, receive from, or delete messages in a queue or topic subscription. The connector provides a Delete action — deletes messages from queues and from subscriptions to topics that are defined as the object type.



Delete action seems to expect two parameters in the connector parameter,  and the looking at the sample from the Process Library, it might not be clear sometimes how to configure the expected second parameter. It should be fine if the connector shows two parameters for delete however only one parameter is required which is the ID delete token from process properties. Delete token is auto generated. There are chances that you could receive null pointer exception.

at com.boomi.connector.util.BaseConnector.createOperation(
at com.boomi.connector.generic.GenericConnectorAction.invoke(




MSAzure Service Bus connector throws Null Pointer Exception when SAS key/Key Name is not set. The connection component for delete might be missing the SAS key configuration which is throwing a null pointer exception during initialization. The SAS key is required may be not for a query but for a delete operation. 
User guide: 






The connector might show two parameters but it is fine to setup only the delete token in the connector parameter to perform a delete operation.   

SAS key configuration setup in the connector shall resolve the issue, Enter or paste the primary or secondary key from the Shard access policy into SAS key field in connector