[prev in list] [next in list] [prev in thread] [next in thread]
List: soap-user
Subject: RE: need Using the MSSoapT (and TcpTunnelGui) trace program inclu
From: Pete Roth <proth () telemetrytech ! net>
Date: 2001-07-31 17:26:08
[Download RAW message or body]
That's ok about the mistake. About the firewall though. Don't all the
packets use port 80 anyway? Or are they somehow going out at the localhost
port? Or some other port, not 80? Port 80 is definitely opened on our
firewall, but if those tracing programs somehow use another port to actually
send the packets, that may be closed. Yet I don't think that is possible
since the web server is only listening on port 80.
Thanks for all your help anyway. Anyone else have any ideas?
Peter Roth
Telemetry Technologies Inc.
p: 404.231.0021 ext. 1290
e: proth@TelemetryTech.net
-----Original Message-----
From: Steeve Gilbert [mailto:Steeve_Gilbert@canammanac.com]
Sent: Tuesday, July 31, 2001 1:00 PM
To: soap-user@xml.apache.org
Subject: RE: need Using the MSSoapT (and TcpTunnelGui) trace program
inclu ded with MSSoap toolkit
Yes I made a mistake. But I don't know what else to do. Anyway, be sure
that it's not your firewall that's getting in the way.
Good luck!
Steeve...
Pete Roth <proth@telemetrytech.net> on 31/07/2001 12:02:26 PM
Please respond to soap-user@xml.apache.org
To: "'soap-user@xml.apache.org'" <soap-user@xml.apache.org>
cc: (bcc: Steeve Gilbert/G_STGEORGES/CANAM_MANAC)
Subject: RE: need Using the MSSoapT (and TcpTunnelGui) trace program inclu
ded with MSSoap toolkit
It's still not working. Yet, thanks for your help so far Steve.
I was already doing something similar to what you said. Your method didn't
work either and I don't see how it would. You said:
[Client point to http://server:8080/adir/file.asmx?WSDL] -->[MSSoapT Listen
Yet, shouldn't "server" be changed to "localhost" Since that is what
MSSoapT
or TcpTunnel listen on? Even if I put localhost though it doesn't work.
(I
tried with my server IP and localhost). I get, this back when using
"localhost" for the "server" in the above example (if I use my server IP I
get nothing back, it just hangs and not even the sent XML appears in
MSSoapT
or TcpTunnel):
****************************************************************************
****
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response
content ty
pe "text/html; charset=iso-8859-1", must be: "text/xml". Response was:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD><BODY>
<H1>Not Found</H1>
The requested URL /VnocngWebService/VnocngWebService.asmx was not found on
this
server.<P>
</BODY></HTML>
]
at org.apache.soap.rpc.Call.getEnvelopeString(Call.java:175)
at org.apache.soap.rpc.Call.invoke(Call.java:212)
at com.telemetrytech.utils.SoapAddTest.main(SoapAddTest.java:81)
****************************************************************************
****
I am putting only the SOAP server IP into MSSoapIP "Destination host" on
port 80. Or, If using TcpTunnel I use "8080 MyServerIP 80" as the three
command line arguments. I put the entire address (protocol and all) in my
Java client (using localhost:8080 instead of my server's IP though when
trying to use either SoapT or TcpTunnel).
If you have any further Idea's I'd love to hear them. Our firewall
shouldn't be blocking me could it? As far as I can tell only port 80 is
being used still. Since I see the data working like this:
SOAP Request:
JavaClient --> MSSoapT (or TcpTunnel) --> my server
SOAP Response:
my server --> MSSoapT (or TCPTunnel) --> my client.
If I understand this correct as above, it seems that MSSoapT is not passing
the XML onto my server correct. It seems to be messing up the URL along
the
path. Remember I am defining the path to the service endpoint only in my
Client, MSSoapT only has the IP and port of the server.
Peter Roth
Telemetry Technologies Inc.
p: 404.231.0021 ext. 1290
e: proth@TelemetryTech.net
-----Original Message-----
From: Steeve Gilbert [mailto:Steeve_Gilbert@canammanac.com]
Sent: Tuesday, July 31, 2001 10:44 AM
To: soap-user@xml.apache.org
Subject: Re: need Using the MSSoapT (and TcpTunnelGui) trace program
included with MSSoap toolkit
Hi Pete!
You didn't mentionned it but I guess your client is in Java since you're in
this list right?
[Client point to http://server:8080/adir/file.asmx?WSDL] -->[MSSoapT Listen
to 8080. Redirect call to server on port 80] --> [The server (Listenning
to 80) take this and respond (suppose to)]
If with this you server doesn't respond, maybe it got a problem. I have a
Java client and a .NET service and that's what I do.
Steeve...
Pete Roth <proth@telemetrytech.net> on 31/07/2001 10:13:38 AM
Please respond to soap-user@xml.apache.org
To: "Soap-dev List (E-mail)" <soap-dev@xml.apache.org>, "Soap-user list
(E-mail)" <soap-user@xml.apache.org>
cc: (bcc: Steeve Gilbert/G_STGEORGES/CANAM_MANAC)
Subject: need Using the MSSoapT (and TcpTunnelGui) trace program included
with MSSoap toolkit
Has anyone gotten the MSSoapT tracing program to work that comes with the
MSSoap toolkit? It is a similar program to TcpTunnelGUI. I cannot get it
to pass the information to my server correctly.
The instructions below however do not say what to do with the wsdl file
once
it is downloaded and modified. If I do exactly what it says, nothing will
happen since my client still points to the asmx file on the server. Also,
I
am running a .NET server which the endpoint is not .wsdl, but .asmx. To
see
the WSDL file you do (POST or GET I forget) and add a ?WSDL to the end of
the .asmx URL.
So, I tried pointing my client to the local wsdl file I downloaded and
modified. This however will not work, since I cannot have a local web
server on the same port that the MSSoapT program is listening on which
would, I think, be required if I point my client to the local wsdl file.
Any help would be appreciated. I am trying to get this Microsoft Trace
program working since the TcpTunnelGui would never pass the requests it
receives to the server. (Basically the same problem I'm having now). If
someone could help me with that program that would be just as great.
For TcpTunnelGui, I point my client to the local port (with the server path
to the .asmx file still appended), run TcpTunnelGui with that local port,
put the server IP address as the second argument and port 80 (port server
is
listening on) as the third argument. Doing this, the client just hangs
after sending out the XML, which I see in TcpTunnelGui. It seems to be
waiting for the server to respond, which it never does.
Any help on either matter would be VERY helpful. I haven't found anything
in the archives about TcpTunnelGui not working after it is seemingly setup
correctly. Should I specify the path on the host argument to TcpTunnelGui
maybe? I have tried that and that never worked either.
These are the instructions Microsoft includes for using this program:
Copy the WSDL file from the server to the client.
Modify location attribute of the <soap:address> element in the local
copy of the WSDL document to direct the client to localhost:8080 and make a
note of the current host and port. For example, if the WSDL contains
<http://MyServer/VDir/Service.wsdl>, change it to
<http://localhost:8080/VDir/Service.wsdl> and make note of "MyServer".
On the client, run MSSOPT.exe.
On the File menu, point to New, and either click Formatted Trace (if
you don't want to see HTTP headers) or click Unformatted Trace (if you do
want to see HTTP headers).
In the Destination host box, enter the host specified in Step 2.
In the Destination port box, enter the port specified in Step 2.
Click OK.
Thanks.
Peter Roth
Telemetry Technologies Inc.
p: 404.231.0021 ext. 1290
e: proth@TelemetryTech.net
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic