Quantcast
Channel: Service Bus forum
Viewing all 1916 articles
Browse latest View live

Java: Azure Service Bus Queue Receiving messsages with sessions

$
0
0

Hi, 
I posted a question on StackOverflow but no one answered so I'm trying here too 😊

(Link: stackOverflow: https://stackoverflow.com/questions/59213314/java-azure-service-bus-queue-receiving-messsages-with-sessions)

I'm writing code in java (using Azure SDK for Java), I have a Service bus queue that contains sessionful messages. I want to receive those messages and process them to another place.

I make a connection to the Queue by using QueueClient, and then I use registerSessionHandler to process through the messages (code below).

The problem is that whenever a message is received, I can print all details about it including the content, but it is printed 10 times and after each time it prints an Exception. (printing 10 times: I understand that this is because there is a 10 times retry policy before it throws the message to the Dead letter queue and goes to the next message.)

The Exception says

> USERCALLBACK-Receiver not created.Registering a MessageHandler creates a receiver.

But I'm sure that the SessionHandler does the same thing as MessageHandler but includes support for sessions, so it should create a receiver since it receives messages. I have tried to use MessageHandler but it won't even work and stops the whole program because it doesn't support sessionful messages, and the ones I receive have sessions.

My problem is understanding what the Exception wants me to do, and how can I fix the code so it won't give me any exceptions? Does anyone have suggestions on how to improve the code? or other methods that do the same thing?

QueueClient qc =newQueueClient(newConnectionStringBuilder(connectionString),ReceiveMode.PEEKLOCK);

qc.registerSessionHandler(newISessionHandler(){@OverridepublicCompletableFuture<Void> onMessageAsync(IMessageSession messageSession,IMessage message){System.out.printf("\nMessage received: "+"\n --> MessageId = %s "+"\n --> SessionId = %s"+"\n --> Content Type = %s"+"\n --> Content = \n\t\t %s",
                            message.getMessageId(),
                            messageSession.getSessionId(),
                            message.getContentType(),
                            getMessageContent(message));return qc.completeAsync(message.getLockToken());}@OverridepublicCompletableFuture<Void>OnCloseSessionAsync(IMessageSession iMessageSession){returnCompletableFuture.completedFuture(null);}@Overridepublicvoid notifyException(Throwable throwable,ExceptionPhase exceptionPhase){System.out.println("\n Exception "+ exceptionPhase +"-"+ throwable.getMessage());}},newSessionHandlerOptions(1,true,Duration.ofMinutes(1)),Executors.newSingleThreadExecutor());

Message being received by multiple queues

$
0
0

Greetings, I am trying to test my service bus saga from my development machine, which wasn't a problem until I deployed the code to the server.  I have the service bus queue name as a configuration variable, so messages of type "StartCreateUserSaga" when running on my local machine go to the "userservicelocal" queue and messages from the deployed server go to the "userservice" queue.  However, the messages are going to both queues whether they are sent from the server to the "userservice" queue or from my local machine to the "userservicelocal" queue.  Since both queues have different saga storage (local postgres vs. server postgres) this causes a mess, aside from the inability to guarantee that my local machine will process it so I can debug.

I am failing to see what the point is of having named queues if any queue in an Azure Service Bus instance will pick up messages of its configured type whether or not they actually are directed to the queue in question.  Unless I'm really missing something fundamental the entire point of named queues is to direct traffic to its intended consumer.

We have separate Azure Service Bus instances in separate resource groups for our different deployed environments (dev, qa, uat, prod) but not for 'local' development. Creating an instance for 'local' use would be the obvious work around but I would like to understand why ASB is behaving in this very sub-ideal fashion.  

Thanks in advance

Sending to Event Hub

$
0
0

I don't know what's wrong with this node.js code.  I don't get any error messages, but I can't see the messages in Event Hub.  I'm able to send the same payload / keys from Python to the same EventHub without issue.  Any suggestions?

const { EventHubClient } = require("@azure/event-hubs");
// Connection string - primary key of the Event Hubs namespace.
const connectionString = "Endpoint=sb://sensor-partner-eh-namespace-cfrlr.servicebus.windows.net/;SharedAccessKeyName=XXX;SharedAccessKey=XXX;";
// Name of the event hub. For example: myeventhub
const eventHubsName = "sensor-partner-eh-03";
// Open Payload File
const payload = require("./payload.json");
async function main() {
  const writeclient = EventHubClient.createFromConnectionString(connectionString, eventHubsName);
  for (let i = 0; i < 100; i++) {
    var eventData = payload;
    console.log(JSON.stringify(eventData,null,4));
    await writeclient.send(eventData,0);
  }
  await writeclient.close();
}
main().catch(err => {
  console.log("Error occurred: ", err);
});

Error during communication with Service Bus. Check the connection information, then retry.Messages are going to Deadletter Queue or going to Deadletter queue to get deleted

$
0
0

Hello All , I am getting the error in subject line and also sometimes get
The
request was aborted: The request was canceled. Why is it happening ,sometimes the messages are being received properly.


I am calling a method XYZ in a loop till a certain count of messages .In XYz method below code is written to receive message..

Dim message AsBrokeredMessage= queueClient.Receive(TimeSpan.FromSeconds(0))

Error :Error during communication with Service Bus. Check the connection information, then retry

or

The request was aborted: Therequest was canceled.

Details:

StackTrace:atMicrosoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResultresult)
atMicrosoft.ServiceBus.Messaging.IteratorAsyncResult`1.RunSynchronously()
atMicrosoft.ServiceBus.Messaging.MessageReceiver.OnTryReceive(TrackingContexttrackingContext,Int32messageCount, TimeSpanserverWaitTime,IEnumerable`1& messages)
atMicrosoft.ServiceBus.Messaging.MessageReceiver.TryReceive(TrackingContexttrackingContext,Int32messageCount, TimeSpanserverWaitTime,IEnumerable`1& messages)
atMicrosoft.ServiceBus.Messaging.MessageReceiver.TryReceive(TimeSpanserverWaitTime,BrokeredMessage& message)
atMicrosoft.ServiceBus.Messaging.QueueClient.Receive(TimeSpanserverWaitTime)

                  

Servicebus Message Lock Lost exception

$
0
0

HI there,

We have a Premium service-bus subscription in Production, the Lock token is expired too sooner and the same message is picked up by other threads of Logic app(I am using Logicapp to process the Message payload), like wise multi threads of Logic apps are picking the same message and trying to process while the first one is still in progress. The Lock Duration for ServiceBus is 5 minutes.

Please help. we are facing this issue and lot many Logic apps are executed unnecessarily. 

Thanks.


Message lock lost - service bus outage?

$
0
0

Trying to troubleshoot what seems to be an Azure service bus issue - the message consumer is logic apps, but this felt like the more appropriate forum.

I completed a load test over the weekend, around 8500 messages processed successfully, but 5 errors. 4 of the errors occurred at very close to the same time, which is why I'm suspicious of some kind of outage.

I have a logic app consuming messages from the service bus - it is configured currently to process up to 10 messages concurrently. For the 5 errors, it appears as if there is some kind of issue when marking the message as 'complete' and hence removing it from the queue - the logic app reports a 'Gateway timeout', and on automatically retrying the same step receives a message from the service bus:

"Failed to complete the message with the lock token '250e397b-f3d1-45e4-9e6f-e07e79ff0037'. The lock on the message has been lost"

On checking the logic app executions, I can see another attempt was made to process the same message with a DIFFERENT message lock ID, approximately 5 seconds after the first attempt encountered the gateway timeout (and hence the 2 logic app executions ran concurrently for a while). It appears that the original lock on the message was somehow abandoned, and the 2nd logic app picked it up from the service bus again.

Summary of some key data for the 2 attempts at processing the message in the image below - the service bus is configured with a lock period of 5 minutes, which I see reflected in the 'enqueued time' and 'locked until' values for the first attempt.

Any ideas? Thanks in advance.

Case Study Request: Azure Service Bus for Integrating Legacy Applications

$
0
0

Hi all,

Does anyone know of a case study for using Azure Service Bus in an Enterprise setting for integrating a variety of legacy monoliths and new services, written in different languages?

Don't specifically need technical detail of implementation, need evidence that others are doing this to assist with convincing of stakeholders.

Thanks

Unable to receive messages frpm Azure Service Bus Queue & topics

$
0
0

Hello,

I have a tried with below sample for receiving messages from Azure Service Bus 

 https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-how-to-use-topics-subscriptions

But getting below error on running for Queues & Topics from console app. Pls help

Message handler encountered an exception Microsoft.Azure.ServiceBus.ServiceBusCommunicationException: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server ErrorCode: TryAgain ---> System.Net.Sockets.SocketException: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.ServiceBusConnection.<CreateConnectionAsync>d__45.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.FaultTolerantAmqpObject`1.<OnCreateAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.Singleton`1.<GetOrCreateAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.Singleton`1.<GetOrCreateAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.Amqp.AmqpLinkCreator.<CreateAndOpenAmqpLinkAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<CreateLinkAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.FaultTolerantAmqpObject`1.<OnCreateAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.Singleton`1.<GetOrCreateAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.Amqp.Singleton`1.<GetOrCreateAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<OnReceiveAsync>d__86.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<OnReceiveAsync>d__86.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<>c__DisplayClass64_0.<<ReceiveAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.RetryPolicy.<RunOperation>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.Azure.ServiceBus.RetryPolicy.<RunOperation>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<ReceiveAsync>d__64.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<ReceiveAsync>d__62.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Azure.ServiceBus.MessageReceivePump.<<MessagePumpTaskAsync>b__11_0>d.MoveNext().
Exception context for troubleshooting:
- Endpoint: vicroadsservicebus.servicebus.windows.net
- Entity Path: userqueue
- Executing Action: Receive


Krishna


Impossible to deploy custom service bus queue endpoint for IoT Hub

$
0
0

When navigating to my IoT Hub > Add custom endpoint > Service bus, I'm always getting the same error during deployment: "Unable to refresh hub data from service Cannot read property 'd32059e9-2875-4b8b-a533-35541e16f825' of null"

Please help


Should Delete Locks be respected from Service Bus Explorer

$
0
0
I have created Delete locks on all our resources in the Azure Portal, however we can delete a queue via the Service Bus Explorer Application, if we try and delete the queue via the portal the lock is respected.  Should Delete Locks prevent the deletion of queues from Service Bus Explorer?

Cannot access a disposed object. Object name: 'tlsxyz'

$
0
0

I'm facing a random error when sending message from an Azure function to an Azure Service Bus (Standard) Topic.

the message error is:

Cannot access a disposed object. Object name: 'tls2576'., Stacktrace : at Microsoft.Azure.ServiceBus.Core.MessageSender.OnSendAsync(IList1 messageList) at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func1 operation, TimeSpan operationTimeout) at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func1 operation, TimeSpan operationTimeout) at Microsoft.Azure.ServiceBus.Core.MessageSender.SendAsync(IList1 messageList) at ServiceBusFunctions.MyTopic.Run(HttpRequest req, ILogger log, ExecutionContext context) in myAzureFunction

sometimes the object name in the error is 'tls2716'.

The code is running from an Azure function instance containing 3 functions. Tere are 2 redundant functions APP containing the same code called in round robin from an Application Gateway. The client code to send messages to the topic is:

var message =newMessage(Encoding.UTF8.GetBytes(requestBody));//Custom properties for topis routing
message.UserProperties.Add("P1", P1);
message.UserProperties.Add("P2", P2);
message.UserProperties.Add("P3", P3);ITopicClient topicClient =newTopicClient(SBConnectionString,CCTopicName);
await topicClient.SendAsync(message);
await topicClient.CloseAsync();

thanks for your help

Azure EventHub Event Format

$
0
0

All,

I set up an EventHub Namespace and EventHub and was able to successfully send and receive events to it using Python scripts. I was also able to enable the Capture feature and store the events in Azure Blob Storage in Avro format. 

I wanted to know more about EventHubs and would be great if someone points me in the right direction:

[1] Can the file format be changed to say for example csv or json format so that the files get created in csv/json format? Or is Avro the only one supported?

[2] When the Event is in EventHub itself before it gets aged out what is the format of the event - is it json?

[3] When the Event data is stored in Azure Blob Storage (in avro format) how do I know what is the structure of the data so that I can create an appropriate schema which I can then use in Azure Data Explorer definition.

Thanks,

rgn

Put token failed. status-code: 404, status-description: The messaging entity 'sb://nxpricing-dev.servicebus.windows.net/request-input' could not be found. TrackingId:c67efadd-8f86-4d01-b082-183c7ce27577_G13

$
0
0

I have a python Azure Function running in a container in AKS. 

The function received a message from a queue, and puts a message in another queue back. This is referring to the inbound queue:

fail: Host.Executor[0] 
      MessageReceiver error (Action=Receive, ClientId=MessageReceiver1request-input, EntityPath=request-input, Endpoint=nxpricing-dev.servicebus.windows.net) 
Microsoft.Azure.ServiceBus.MessagingEntityNotFoundException: Put token failed. status-code: 404, status-description: The messaging entity 'sb://nxpricing-dev.servicebus.windows.net/request-input' could not be found. TrackingId:c67efadd-8f86-4d01-b082-183c7ce27577_G13, SystemTracker:nxpricing-dev.servicebus.windows.net:request-input, Timestamp:2019-08-30T06:23:20. 
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.OnReceiveAsync(Int32 maxMessageCount, TimeSpan serverWaitTime) 
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.<>c__DisplayClass65_0.<<ReceiveAsync>b__0>d.MoveNext() 
--- End of stack trace from previous location where exception was thrown --- 
   at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func`1 operation, TimeSpan operationTimeout) 
   at Microsoft.Azure.ServiceBus.RetryPolicy.RunOperation(Func`1 operation, TimeSpan operationTimeout) 
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.ReceiveAsync(Int32 maxMessageCount, TimeSpan operationTimeout) 
   at Microsoft.Azure.ServiceBus.Core.MessageReceiver.ReceiveAsync(TimeSpan operationTimeout) 
   at Microsoft.Azure.ServiceBus.MessageReceivePump.MessagePumpTaskAsync()

Any ideas?

thanks!

Azure Lab Services cannot create VMs

$
0
0

I am getting the error: 

40103: Invalid authorization token signature, Resource:sb://dtl-row2-sb-westeurope.servicebus.windows.net/row2-uksouth-operationjobs4. TrackingId:27876b41-b5ad-49c2-8eea-df87ceb6c773_G22, SystemTracker:dtl-row2-sb-westeurope.servicebus.windows.net:row2-uksouth-OperationJobs4, Timestamp:2020-01-10T22:36:30


Classroom labs is also failing to start VMs. I tried performing starting of the VMs from different computers and restarting my computer and it's still not working.

This seems to me like a backend issue in Azure but is there something different I could be doing to fix this on my end?

There was no Forum for Azure VMs or Lab Services so I picked Service Bus since I saw some other answers on social.msdn referring to Service Bus.

Login not possible

$
0
0

Hi,my account has been blocked and i need to contact the support. But to create a ticket i need to log in. Do someone know an address for support? I found nothing without using an account.

Thanks a lot.


Could not load file or assembly 'Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The module was expected to contain an assembly manifest.

$
0
0

I have been using this Microsoft.ServiceBus.dll recently in my .net windows service and it was working fine . Suddenly it started showing this error when being used in Windows service which is deployed now to production. Downgrading to 2.7.6 is not a solution as it is not working for me .

The file exists at proper place with proper reference given and Copy Local is also set to True.

.Please help




TimeOutException on Azure Service Bus message post

$
0
0

Hi!

Can you please give a reason why I get the following exception continuous around 3 minutes while sending message to Azure Service bus? Below mentioned is the detail stack trace. Is there any workaround to handle this type of failure?


System.TimeoutException: The request operation did not complete within the allotted timeout of 00:01:10. The time allotted to this operation may have been a portion of a longer timeout. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:9746a2cb-0f95-43c5-b3f4-2233f0e94905, Timestamp:1/17/2020 8:53:08 AM
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<>c.<GetAsyncSteps>b__9_3(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.RequestAsyncResult.<>c__DisplayClass8_1.<GetAsyncSteps>b__4(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<>c.<GetAsyncSteps>b__9_3(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpTransactionalAsyncResult`1.<>c.<GetAsyncSteps>b__18_3(TIteratorAsyncResult thisPtr, IAsyncResult a)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.EndSendCommand(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.OnEndSend(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.MessageSender.OnSend(TrackingContext trackingContext, IEnumerable`1 messages, TimeSpan timeout)
   at Microsoft.ServiceBus.Messaging.MessageSender.Send(TrackingContext trackingContext, IEnumerable`1 messages, TimeSpan timeout)

 

AMQP error: The format code '0xD1' at frame buffer offset '56' is invalid or unexpected.

$
0
0
I have an application that is writing to Azure service bus using the Javascript interface, and get this error as one of the websocket messages back from the server.  The connection string being used is correct, and everything looks good regarding the message content.  Does anyone here have any idea what this error might mean?  I'm quickly running out of ideas, and the message doesn't provide much information. 

Can a service bus subscribe to a topic from a different service bus?

$
0
0

The system I'm working on has 2 services busses.  One is an external service bus for incoming messages from IoT devices and outgoing messages to 3rd parties, the other is for message passing between the different internal components of the system.

There is now a requirement to expose some existing (internal) messages, to the external service bus, and I'd like to do this without changing any code.  

Is there a way for an external topic to be sent messages from an internal subscription?   I realise I could do this with code, but is there a way with 'just' infrastructure configuration?


Resubmit deadletter message to subcription

$
0
0

Hi

We have a scenario where a message fails multiple times for a particular subscriber and is sent to the deadletter queue. Particular deadletter messages we want to resubmit to the particular subscriber at a later time.

I cannot see a way to do this. I try to resubmit to the subscriber's queue doing something like the following:

var subscriptionPath = SubscriptionClient.FormatSubscriptionPath(topicName, subscriptionName);
var client = QueueClient.CreateFromConnectionString(connectionString, subscriptionPath);
client.Send(brokeredMessage);

But this causes an Invalid Operation exception with message Cannot open a Queue client for entity type Subscriber.

I'm able to resubmit it to the topic, but that means all subscribers receive it, so I don't want to do this.

How do I do this? If I'm not able to, what is recommended instead?

Thanks

Viewing all 1916 articles
Browse latest View live