Hello Guys,
I am getting this issue "This messaging entity has already been closed, aborted, or disposed."
Here is the scenario is, I am trying to process the Dead Letter Queue messages with Azure Functions.
Snippet here
deadLetterClient.OnMessage(msg =>
{
if (msg != null)
{
int retryCount = 0;
string domainObjectID = string.Empty;
domainObjectID = msg.GetBody();
try
{
DateTime oTime = Convert.ToDateTime("ds");
msg.Complete();
}
catch (Exception error)
{
-- This is the error throwing some time.
-- Error: This messaging entity has already been closed, aborted, or disposed
msg.Abandon(new Dictionary<string, object> { { "RetryCount", retryCount.ToString() } });
}
}
});
deadLetterClient.Close();

In this secanrio also throwing error like "Operation is not valid due to the current state of the object".
public static void Run(BrokeredMessage myQueueItem, TraceWriter log)
{
      string domainObjectID = string.Empty;
      //domainObjectID = myQueueItem.GetBody<string>();
      var bodyStream = myQueueItem.GetBody<Stream>();
      var sr = new StreamReader(bodyStream);
      var jsonText = sr.ReadToEnd();
      log.Info("C# ServiceBus queue trigger function processed message:" + jsonText);
      try
      {          
            var deadLetterqueuePath = QueueClient.FormatDeadLetterPath(QueueClient.CreateFromConnectionString(connectionString, mqCustomer).Path);
            var deadLetterClient = QueueClient.CreateFromConnectionString(connectionString, deadLetterqueuePath, ReceiveMode.PeekLock);
            deadLetterClient.Send(myQueueItem);
    }
      catch
      {
            log.Info("Exception");
      }
      finally
      {
            //myQueueItem.Abandon();
            //myQueueItem.DeadLetter();
      }
}

Advance thanks for suggestions.

Thanks

San

I'm getting QuotaExceededException s with the info...

"Put token failed. status-code: 403, status-description: The maximum number of '1000' tokens per connection has been reached."

It's not entirely clear to me which quota I've exceeded. Any clues as to why I might be getting these exceptions? Thanks.

Posting a message to EventHubs from JavaScript in Firefox results in an "element not found" error.

The reason for this looks to be a bug in Firefox as described here: https://bugzilla.mozilla.org/show_bug.cgi?id=884693

It seems that Firefox is not able to handle an empty response which has a Content-Type header that contains "application/xml; charset=utf-8". Firefox tries to parse parse the empty response as an XML document but cannot find the root element (hence the element not found error).

I know this is a bug in Firefox as other browsers handle this case correctly, but should the response type really be "application/xml". If the response is empty wouldn't it make more sense to set the Content-Type to "text/plain" instead?

I'm working with this code for receiving messages from a queue:

function startReceiver(){
    serviceBusService.getQueue(configurations.queueForRequest, function(err, queue){
	if(!err){
	    var length = queue.CountDetails['d2p1:ActiveMessageCount'];
	    if(length > 0) {		
serviceBusService.receiveQueueMessage(configurations.queueForRequest, {isPeekLock:true}, function(error, lockedMessage){HandleMessage(error, lockedMessage)});
		return;
	      }
	}
	else{
	    console.log('Can not get queue');
	}
	setTimeout(startReceiver, 3000);//if err or there are no messages then call this method later
    });
}

function handleMessage(err, msg){

    var result;
    if (!err){
	serviceBusService.deleteMessage(msg, function(deleteError){
	    if(deleteError) {
		console.log('Can not delete a message');
	    }
	    else{
		console.log('Msg has been deleted');
	    }
	});
	try{
            result = GetResult(msg.body)
	}
	catch (er){
	    result = GetResultWhenExp();
	}
	finally{
	    sendMessage(result); //send a response
	    startReceiver(); //repeat a receiver loop
	}

    }//!error
    else{console.log('Error occured: '+err);
	 setTimeout(startReceiver, 3000); //repeat a receiver loop later
	}
}

The issue is I can receive a message when handleMessage() is running the first time only. Further startReceiver() can get the correct count of active messages, but handleMessage() gets undefined msg as argument always (i.e. serviceBusService.receiveQueueMessage() fails, err is "No messages to receive").

Using C# library with its standard fucnctions for receiving messages it works great.

What's wrong here? Please help

We have Service Bus newly installed in our enviornment. We do have errors below where we see SQL connection timed out and it's intermittent. When we check on the SQL server, we don't see any failover or errors.

.NET 4.6.2 and TLS 1.0 is installed & enabled on both Service bus and SQL.

Anyone had a similar issue ?

