Re: TCP monitor tool like TCPmon
6tc1_at_qlink.queensu.ca
Date: 09/30/04
- Next message: John K: "Re: way to extract the method names from all java files in a set of directories?"
- Previous message: Ankur Bulsara: "Re: Can't deserialize xsd:date attributes using Axis WSDL2Java classes"
- Next in thread: John K: "Re: TCP monitor tool like TCPmon"
- Maybe reply: John K: "Re: TCP monitor tool like TCPmon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 30 Sep 2004 13:00:14 -0700
D'oh... sorry, you are of course right... I wasn't paying attention
when I received the suggestion and when I actually tried it.
However, I have tried this solution and it still results in me not
being able to connect to the external website. The text field on top
correctly shows the HTTP request generated by my browser - but the
lower text field shows the stack trace:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at org.apache.axis.utils.tcpmon$Connection.run(tcpmon.java:1144)
Is it possible the parameters are different than "proxyHost" and
"proxyPort"?
Thanks,
Novice
- Next message: John K: "Re: way to extract the method names from all java files in a set of directories?"
- Previous message: Ankur Bulsara: "Re: Can't deserialize xsd:date attributes using Axis WSDL2Java classes"
- Next in thread: John K: "Re: TCP monitor tool like TCPmon"
- Maybe reply: John K: "Re: TCP monitor tool like TCPmon"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|