Jump to content
  • 0

Problem in L2J Please help!!


Question

Posted

Hi.I have a problem with my server.I start my server and it starts normally.Now when I try to login from a local PC my ping is always 5.Server is live and for anyone who tries to login ping is 5 again.And after about 4-6 hours server stops working.It stucks.In the past I didn't have this problem.For example when I was logging from my local PC the ping was 0 or 1.And if another person was trying to log in his/her ping was different and server was working fine.Can anybody tell me how can I solve this problem?It came up when I added Scheme Buffer and some other NPCs.I removed them but nothing.Any help?My main question is : My problem is the ping (always 5) or something else?

 

Thanks a lot for your time.

9 answers to this question

Recommended Posts

  • 0
Posted

I think your problem is RAM.

 

You using l2j freya, right? I think you using bad java specs inside .bat files and your server crashes, because of RAM memory. Read the logs, there you will find the problem.

  • 0
Posted

usually, a personal computer isnt enough to run a l2jserver, moreover if you run any l2 client in such computer as well.

A probe of that is that local network should have 0 ping and is exhasuted enough to have a 5 ms delay

  • 0
Posted

First thanks a lot for your time guys.Now I don't think the problem is my RAM because I had my server online for a long time in the past and it never crashed.It start crashing when I add some custom NPCs...Like GrandBoss manager, scheme buffer, pvp-pk manager and noblesse master.I removed them but nothing.Do I need to start my server all over again ?I mean do I need to delete my current datapack sql database (after keeping a backup) and start all over again?And yes my server used L2J Freya.Thanks again guys.

  • 0
Posted

those scripts perform connections to database

 

example

Connection con = null;
try
{
con = L2DatabaseFactory.getInstance().getConnection();
// Do stuff...
}
catch(Exception e)
{
}

 

and, at the end they dont close the database like this:

finally
{
L2DatabaseFactory.close(con);
}

 

or like this

finally
{
try
{
	if(con != null)
		con.close();
}
catch(Exception e) {}
}

  • 0
Posted

Unclosed connections are automatically verified through ConnectionCloser (if you use reworked IL or post IL you should have it). Avoid to use Python buffers, or even Python, at all. You got 0 lisibility if it got errors.

 

If your server is reachable by anyone, verify about logs. It can be some packet floods.

  • 0
Posted

Unclosed connections are automatically verified through ConnectionCloser (if you use reworked IL or post IL you should have it). Avoid to use Python buffers, or even Python, at all. You got 0 lisibility if it got errors.

 

 

If your server is reachable by anyone, verify about logs. It can be some packet floods.

No I tried everything but no result.What should I do guys please.I deleted all of my files and set them up again but nothing.I am thinking of formating my PC and start all over again.Any ideas?

P.S : I am using Rind4s buffer.It is a scripted Scheme buffer.Should I upload it and see if there is a problem there?Now about "Unclosed connections are automatically verified through ConnectionCloser (if you use reworked IL or post IL you should have it" and "If your server is reachable by anyone, verify about logs. It can be some packet floods" What does this means and how can I found if the problem is there?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..