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

Bug Runescape Appears To Have Closed Or Disconnected/ConnectIOexecption

Discussion in 'Client & Site Support' started by Cresent, Sep 30, 2017.

  1. Cresent

    Joined:
    May 27, 2017
    Messages:
    2
    Likes Received:
    0
    After having a bot run for X amount of time I get a error of: Runescape Appears To Have Closed Or Disconnected and also ConnectIOexecption

    Any fix for this?
     
  2. Savior

    Savior Java Warlord

    Joined:
    Nov 17, 2014
    Messages:
    4,906
    Likes Received:
    2,748
    Noticed that too. I'm on mobile so i can't provide logs atm, i will post them later here.
    Also it seems that it happens to all running sessions at once, not just a single session at a time.
     
  3. Cresent

    Joined:
    May 27, 2017
    Messages:
    2
    Likes Received:
    0
    Im only having 1 bot run at a time rn, maybe its something that needs a patch
     
  4. American Express

    American Express RuneMate Staff

    Joined:
    Oct 2, 2015
    Messages:
    3,097
    Likes Received:
    1,112
  5. Savior

    Savior Java Warlord

    Joined:
    Nov 17, 2014
    Messages:
    4,906
    Likes Received:
    2,748
    Code (Text):
    1.  
    2. [Debug] Java Home: c:\program files (x86)\runemate\jre
    3. [Debug] Java Version: 8u121 x86 (Oracle Corporation)
    4. [Debug] Maximum Heap Size: 990MB
    5. [Debug] RuneMate Version: 2.63.0
    6. [Debug] Operating System: Windows 10 x64
    7.  
    8.  
    9. (junk)
    10.  
    11.  
    12.  
    13. RuneScape appears to have been closed or disconnected.
    14. RuneScape appears to have been closed or disconnected.
    15. RuneScape appears to have been closed or disconnected.
    16. RuneScape appears to have been closed or disconnected.
    17. RuneScape appears to have been closed or disconnected.
    18. [Report on the forums] The bot object was stopped before its exception was thrown.
    19. java.rmi.ConnectIOException: Exception creating connection to: 192.168.178.34; nested exception is:
    20.     java.net.SocketException: Permission denied: connect
    21.     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
    22.     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    23.     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    24.     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130)
    25.     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227)
    26.     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179)
    27.     at com.sun.proxy.$Proxy8.uid(Unknown Source)
    28.     at nul.IIIiiIiiiiIIi.catch(kac:106)
    29.     at com.runemate.game.api.hybrid.local.Camera.getPitch(ajc:165)
    30.     at com.runemate.game.api.hybrid.local.Camera.const(ajc:46)
    31.     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    32.     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    33.     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    34.     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    35.     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    36.     at java.lang.Thread.run(Thread.java:745)
    37. Caused by: java.net.SocketException: Permission denied: connect
    38.     at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    39.     at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
    40.     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    41.     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    42.     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    43.     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    44.     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    45.     at java.net.Socket.connect(Socket.java:589)
    46.     at java.net.Socket.connect(Socket.java:538)
    47.     at java.net.Socket.<init>(Socket.java:434)
    48.     at java.net.Socket.<init>(Socket.java:211)
    49.     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
    50.     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
    51.     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
    52.     ... 15 more
    53. RuneScape appears to have been closed or disconnected.
    54. RuneScape appears to have been closed or disconnected.
    55. [Report on the forums] The bot object was stopped before its exception was thrown.
    56. RuneScape appears to have been closed or disconnected.
    57. RuneScape appears to have been closed or disconnected.
    58. [Report on the forums] The bot object was stopped before its exception was thrown.
    59.  

    @Cloud
    All RS3 and OSRS clients have this error at once. Internet connection isn't interrupted or anything as far as I am aware, since the RS3 sessions didn't expire.
     
  6. DeXuM

    Joined:
    Jul 12, 2018
    Messages:
    5
    Likes Received:
    0
    im currently experiencing this problem any fixes?
     
  7. IronFarmer

    Joined:
    May 1, 2017
    Messages:
    23
    Likes Received:
    0
    Same thing, since im using a premium bot i have already lost like 70 cents by it just running for few minutes and then closing.
     
  8. Negrita

    Joined:
    Jan 28, 2017
    Messages:
    491
    Likes Received:
    183
    Stop using a premium bot then until you figured out how to fix it ...
     
    JonFon1234 likes this.
  9. kawabungadk

    Joined:
    Dec 19, 2014
    Messages:
    230
    Likes Received:
    23
    same as the others for me too
     
  10. omgarock

    Joined:
    Jul 15, 2018
    Messages:
    16
    Likes Received:
    0
    Also having this issue, however with extreme hours of botting like 20ish hours but sometimes sooner.
    -EDIT: Read the logs, it seems to only happen when runescape updates, it somehow prevents your bot from starting again until you relaunch, or in my case restart your computer.

    Also if you're having issues with it charging you the best way around is to completely restart or you'll just keep running and stopping your bot.
     
    #10 omgarock, Aug 2, 2018
    Last edited: Aug 2, 2018

Share This Page

Loading...