TrackingId:6851d220-9a45-47ed-aa0e-af65883a1999_BAE-MAS-0031, SubsystemId: NoSystemTracker. A SQL exception was caught. Command =[dbo].[PingDatabase], error number =-2,procedure=, server = RSBDB.domain.local\I1, databasename = RSBMessageContainer01, error = error number =-2, error state =0, error class =11, error message = Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  This failure occured while attempting toconnectto the Principle server.  The duration spent while attempting toconnectto this server was -[Pre-Login] initialization=23536; handshake=29996;,procedure=, line number =0
System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  This failure occured while attempting toconnectto the Principle server.  The duration spent while attempting toconnectto this server was -[Pre-Login] initialization=23536; handshake=29996;---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.Cloud.ServiceBus.Common.Sql.SqlCommandAsyncResult.<GetAsyncSteps>d__5.MoveNext()
ClientConnectionId:d58f3d93-e749-4534-af8a-82884d7faaa6
Error Number:-2,State:0,Class:11

we were testing in our test ServiceBus to add in the failover DB instance in the Service Bus connection string. After successfully following the steps below, we encounter the error "Security token service finished processing a request with failure" in events logs almost every minute.

I have a case with Microsoft for 3 weeks and they seem unable to find out the root cause. Would anyone here seen such similar token service error ?

Why would the connection string is going to a local host -> https://localhost:9355/ServiceBusDefaultNamespace/$STS/OAuth/

Steps to add in DB failover string:

1. Execute “SB-GetFarm” cmdlet, to collect information about your current configuration: Certificates thumbprint, connection string, RunAsAccount , MessageBrokerPort , etc. You will need that info on step 3.
2.      Remove all nodes from the Service Bus Farm
3.      On one of the farm nodes, Restore the SBFarm using the new Connection string. As an example, let’s imagine that we need to modify SB connection string to add “Failover Partner” attribute. The cmdlet would be like below:

Restore-SBFarm -FarmCertificateThumbprint F91C37410FBE53B92E1B24FAC7A0D82EA4391B81 -GatewayDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False” -SBFarmDBConnectionString “Data Source=<SQL Server>;Failover Partner= Mirroring Server>;Initial Catalog=SbManagementDBNew;Integrated Security=True;Encrypt=False” -EncryptionCertificateThumbprint  91C37410FBE53B92E1B24FAC7A0D82EA4391B81 -RunAsAccount <YourAccount> -MessageBrokerPort <MessageBrokerPort> -HttpsPort <HttpsPort> -TCPPort <TCPPort>

Note: The Restore-SBFarm cmdlet creates a new Service Bus for Windows Server farm database (SbManagementDBNew). You can delete the old Service Bus for Windows Server farm database. Once above cmdlet is executed, next two connections strings will have been changed: GatewayDBConnectionString and SBFarmDBConnectionString

4.      On all new farm nodes, run the Add-SBHost :

$secure_string_pwd = convertto-securestring “<Your Password>” -asplaintext -force

Add-SBHost -SBFarmDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SbManagementDBNew;Integrated Security=True;Encrypt=False” -RunAsPassword $secure_string_pwd -EnableFirewallRules $T

5.      Call the Stop-SBFarm cmdlet to stop all Service Bus for Windows Server services on all hosts, that’s a prerequisite for next step.
6.      Restore the message containers. This step is required to modify the connection string to the message containers. Remember that you can have more than one (For more information, see the Get-SBMessageContainer cmdlet).

Restore-SBMessageContainer -Id 1 –ContainerDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False”

7.      Call the Start-SBFarm cmdlet to start all Service Bus for Windows Server services on all hosts.

Error after update connection string for failover DB:

Security token service finished processing a request with failure. TrackingId: dff19ba2-f023-42fc-9cdd-150cd2d21f47_GCE-MAS-0021, Absolute Uri: https://localhost:9355/ServiceBusDefaultNamespace/$STS/OAuth/, Message: System.FormatException: Cannot resolve a namespace for scope: https://localhost:9355/ServiceBusDefaultNamespace.
   at Microsoft.Cloud.ServiceBus.Security.OAuthAuthenticationRequest.Parse(Message message, Int32 maxArrayLength)
   at Microsoft.Cloud.ServiceBus.Security.SecurityTokenServiceProtocolHandler.GetTokenAsyncResult.ParseAuthenticationRequest(Message requestMessage, Int32 maxArrayLength)
   at Microsoft.Cloud.ServiceBus.Security.SecurityTokenServiceProtocolHandler.GetTokenAsyncResult.<GetAsyncSteps>d__2c.MoveNext()
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()

1. Execute “SB-GetFarm” cmdlet, to collect information about your current configuration: Certificates thumbprint, connection string, RunAsAccount , MessageBrokerPort , etc. You will need that info on step 3.
2.      Remove all nodes from the Service Bus Farm
3.      On one of the farm nodes, Restore the SBFarm using the new Connection string. As an example, let’s imagine that we need to modify SB connection string to add “Failover Partner” attribute. The cmdlet would be like below:

