| Author |
Message
|
| JoseR |
 Posted: Thu Apr 27, 2006 1:43 pm Post subject: SOAP Client - HttpURLConnection versus socket |
 |
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
Hello There,
Has anyone run into the follwoing scenario:
After developing a web service on WMB v6.0 listening on port 7080.
HTTPinput node -> Filter node -> HTTP request node (to WebSphere web service) -> HTTP Reply node
I started developing a simple web service client in java.
If I run the client and the broker on my local machine (Windows), everything works beautifully. However If a push the web service to my development box (AIX server) my client fails with a Error 500: Server returned HTTP response code: 500 for URL:...
Someone once told me that I could use sockets instead for my currently HttpURLConnection call.
Enabling the debugger, this is what I found:
On the local web service, the HTTP Request Node returns a meesage and the flow request completes just fine.
On the remote (AIX) web service, the HTTP Request Node fails to return a message and soon the message flow gives up returning a 500 error message from the server.
Any ideas as to what might have gone wrong here.[/img]
_________________
Jose R
WWJD
< ))><< |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 27, 2006 8:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
How about the deploy of the webservice to the AIX box.
Could you ever get the service to work on this box independantly from the broker?
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Apr 28, 2006 6:34 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| I had this problem when I developed the web service using WSADIE. For some reason, WSADIE wasn't returning. I didn't have the problem with WID though. |
|
| Back to top |
|
|
| JoseR |
| Posted: Mon May 01, 2006 6:52 am Post subject: |
|
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
Thanks for the Follow up everyone.
To answer yoru question:
The web service works just fine when I call it independently from the broker. The web service also works when I make a call through the broker on my local system (Windows XP). The web service fails however when I make a call from the broker on my AIX server (from my client on my windows system).
I am using RAD to develop and test the client call and have also configure the WMB Toolkit with RAD to have a single workbench.
_________________
Jose R
WWJD
<))><< |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 01, 2006 2:46 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is there a network connectivity problem between your windows machine and the AIX machine?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JoseR |
| Posted: Tue May 02, 2006 8:18 am Post subject: |
|
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
I do not believe there are connectivity issues between AIX and Windows server but I will check again to validate this point.
I had extended the request time out for my HTTP Request node from 120 secs to 400 sec and enalbed the Debbuger.
Here there are some context from the SockeException for last 2 exceptions on the Exception tree of the RecoverableException
Text = A Web Service request has detected a SOCKET error whilst invoking a web service located at host &1, on port &2, on path &3.
Text = A connection with a remote socket was reset by that socket.
Obviously, the request gets propagated from AIX broker to the Web Service Server on Windows.. but This Windows server however does not return a reply because of the socket reset (I believe).
Note: - The windows broker does not present this issues and so the WebService Server on Windows can pass the request to the WIN broker without any problem.
_________________
Jose R
WWJD
<))><< |
|
| Back to top |
|
|
|
|
