You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike G (JIRA)" <de...@db.apache.org> on 2006/08/10 23:27:15 UTC
[jira] Created: (DERBY-1668) Unable to connect using Windows client
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: 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.
-
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
[jira] Commented: (DERBY-1668) Unable to connect using Windows
client
Posted by "Bryan Pendleton (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1668?page=comments#action_12443683 ]
Bryan Pendleton commented on DERBY-1668:
----------------------------------------
Can you expand on the note "(using tunnel-port 1528 to connect to server) "? What is a
tunnel-port and how are you configuring it?
Can you not just set the hostname and port number of your Server machine directly in
the URL of your client-side connection?
> 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: 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.
-
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
[jira] Resolved: (DERBY-1668) Unable to connect using Windows
client
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-1668) Unable to connect using Windows
client
Posted by "Rajesh Kartha (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1668?page=comments#action_12427354 ]
Rajesh Kartha commented on DERBY-1668:
--------------------------------------
The first question that comes to my mind is:
Did you start the server on Linux using the -h option allowing clients from other host machines to connect to it ?
(Derby Server and Admin guide at http://db.apache.org/derby/docs/10.1/adminguide/derbyadmin.pdf for more info.)
> 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: 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.
-
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