Restore-SBFarm -FarmCertificateThumbprint F91C37410FBE53B92E1B24FAC7A0D82EA4391B81 -GatewayDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False” -SBFarmDBConnectionString “Data Source=<SQL Server>;Failover Partner= Mirroring Server>;Initial Catalog=SbManagementDBNew;Integrated Security=True;Encrypt=False” -EncryptionCertificateThumbprint  91C37410FBE53B92E1B24FAC7A0D82EA4391B81 -RunAsAccount <YourAccount> -MessageBrokerPort <MessageBrokerPort> -HttpsPort <HttpsPort> -TCPPort <TCPPort>

Note: The Restore-SBFarm cmdlet creates a new Service Bus for Windows Server farm database (SbManagementDBNew). You can delete the old Service Bus for Windows Server farm database. Once above cmdlet is executed, next two connections strings will have been changed: GatewayDBConnectionString and SBFarmDBConnectionString

4.      On all new farm nodes, run the Add-SBHost :

$secure_string_pwd = convertto-securestring “<Your Password>” -asplaintext -force

Add-SBHost -SBFarmDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SbManagementDBNew;Integrated Security=True;Encrypt=False” -RunAsPassword $secure_string_pwd -EnableFirewallRules $T

5.      Call the Stop-SBFarm cmdlet to stop all Service Bus for Windows Server services on all hosts, that’s a prerequisite for next step.
6.      Restore the message containers. This step is required to modify the connection string to the message containers. Remember that you can have more than one (For more information, see the Get-SBMessageContainer cmdlet).

Restore-SBMessageContainer -Id 1 –ContainerDBConnectionString “Data Source=<SQL Server>;Failover Partner=<SQL Mirroring Server>;Initial Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False”

7.      Call the Start-SBFarm cmdlet to start all Service Bus for Windows Server services on all hosts.

Pradebban Raja

Hi,

I am working on sending around 1000 msg/s to an Azure Event Hub with 16 partitions and 5 TU's from an Apache Storm Cluster (Java). What we have noticed is a single EventHubClient can't keep up with this throughput so we have decided to use a pool of clients, however if we create a pool of 10 clients we are running into an odd situation where the client code freezes and does not respond. Does this have something to do with the number of TCP connections we're opening?

<dependency>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-eventhubs</artifactId>
<version>0.7.8</version>
</dependency>

This is the version we're using but we have also tried 0.9.0 with no luck.

Here is an example of how we're sending, the interface for the client is just a wrapper around the EventHubClient for unit testing purposes:

We are using ServiceBus v2.7 and AccessControlExtensions v1.0

Given 2 namespaces named like this ["customxyzns", "customxyzns2"], if you call NamespaceAccessControl.GetAccessControlList() using the first, it resolves the second one and errors out.  Here is an example stack trace with namespaces updated to match.

