Webserver problem when posting number via http

Okay, here’s the situation that I’m very confused about. We have two QA servers that are in a cluster. The package that I created does something at the end where it calls a webservice and posts an EAI tracking number to the webserver via http. As mentioned before, both QA servers are in a cluster.

Today, I noticed that one QA server is posting the EAI tracking number properly and receiving back a return code, whereas the other QA server tries to post the EAI tracking number, but doesn’t get back the return code. There’s no return code at all. What makes this so weird is that both servers have the exact same code and both are calling the exact same webserver. While tracing through the code, I noticed the below when I run pub.client:http in my PostEAINumber service:

QA server one:

I see the following in the Results tab for the header/lines document:

Name Value

Pragma no-cache
Cache-control no-cache
Content-type text/html
Content-length 90

QA server two (the server that posts the EAI number properly):

Server Microsoft-IIS/5.0
X-Powered-By ASP.NET
X-AspNet-Version 1.1.4322
Cache-Control private, max-age=0
Content-Type text/xml; charset=utf-8

Why the difference? What is this telling me? Can anyone here please tell me what to try…what to look for… any tips why all of a sudden this could be happening when you’re talking about two server that have the same package information, calling the exact same webserver?

By the looks of this its looking to me that the QA1 server is not able to maintain the connection state from start till end of the transaction. Just check from where you are getting the response code. Is it that the QA1 server does not have a proper network port opened because of which it is able to send a request but not receive a response as its inbound port is not in place to accept response.

Also ensure that the network paths between both your servers are open to and from your target application.