Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Check if your server (or a proxy server) is not going up and down. There might be something between a proxy and a client sending intermittent requests to non-functioning hosts as well. There might as well be too many requests in a short amount of time.

  2. ,
    Expert tip

    Check if your server (or a proxy server) is not going up and down. There might be something between a proxy and a client sending intermittent requests to non-functioning hosts as well. There might as well be too many requests in a short amount of time.

Solutions on the web

, 1 year ago
Error setting up client lease upon performing connect.
via GitHub by nottaran
, 1 year ago
Error setting up client lease upon performing connect.
via GitHub by Sixftrabbit
, 2 years ago
Error setting up client lease upon performing connect.
via GitHub by ericsvince
, 5 months ago
Error setting up client lease upon performing connect.
via Stack Overflow by megabobik
, 2 years ago
Error setting up client lease upon performing connect.
via Stack Overflow by MadMad666
, 2 years ago
Error setting up client lease upon performing connect.
java.net.ConnectException: Connection timed out: connect	at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)	at java.net.PlainSocketImpl.connect(Unknown Source)	at java.net.SocksSocketImpl.connect(Unknown Source)	at java.net.Socket.connect(Unknown Source)	at org.jboss.remoting.transport.socket.SocketClientInvoker.connect(SocketClientInvoker.java:293)	at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:210)	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket(BisocketClientInvoker.java:477)	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:1190)	at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:833)	at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:470)	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169)	at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:529)	at org.jboss.remoting.Client.setupClientLease(Client.java:2070)	at org.jboss.remoting.Client.connect(Client.java:1924)	at org.jboss.remoting.Client.connect(Client.java:737)	at mage.remote.SessionImpl$5.run(SessionImpl.java:403)	at mage.remote.SessionImpl.handleRemotingTaskExceptions(SessionImpl.java:136)	at mage.remote.SessionImpl.establishJBossRemotingConnection(SessionImpl.java:281)	at mage.remote.SessionImpl.connect(SessionImpl.java:239)	at mage.client.MageFrame.connect(MageFrame.java:822)	at mage.client.dialog.ConnectDialog$ConnectTask.doInBackground(ConnectDialog.java:411)	at mage.client.dialog.ConnectDialog$ConnectTask.doInBackground(ConnectDialog.java:401)	at javax.swing.SwingWorker$1.call(Unknown Source)	at java.util.concurrent.FutureTask.run(Unknown Source)	at javax.swing.SwingWorker.run(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)	at java.lang.Thread.run(Unknown Source)