[Grinder-development] [ grinder-Bugs-927828 ] Proxy exits unexpectedly

[SourceForge.net <no...@so...>]

Bugs item #927828, was opened at 2004-04-01 21:06
Message generated for change (Comment added) made by philipa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=927828&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: TCPProxy
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Brett Knights (bknights)
Assigned to: Philip Aston (philipa)
Summary: Proxy exits unexpectedly

Initial Comment:
The grinder-3.0-beta21 exits unexpectedly. 
JDK:
java version "1.4.2_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 
1.4.2_02-b03)
Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed 
mode)

Windows 2000 Pro.
The last exception thrown follows although it threw a 
bunch of these and continued to work.

java.net.ConnectException: Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native 
Method)
        at java.net.PlainSocketImpl.doConnect
(PlainSocketImpl.java:305)
        at java.net.PlainSocketImpl.connectToAddress
(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect
(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:452)
        at java.net.Socket.connect(Socket.java:402)
        at java.net.Socket.<init>(Socket.java:309)
        at java.net.Socket.<init>(Socket.java:124)
        at 
net.grinder.tools.tcpproxy.TCPProxySocketFactoryImplem
entation.create
ClientSocket
(TCPProxySocketFactoryImplementation.java:71)
        at 
net.grinder.tools.tcpproxy.HTTPProxyTCPProxyEngine$HT
TPProxyStreamDem
ultiplexer.run(HTTPProxyTCPProxyEngine.java:386)
        at java.lang.Thread.run(Thread.java:534)
Engine exited

----------------------------------------------------------------------

>Comment By: Philip Aston (philipa)
Date: 2005-12-17 13:09

Message:
Logged In: YES 
user_id=2117

This is old. (My fault, I know).

The TCPProxy works fine under W2K.

Looking at this stack trace, it appears you were attempting
to run the TCPProxy in port forwarding mode against a remote
host/port that wasn't contactable.

I've made some changes to the logging for 3.0 beta 28 (not
yet released) so nicer error messages will be produced when
end points can't be contacted.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=118598&aid=927828&group_id=18598