Service Broker Driving me insane

  •  

    So I've recently replaced the broker endpoints on our servers to all have a "generic" identical name (rather than a server specific name) and to all have the same port. All good so far.

    However running a broker trace on the destination server I see that some messages are failing with

    This message was dropped because it could not be dispatched on time. State: 2

    When I look at the targetUsername it references a service with the OLD port name before the endpoints were dropped and recreated. I cant find anywhere in code that would explain this .

    Any words of wisdom before I leap out a window ?

     

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply