1. Welcome to LilyPad. Download the project, explore the forums, and create your own LilyPad network.


    If you use the software and enjoy it or have a question, or would like to contribute to the future of the software directly or through resources, please sign up and join our little community.

Lilypad Proxy keeps crashing?

Discussion in 'Support' started by KrashDozer, Jun 17, 2013.

  1. KrashDozer

    KrashDozer New Member

    Code (text):
    [Connect] Connected to the cloud
    java.lang.NullPointerException
            at lilypad.server.proxy.net.ProxySession.inboundAuthenticate(ProxySession.java:107)
            at lilypad.server.proxy.net.ProxySession.inboundAuthenticate(ProxySession.java:73)
            at lilypad.server.proxy.net.ProxyInboundHandler$1.run(ProxyInboundHandler.java:125)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
            at java.lang.Thread.run(Thread.java:722)
     
    K thats what I get then I restart and people can connect again. Or it says my server is offline. When I know its not there are people on it. It doesnt kick people off just noone can connect. Two different errors:
    Cant authenticate, and Server is offline errors...
    Any assistance would help. I am on build 24 of Proxy
  2. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Are you running a Distributed or AllInOne setup?
    What is your LilyPad version?
    Have you tried updating to the latest version?
    What is your Java version?
  3. KrashDozer

    KrashDozer New Member

    Running distributed, Now version 22 of the distributed proxy, I have tried to run the latest as my first post said, but I had to restart the Lilypad instance 16-17 times. in a day.... Java version is 1.7
  4. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Please use the latest builds and tell me how it goes.

    The instability was most likely caused to bugs in Netty 4 CR3
  5. KrashDozer

    KrashDozer New Member

    I have used the latest builds, at least with the older builds I dont have to remain in a ssh connection with the server. The latest = me having to stay at my computer to restart the instance every 30 minutes or so. Build 22 Maybe once a day.
  6. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Have you tried build #30 (being the latest?)
  7. KrashDozer

    KrashDozer New Member

    Ill try it now and see if it fixes the issues
  8. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    Be sure to update your Connect and Query server too so you can get the full extent of the latest builds.
  9. KrashDozer

    KrashDozer New Member

  10. KrashDozer

    KrashDozer New Member

    [LilyPad] build 30 of Proxy
    [Connect] Connected to the cloud
    Jun 17, 2013 9:06:32 AM io.netty.util.concurrent.SingleThreadEventExecutor runAllTasks
    WARNING: A task raised an exception.
    java.lang.IllegalStateException: complete already
    at io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPromise.java:400)
    at io.netty.util.concurrent.PromiseTask.setFailureInternal(PromiseTask.java:61)
    at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:145)
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:353)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:365)
    at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)
    at java.lang.Thread.run(Thread.java:722)
    Caused by: java.lang.IllegalStateException: complete already
    at io.netty.util.concurrent.DefaultPromise.setSuccess(DefaultPromise.java:382)
    at io.netty.util.concurrent.PromiseTask.setSuccessInternal(PromiseTask.java:80)
    at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:125)
    ... 4 more
  11. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    You can ignore that exception as it is not fatal and is most likely caused by a breaking Netty update. I have yet to find the cause of it although I've been looking, but it doesn't seem to cause any issues.
  12. DJNinjaCrash

    DJNinjaCrash New Member

    Distributed is really buggy for me, The proxy crashed every hour and when a server restarted you get a weird authentication error.

    I Highly recommend switching to the AllInOne Setup while these bugs are being fixed.
  13. Coelho

    Coelho Software Engineer Staff Member Administrator Maintainer

    There is no known bugs with distributed setups. If anything, this is your fault for not submitting bug reports.
  14. DJNinjaCrash

    DJNinjaCrash New Member


    I'm not saying it was anybodies fault, Blaming people is going to make things 10x worse.
    Everything has bugs, even the biggest in production hardware, I do not spam the forums .ect complaining about it because i know they are probably fixing it and the last thing they need is somebody spamming them about it as i know from experience with the ShadowBlockz Network.

    I am unsure if it is a bug because no errors are shown, I will try and look into it further but at the moment it is not needed.
    All i am trying to do is help out my fellow confused owners who have had the same issues i have with the software.
  15. boboman13

    boboman13 Member Contributor

    The developers usually don't know something is wrong unless someone tells them, and if everyone acts the same than nobody will make the software better.

Share This Page