db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendleton.de...@gmail.com>
Subject Re: Derby confuse with SWing Application Framework
Date Mon, 31 May 2010 14:16:10 GMT
On 05/30/2010 08:46 PM, Hawkx wrote:

> 	at java.net.SocketInputStream.socketRead0(Native Method)
> 	at java.net.SocketInputStream.read(SocketInputStream.java:129)
> 	at java.net.SocksSocketImpl.readSocksReply(SocksSocketImpl.java:88)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:429)
> 	at java.net.Socket.connect(Socket.java:529)

Does this indicate that there is a SOCKS proxy in use?

Perhaps there is a problem with communications via the SOCKS proxy.

Can you configure your application to run without the SOCKS proxy, at least
for experimental testing, to isolate whether that is the source of the problem?



View raw message