Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

java.net.ConnectException: Operation timed out: connect

843830Oct 14 2005 — edited Oct 26 2005
code:
URL url = new URL((URL)null,<a servlet url here>,new HttpTimeoutHandler(this.timeout));
URLConnection con = url.openConnection();
con.setUseCaches(false);
sendHeaders(con);
======================================
when session is alive, the code is ok. but when session timeout, these code will cause exception:
java.net.ConnectException: Operation timed out: connect


Please help me! Thank you!

Comments

Answer

What platform are you on? What are the permissions for the keyfile and directory containing the keyfile? In particular, are the file/directory permission set to permit only the current user to read them? Our new library defaults to enforcing the recommended SSH security practice of having keyfiles be readable by only the current user.

Marked as Answer by Robert Schaefer · Jan 2 2020
Robert Schaefer

Hi John,

i'm running SQL Developer on MacOS 10.15.2. The file permission for the private key is limited to "rw-------" (600). But the directory (".ssh") containing the keys has a lower permission level with "rwxr-xr-x". I limited it to "rwx------" and now the SSH Connections in SQL Developer are working again! Great support, thank you!

I'm glad that you were able to solve your issue. The lack of proper feedback with our new SSH library is something I am looking into. In a future release I hope to provide detailed information when we run into a configuration issue.

YujiSoftware

I had the same problem in my environment.
(SQLDeveloper version 21.2.1.204, build 204.1703)

After investigating the cause, I found that it was a bug in Apache Mina SSHD 2.6.0.
https://issues.apache.org/jira/browse/SSHD-1105
(I've confirmed that this fix solves the problem)

This bug has been fixed in sshd-2.7.0.

I want you to update the version of sshd included in SQLDeveloper.

John McGinnis-Oracle

Thanks for the update. Can you test in your environment with our 21.4.3 release? We updated to sshd-2.7.0 in that release, so hopefully it works out of the box.

YujiSoftware

Thank you for your comment.
After upgrading, it worked fine!
(SQL Developer version 21.4.3.063, build 063.0100)

The Japanese page is still 21.2.1, so I'd be happy if you could update it.
https://www.oracle.com/jp/tools/downloads/sqldev-downloads.html

1 - 6
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Nov 23 2005
Added on Oct 14 2005
1 comment
315 views