Recent content by JarrYD

Awesome, nice find! Makes alot of sense. How would you go about converting public void encode(IoSession session, Object message, ProtocolEncoderOutput out) throws Exception { MapleClient client = (MapleClient) session.getAttribute(MapleClient.CLIENT_KEY); if (client != null) { byte[]...

Ohhh! Alright got you ahah sorry got confused with what you meant, Yep already implemented the fix for too many connections, patched alot of mem leaks and fix and updated the librarys. Thanks for the information, really interesting. Yeah dont think I'll go as far as to downgrade solaxia to v55...

Ah got you ahah thanks for that! Yeah have to change a lot of imports to Eg minacore io session etc. locations are different than that on v55 What did you mean by change sql connector class btw and downgrade to v55? Like what I've gathered is remove The old jar files added like minacore etc...

Awesome thanks for the tip! Just wondering where the sql connection class it, having trouble finding it atm

Ohh right, thanks for the reply :) So this would include doing things like cancel every scheduled and set to null when a client disconnects etc.?

Currently working on a v55 server. Main issue I'm wondering is what are the causes of server instability? What I mean by this is server seems fine after a restart but after about 2 days without restart upon login you will be dced after about 3 minutes. What causes this and is it probably best...

Fixed, coded a new rankingworker. Sorry /thread

Would there be an easier way to exclude item types from this. Like if I wanted to exclude shoes from showing? And can I define nx or non nx or does it have to be the whole shoes category? Thanks! public String EquipList(MapleClient c) { StringBuilder str = new StringBuilder()...

java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)...

Have a feeling too much time is being spend in garbage collector, not sure why, but used usegcoverheadlimit which I think may have resolved the problem. Is there a way to fix the problem or is just supressing it with this command ok?

Bump... Used xms 100m and xmx 700m still crashing

Just never had any issues with v55 used to be able to have it running for days. So new to these errors lolll. So the issue is that its using too much memory? Optimize the bats code?

Can have the server running for about 3 hours max and then after that the server crashes with an error There is insufficient memory for the java runtime environment to continue Native memoery allocation <malloc> failed to allocate 32744 bytes for chunkpool An error report file with more...

bump edited above, ^ helpppp

There aren't any errors, just an exception caught but no info. I think I may have fixed it though, I think there was an error in abstractmovementpackethandler. Thanks though!