[Help] How to fix? L2J

[n0ah]

well, i have an l2j server. And i have some problem. There are some annoying cheaters, who send packets, which make my server laging. Here is the log:

2007.01.27 13:05:51,937 WARN Timer-0 com.mchange.v2.async.ThreadPoolAsynchronousRunner com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@fe1837 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
2007.01.27 13:06:03,000 WARN Timer-0 com.mchange.v2.async.ThreadPoolAsynchronousRunner com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@fe1837 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@16a53bb (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@19f594a (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@9f0a1b (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@15074fb, com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@1303eb4, com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@649e15, com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@1c68656]
2007.01.27 13:07:24,937 WARN Timer-0 com.mchange.v2.async.ThreadPoolAsynchronousRunner com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@fe1837 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
2007.01.27 13:07:24,937 WARN Timer-0 com.mchange.v2.async.ThreadPoolAsynchronousRunner com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@fe1837 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@17ac8b3 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1), com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@e7d40 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@1410b58 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@14ff56a, com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@794165]
2007.01.27 13:23:05,046 INFO main com.mchange.v2.log.MLog MLog clients using log4j logging.
2007.01.27 13:23:05,140 INFO main com.mchange.v2.c3p0.C3P0Registry Initializing c3p0-0.9.0.4 [built 23-January-2006 22:20:29 -0500; debug? true; trace: 10]
2007.01.27 13:23:05,453 INFO main com.mchange.v2.c3p0.PoolBackedDataSource Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@1546e25 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@4741d6 [ acquireIncrement -> 5, acquireRetryAttempts -> 0, acquireRetryDelay -> 500, autoCommitOnClose -> true, automaticTestTable -> connection_test_table, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 4741d6, idleConnectionTestPeriod -> 60, initialPoolSize -> 3, maxIdleTime -> 0, maxPoolSize -> 10, maxStatements -> 0, maxStatementsPerConnection -> 100, minPoolSize -> 1, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@12152e6 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 12152e6, jdbcUrl -> jdbc:mysql://localhost/l2jdb, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 300, testConnectionOnCheckin -> true, testConnectionOnCheckout -> false, usesTraditionalReflectiveProxies -> false ], factoryClassLocation -> null, identityToken -> 1546e25, numHelperThreads -> 3 ]

How it can be fixed?

 

[Gibs]

Update to Rev 191 of Hero or the latest pack of ur serverpack u use.Hlapex or any packet exploiter doesnt work in the latest Revs on any pack.

 

[n0ah]

but i use 191 revision.

 

[Droppo]

that's only a problem of a server running out of resources... increase the ammount of memory for the server...

Droppo.-

 

[jujogual]

yes but i have any promblem similar somethimes the skills of my server fail why????

 

[fliperizzz]

ctrl+alt+delete and do java priority high....

 

[jujogual]

But why is happeing it??? i kwon people that they dont put the high priority and they have a great skills....

I must do it always????

 

[n0ah]

that's only a problem of a server running out of resources... increase the ammount of memory for the server...

Droppo.-

half of all memory is free

 

[Droppo]

half of all memory is free

Yeah... but l2jserver is kinda stupid if you want, and if you don't tell him how much to use it won't use more than 512MB even if you have 4GB of ramm

Droppo.-

 

[George]

But why is happeing it??? i kwon people that they dont put the high priority and they have a great skills....

I must do it always????

you must do it if you want some bugs fixed

Yeah... but l2jserver is kinda stupid if you want, and if you don't tell him how much to use it won't use more than 512MB even if you have 4GB of ramm

Droppo.-

exactly
edit and set to a higher value