1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Resolved Connection refused to host

Discussion in 'Developer Support' started by Aidden, Feb 15, 2016.

  1. Aidden

    Aidden Author of MaxiBots

    Joined:
    Dec 3, 2013
    Messages:
    6,482
    Likes Received:
    990
    Just got this after starting an instance and then closing the game client via the x in the corner

    Code (Text):
    1.  
    2. java.rmi.ConnectException: Connection refused to host: 192.168.0.100; nested exception is:
    3.     java.net.ConnectException: Connection refused: connect
    4.     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
    5.     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    6.     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    7.     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130)
    8.     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
    9.     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
    10.     at com.sun.proxy.$Proxy8.uid(Unknown Source)
    11.     at nul.iiIIiIiiIIii.enum(ewb:93)
    12.     at com.runemate.game.api.hybrid.local.Varp.getValue(shc:20)
    13.     at com.runemate.api.Utils.isGameReady(Utils.java:45)
    14.     at com.runemate.maxibots.tools.webBuilder.WebBuilder.onLoop(WebBuilder.java:61)
    15.     at com.runemate.game.api.script.framework.LoopingScript.run(xub:115)
    16.     at com.runemate.game.api.script.framework.AbstractScript.start(mob:29)
    17.     at nul.IIIiIIiiIiiI.run(bec:112)
    18. Caused by: java.net.ConnectException: Connection refused: connect
    19.     at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    20.     at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
    21.     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    22.     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    23.     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    24.     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    25.     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    26.     at java.net.Socket.connect(Socket.java:589)
    27.     at java.net.Socket.connect(Socket.java:538)
    28.     at java.net.Socket.<init>(Socket.java:434)
    29.     at java.net.Socket.<init>(Socket.java:211)
    30.     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
    31.     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
    32.     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
    33.     ... 13 more
    @Cloud

     
  2. Best Answer:
    Post #3 by Arbiter, Apr 6, 2016
  3. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    This is a very easily reproducible issue but a very hard one to fix. Low priority but acknowledged.
     
  4. Arbiter

    Arbiter Mod Automation

    Joined:
    Jul 26, 2013
    Messages:
    2,937
    Likes Received:
    1,266
    tl;dr Don't do that.
     

Share This Page

Loading...