someguy567 Posted October 5, 2018 Share Posted October 5, 2018 at er.h(er.java:60) at gx.al(gx.java:249) at ab.f(ab.java:36) at aq.as(aq.java:3760) at r.h(r.java:1383) at cl.f(cl.java:93) at client.fq(client.java:2712) at client.ap(client.java:928) at ai.al(ai.java:388) at ai.run(ai.java:367) at java.lang.Thread.run(Thread.java:748) Anyone know what this means? Quote Link to comment Share on other sites More sharing options...
FrostBug Posted October 6, 2018 Share Posted October 6, 2018 Means a thread running some obfuscated code threw an exception Quote Link to comment Share on other sites More sharing options...
Eagle Scripts Posted October 6, 2018 Share Posted October 6, 2018 Is this being thrown by an SDN script? If so; send the error to the script’s developer and he can de-obfuscate the cryptic message. Quote Link to comment Share on other sites More sharing options...
someguy567 Posted October 6, 2018 Author Share Posted October 6, 2018 (edited) How would I go about identifying the cause? It doesn't give any info on where to look. And no, it's my own script. Edited October 6, 2018 by someguy567 Quote Link to comment Share on other sites More sharing options...
someguy567 Posted October 7, 2018 Author Share Posted October 7, 2018 Just now, Alek said: Post the rest of the stack trace, you cut it off. That or it got spammed too much and you can't see the rest of it. The top of the message should say something like "Threw XYZ exception at ABC". That is literally the whole thing. The only other thing is the 'ea' just before it. Nothing else is shown. ea at er.h(er.java:60) at gx.al(gx.java:249) at ab.f(ab.java:36) at aq.as(aq.java:3760) at r.h(r.java:1383) at cl.f(cl.java:93) at client.fq(client.java:2712) at client.ap(client.java:928) at ai.al(ai.java:388) at ai.run(ai.java:367) at java.lang.Thread.run(Thread.java:748) Quote Link to comment Share on other sites More sharing options...
someguy567 Posted October 7, 2018 Author Share Posted October 7, 2018 10 hours ago, Alek said: It's missing something, so its getting cut off. Most likely the logger is being spammed, see if you can catch it right after it starts. I have the bot saving the log to a text file and I make sure it closes it when I get that error, so it is being caught straight after. Do you think this could be caused by having a weak proxy connection somehow? Quote Link to comment Share on other sites More sharing options...
someguy567 Posted October 8, 2018 Author Share Posted October 8, 2018 (edited) @Alek I removed the part where it uses the hop world method from the API and now I'm no longer getting this error. Does that help at all? Edited October 8, 2018 by someguy567 Quote Link to comment Share on other sites More sharing options...
Antonio Kala Posted October 9, 2018 Share Posted October 9, 2018 (edited) 2 hours ago, someguy567 said: @Alek I removed the part where it uses the hop world method from the API and now I'm no longer getting this error. Does that help at all? I'm using osbot's hopping api and it's working perfectly, can you post your code? Edited October 9, 2018 by Antonio Kala Quote Link to comment Share on other sites More sharing options...