db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike G (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1668) Unable to connect using Windows client
Date Thu, 10 Aug 2006 21:27:15 GMT
Unable to connect using Windows client

                 Key: DERBY-1668
                 URL: http://issues.apache.org/jira/browse/DERBY-1668
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions:
         Environment: Server: RHEL4 jdk1.5.0_06 derby
Client: WinXP jdk1.5.0_06 derby
            Reporter: Mike G

server classpath:

client classpath:

Running this on the server locally works fine:
ij> connect 'jdbc:derby://localhost:1527/MyDbTest';
ij> select * from derbyDb;
NUM        |ADDR
180        |Grand Ave.
1910       |Union St.

2 rows selected

However, a problem running this on the windows client (using tunnel-port 1528 to connect to
ij> connect 'jdbc:derby://localhost:1528/MyDbTest';

ERROR (no SQLState): A communication error has been detected. Communication protocol being
used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error
was detected: Software caused connection abort: recv failed. Communication function detecting
the error: *. Protocol specific error codes(s) TCP/IP SOCKETS

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message