August 1, 2017 at 4:01 am
So I have a basic service broker set up for data auditing , two separate initiators set up to send XML messages to a single target box. They use totally separate queues , routes, endpoints etc . I have used the same setup on 3 VPC machines and 3 real servers so I dont "think" the issue is environmental in that respect.
Scenario 1 works just fine
Scenario 2 which I built as a copy of scenario 1 to run on a separate initiator fails (just to be clear they run totally seperately and are called by trigger calls)
It would appear messages happily leave the initiator , make it as far as the receiver queue (if I switch retention on I can see them there) but then vanish. My first thought was the activation proc but that looks just fine.
The messages I see in profile on the initiator are
An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.
And on the reciever
A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State 116.
10053(An established connection was aborted by the software in your host machine.)
Any words of wisdom ? Ive gone through the code time and time again and Im at a loss
thanks Simon
August 1, 2017 at 10:07 am
Check the ports specified in the route - usually have seen this error when the ports are in use for something else.
You may also want to check this article - your error and some other troubleshooting is explained in the last section:
Troubleshooting Routing and Message Delivery
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply