Is something blocking or is something wrong in our app.
Hello Guys!Right now I'm in a project were we uppgrading a java-ee-app from jboss 4 to jboss 5.1.2.
This app is making a webservice call to an other server in a IIS.
The infrastructure looks something like
Jboss -> black_box_of_firewalls -> Microsoft IIS.
Right now the IIS is down, and that is ok for now.
How ever my intention is that the old-app and the new-app should work in the same way.
But we get different response for the same call.
I have asked the firewall-guys to sniff the traffic after the firewall.
From the old-app we caught this call and response:
POST /xxx/ws_xxx.asmx HTTP/1.1
SOAPAction: "http://www.xxx.xx/xxx/aQuestion"
Content-Type: text/xml; charset=UTF-8
JBoss-Remoting-Version: 22
User-Agent: JBossRemoting - 2.2.2.SP10
Host: 1.2.3.4:1234
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Length: 264
Connection: Keep-Alive
X-BlueCoat-Via: 80AF669A73FA896C
<env:Envelope>bla bla bla</env:Envelope>
HTTP/1.1 500 Internal Server Error
Date: Fri, 11 May 2012 10:38:45 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 493
<?xml version="1.0" encoding="utf-8"?> bla bla bla<soap:Envelope></soap:Envelope>
To me I can see the soap-envelop we sent and that the IIS responded.
But from the new-app we caught this call and response:
POST /xxx/ws_xxx.asmx HTTP/1.1
SOAPAction: "http://www.xxx.xx/xxx/aQuestion"
Content-Type: text/xml; charset=UTF-8
JBoss-Remoting-Version: 22
User-Agent: JBossRemoting - 2.5.4.SP3 (Flounder)
remotingContentType: remotingContentTypeNonString
Host: 1.2.3.4:1234
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Transfer-Encoding: chunked
Connection: Keep-Alive
X-BlueCoat-Via: 80AF669A73FA896C
HTTP/1.1 400 Bad Request
Content-Type: text/html
Date: Fri, 11 May 2012 10:34:37 GMT
Connection: close
Content-Length: 20
<h1>Bad Request</h1>
As you can se there seems to be no soap-envelop in the request, and there are some different other header like: Transfer-Encoding: chunked, and remotingContentType.
In the response I see nothing about IIS either. So even if my firewall-guys say that I'm wrong I do have some doubt's that the response in fact came from the IIS.
What do you think guys, could this be because of:
1) Bug in new-app
2) Misstake in sniffing, the sniffer missed the envelop in some strange way
3) Something in firewall is removing the sending saop-envelope
4) The response is from somtehing else, perhaps inour balck box of fire walls.
...or something else?
All guesses and suggestions are most welcome.
Best regagards
Fredrik