System.Data.Services.Client.DataServiceClientException: ACS50010: Validation of Audience URI(s) 'https://customxyzns-sb.accesscontrol.windows.net/v2/mgmt/service/' failed. No match was found with allowed audience(s) 'https://customxyzns2-sb.accesscontrol.windows.net/v2/mgmt/service'.
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](System.Data.Services.Client.DataServiceContext, System.Data.Services.Client.QueryComponents)
   at System.Data.Services.Client.DataServiceQuery`1.Execute()
   at System.Data.Services.Client.DataServiceQuery`1.GetEnumerator()
   at System.Linq.Enumerable.FirstOrDefault[TSource](System.Collections.Generic.IEnumerable`1[TSource])
   at System.Data.Services.Client.DataServiceQueryProvider.ReturnSingleton[TElement](System.Linq.Expressions.Expression)
   at System.Linq.Queryable.FirstOrDefault[TSource](System.Linq.IQueryable`1[TSource])
   at Microsoft.ServiceBus.AccessControlExtensions.NamespaceAccessControl.GetLongestPrefixRelyingPartyAddress(Microsoft.ServiceBus.AccessControlExtensions.AccessControlManagement.ManagementService, System.String) in c:\DEV\Git\Stackify\ThirdParty\Microsoft.ServiceBus.AccessControlExtensions\Microsoft.ServiceBus.AccessControlExtensions\NamespaceAccessControl.cs:line 53
   at Microsoft.ServiceBus.AccessControlExtensions.NamespaceAccessControl.GetAccessControlList(System.Uri, Microsoft.ServiceBus.AccessControlExtensions.AccessControlSettings) in c:\DEV\Git\Stackify\ThirdParty\Microsoft.ServiceBus.AccessControlExtensions\Microsoft.ServiceBus.AccessControlExtensions\NamespaceAccessControl.cs:line 33
   at Stackify.Core.Services.ServiceProvider.ClientServiceNamespaceService.EnsureQueueExists(Microsoft.ServiceBus.NamespaceManager, System.String, Stackify.Core.Entities.Azure.AzureServiceNamespace, Stackify.Core.Entities.Azure.AzureServiceNamespace) in c:\build-dir\PBW-PTWB1162-BA\Common\Stackify.Core.Services\ServiceProvider\ClientServiceNamespaceService.cs:line 304
   at Stackify.Core.Services.ServiceProvider.ClientServiceNamespaceService.EnsureAgentAccess(Stackify.Core.Entities.Client.Device.ClientAgent) in c:\build-dir\PBW-PTWB1162-BA\Common\Stackify.Core.Services\ServiceProvider\ClientServiceNamespaceService.cs:line 218
   at Stackify.Core.Services.ServiceProvider.ClientServiceNamespaceService.EnsureAllAgentAccess() in c:\build-dir\PBW-PTWB1162-BA\Common\Stackify.Core.Services\ServiceProvider\ClientServiceNamespaceService.cs:line 119
   at WorkerRoleLib.GeneralTask.TaskRunner.Process(Microsoft.ServiceBus.Messaging.BrokeredMessage, System.Collections.Generic.Dictionary`2[System.String,System.String], System.Object) in c:\build-dir\PBW-PTWB1162-BA\StackifyWorkers\WorkerRoleLib\GeneralTask\TaskRunner.cs:line 331
   at Knock.Objects.Workers.MessagePumpWorker`1+<>c__DisplayClass2.<receivemessage>b__1() in c:\build-dir\PBW-PTWB1162-BA\StackifyWorkers\Knock.Objects.Workers\MessagePumpWorker.cs:line 158
   at StackifyLib.ProfileTracer.ExecInternalOperation(System.String, System.Action)
   at StackifyLib.ProfileTracer.Exec(System.Action)
   at Knock.Objects.Workers.MessagePumpWorker`1.ReceiveMessage(Microsoft.ServiceBus.Messaging.BrokeredMessage) in c:\build-dir\PBW-PTWB1162-BA\StackifyWorkers\Knock.Objects.Workers\MessagePumpWorker.cs:line 111
   at Microsoft.ServiceBus.Messaging.MessageReceivePump+SyncCallbackAsyncResult.ExecuteSyncCallback(System.Object)
   at Microsoft.ServiceBus.Common.IOThreadScheduler+ScheduledOverlapped.IOCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at Microsoft.ServiceBus.Common.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   --- End of inner exception stack trace ---
   at System.Data.Services.Client.QueryResult.Execute()
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](System.Data.Services.Client.DataServiceContext, System.Data.Services.Client.QueryComponents)</receivemessage>
Is there any insight on how to prevent this outside of changing the namespace names themselves so they aren't similar.
This seems to be an internal bug to the dlls.

I have a namespace created in the classic portal - it contains several notification hubs and by mistake also a queue.

So I just found out that it did not auto convert to a notification hub type but is a mixed type resulting in my users not getting push messages.

I followed the instructions and deleted the queue but it is still listed as a mixed type and push still does not work.

Hi,

I want to send Twitter data into Azure Search and be able to query it at a later time. The Twitter Sentiment Analysis example talks about sending feed to Event Hub which in turn acts as input to Stream Analytics. So, then I looked at the outputs of stream analytics and inputs of Azure Search - seems like this would be a feasible architecture (at least conceptually):
Twitter -> Event Hub -> Stream Analytics -> DocumentDB -> Azure Search

Does this make sense? Seems a bit round about way but wondering if this is the most optimal way?

Thanks,

Rajeev

I've written a basic Hello World application using Azure Service Bus and everything works fine.

Now, I have to test PCI compliance on the machine that will be using the Azure Service Bus.  One of the requirements for PCI compliance is to disable TLS 1.0.  Unfortunately, as soon as I do that my Hello World application fails with the following exception:

"An unhandled exception of type 'Microsoft.ServiceBus.Messaging.MessagingCommunicationException' occurred in Microsoft.ServiceBus.dll

Additional information: A call to SSPI failed, see inner exception."

To be clear, the only thing that changed between working and not working is disabling TLS 1.0 on the host machine and I am not sure what to do to correct this.

Apologies I can't find the forum for Event Hubs is there one?

Anyhow... Basically a 1 unit is limited to 1MB/s. Though on my monitoring chart I can see more than 1MB/s peaking into the hub. I don't understand why the graph shows higher than 1 MB/s?

I can see stuff coming out higher - presumably because it's compressed. 

shaun

The Event Hub programming guide mentions .NET SDK. Does it support any of the other languages mentionedhere OR is .NET the only framework supported?

I have a partitioned topic in a Service Bus Standard (East US). I keep getting gateway timeout errors while creating a subscription on it (using old and new portal).