java.net.SocketTimeoutException

connect timed out: 10.117.50.52:4335" [90067-165]

Samebug tips1

Check for proxy misconfigurations and AWS issues.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web3690

  • via Google Groups by Henrik Mohr, 11 months ago
    connect timed out: 10.117.50.52:4335" [90067-165]
  • connect timed out: mydomain:9092" [90067-168] Error Code: 90067
  • via nutch-user by Manish Verma, 9 months ago
    connect timed out
  • Stack trace

    • java.net.SocketTimeoutException: connect timed out: 10.117.50.52:4335" [90067-165] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:158) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:397) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:287) at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:110) at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:94) at org.h2.Driver.connect(Driver.java:72) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:266) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:175) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:684) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:616) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:479) at org.apache.tomcat.jdbc.pool.ConnectionPool.<init>(ConnectionPool.java:135) at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:114) at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:101) at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:125) at datomic.sql$connect.invoke(sql.clj:12) at datomic.sql$select.invoke(sql.clj:74) at datomic.kv_sql.KVSql.get(kv_sql.clj:60) at datomic.kv_cluster.KVCluster$fn__2086$fn__2088.invoke(kv_cluster.clj:83) at datomic.kv_cluster.KVCluster$fn__2086.invoke(kv_cluster.clj:81) at clojure.core$binding_conveyor_fn$fn__3989.invoke(core.clj:1819) at clojure.lang.AFn.call(AFn.java:18) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384) at java.net.Socket.connect(Socket.java:546) at org.h2.util.NetUtils.createSocket(NetUtils.java:119) at org.h2.util.NetUtils.createSocket(NetUtils.java:100) at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:93) at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:393) ... 25 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 day ago
    Unknown user
    Once, 1 day ago
    Unknown user
    Once, 1 day ago
    24 times, 3 days ago
    Unknown user
    Once, 3 days ago
    1196 more bugmates