db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-1668) Unable to connect using Windows client
Date Mon, 30 Jul 2007 19:49:53 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden resolved DERBY-1668.
-----------------------------------

    Resolution: Cannot Reproduce

We have not had an update on this issue in some time. Closing CNR


> Unable to connect using Windows client
> --------------------------------------
>
>                 Key: DERBY-1668
>                 URL: https://issues.apache.org/jira/browse/DERBY-1668
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Client
>    Affects Versions: 10.1.3.1
>         Environment: Server: RHEL4 jdk1.5.0_06 derby 10.1.3.1
> Client: WinXP jdk1.5.0_06 derby 10.1.3.1
>            Reporter: Mike G
>
> server classpath:
> /opt/db-derby-10.1.3.1-bin/lib/derby.jar:/opt/db-derby-10.1.3.1-bin/lib/derbytools.jar:/opt/db-derby-10.1.3.1-bin/lib/derbynet.jar:/opt/db-derby-10.1.3.1-bin/lib/derbyclient.jar
> client classpath:
> d:\sun\db-derby-10.1.3.1-bin\lib\derbyclient.jar;d:\sun\db-derby-10.1.3.1-bin\lib\derbytools.jar;d:\sun\db-derby-10.1.3.1-bin\lib\derby.jar;d:\sun\db-derby-10.1.3.1-bin\lib\derbynet.jar
> 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 server)
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message