Jump to content

Recommended Posts

Posted (edited)

Avoiding a ScheduledFuture task is a fancy way to "rest" your ThreadPool, although you have a vulnerable area (the one that you are doing db connection). This area can delay some times due to connection pool being busy or your query executing slow due to a lot of calculations. During that computation time (delay mentioned above) 2 or more threads (player clicks) can access this area at the same time aka multiple connections at the same time which will lead to duplicate data in your StringBuilder as StringBuilder is a not synchronized structure itself. You can either use StringBuffer, which is not prefered for the same reason CopyOnWriteArrayList is not prefered (slow writing operations) OR synchronize the vulnerable area. 

My suggestion:

 

private final Lock _connectionLock = new ReentrantLock()

private final void generateBuilder(...)
{
	if (!_connectionLock.tryLock())
		return;
	
	final StringBuilder sb = new StringBuilder();
	//probably more builders

	try
	{
		//connections and computations here

		_lastUpdate = System.currentTimeMillis(); OR _nextUpdate = ... (depends on your approach)
	}
	finally
	{
		//empty PVP/PK builder here
		//feed PVP/PK with the corresponding builder
		_connectionLock.unlock();
	}

 

During the vulnerable time this will return the old PVP/PK stored data when they are requested.

 

Also static fields are redundant in singleton classes so you can declare builders as

 

private final StringBuilder PVP = new StringBuilder();
private final StringBuilder PKS = new StringBuilder();

 

although CAPS is not a proper naming convention for those.

 

Edited by Zake
Posted
3 hours ago, Zake said:

This area can delay some times due to connection pool being busy or your query executing slow due to a lot of calculations. During that computation time (delay mentioned above) 2 or more threads (player clicks) can access this area at the same time aka multiple connections at the same time which will lead to duplicate data in your StringBuilder as StringBuilder is a not synchronized structure itself.

This code is used about one year in 3 server and never there existed any issue with duplicated StringBuilders. I will try to exploit and if I face that kind of issue I will update the share.

Posted
12 minutes ago, StinkyMadness said:

This code is used about one year in 3 server and never there existed any issue with duplicated StringBuilders. I will try to exploit and if I face that kind of issue I will update the share.

It's not quite easy to produce this with low population. You can always benchmark this. Fill your characters table with a lot of data, and create a bunch of db connection tasks to keep connection pool busy enough, so that you have time to execute 2 requests at the same time.

Posted (edited)
11 hours ago, Zake said:

It's not quite easy to produce this with low population. You can always benchmark this. Fill your characters table with a lot of data, and create a bunch of db connection tasks to keep connection pool busy enough, so that you have time to execute 2 requests at the same time.

I think the problem can be solved instant by just moving the "_nextUpdate = System.currentTimeMillis() + 60000L;" on top of the method so the Connection will not affect it as it will be instantly updated the _nextUpdate.

//Update (Can't edit first topic for some reason)
https://pastebin.com/RfmLz5ZW

Edited by StinkyMadness
Posted (edited)
7 hours ago, StinkyMadness said:

I think the problem can be solved instant by just moving the "_nextUpdate = System.currentTimeMillis() + 60000L;" on top of the method so the Connection will not affect it as it will be instantly updated the _nextUpdate.

//Update (Can't edit first topic for some reason)
https://pastebin.com/RfmLz5ZW

You may avoid duplicate connections this way, although if a new player asks for data while 1st one is still processing he will get temporarily an empty table. Even critical error maybe if table is half fed. You could remove final modifiers from your structures, then create temporary StringBuilders during connection time and change the address of the pvp/pk to these temps when they are fully fed.

 

Edit: gonna investigate about topic edit issue and let you know

Edited by Zake
Posted
12 minutes ago, Zake said:

You may avoid duplicate connections this way, although if a new player asks for data while 1st one is still processing he will get temporarily an empty table. Even critical error maybe if table is half fed. You could remove final modifiers from your structures, then create temporary StringBuilders during connection time and change the address of the pvp/pk to these temps when they are fully fed.

 

Edit: gonna investigate about topic edit issue and let you know

I guess the VPS/Dedicate has not that kind of issues on 2021.. they are not that slow.. also the empty StringBuilders not give critical error on the way the HTML is written.. maybe it will be empty but they can just reopen it 😄


i want to update the link on main topic but i can't edit it for some reason.

Posted (edited)
1 hour ago, StinkyMadness said:

I guess the VPS/Dedicate has not that kind of issues on 2021.. they are not that slow.. also the empty StringBuilders not give critical error on the way the HTML is written.. maybe it will be empty but they can just reopen it 😄


i want to update the link on main topic but i can't edit it for some reason.

May i suggest you post it on https://gist.github.com ?
So you can keep updating it and the link wont change.

Edited by ZaNteR
grammar smh...
Posted (edited)
5 hours ago, ZaNteR said:

May i suggest you post it on https://gist.github.com ?
So you can keep updating it and the link wont change.

I suggest @Maxtor to review a bit the privileges 😛 about people to be able to edit their topic 🙂
But thanks for the option

Edited by StinkyMadness
Posted (edited)
-	public void showRakingList(Player player)
+	public synchronized void showRakingList(Player player)

 

@Zake ReentrantLock is a bad way to solve this 'problem' and does not need to be placed here for many reasons. Indeed, it might be show different html content rarely even while StringBuilder is way faster than StringBuffer cause is fat since is syncing all of its methods, but all you have to do, is an object synchronization (if stinky still want to keep it as it is) but not by using the reentrantLock here, in this case...

 

@StinkyMadness I would do the whole thing a bit different, like a manager which will storing the infos in custom classes and generate the content directly up on the player's request with a FloodProtector check. No sync at all

Edited by melron

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



  • Posts

    • Update M54: Global HP/MP/CP consumable handling expanded beyond combat-only usage. Offensive mage idle recovery with learned skill Battle Heal. Spellhowler/Storm Screamer prioritizes Hurricane, using Vampiric Claw mostly below 90% HP. Major structural refactor initialized: Added category/class organization such as Archer, Dagger, Tank, Mage, Healer, Support and Specialized class files. Further structural cleanup. Extracted combat memory/state and more class-policy logic from the main controller. Added global stuck/inactivity watchdog for bots blocked by terrain/geodata. Added unreachable dropped ground-item timeout/temporary blacklist. Reworked Necromancer/Soultaker PvP: Dominator level 78+ maintains learned Arcane Power toggle on. Overlord/Dominator level 44+ maintains learned Soul Guard toggle automatically. Stability/scalability update: Bot controller ticks staggered instead of all starting in the same phase: Same 350 ms update rate retained Reduces simultaneous AI workload bursts. Removed the old manual aggressive-monster EVT_AGGRESSION bridge. Phantoms now use native Lucera setActive() behavior so monsters aggro them naturally. Reduced unnecessary NPC scans and native AI event pressure. Added saved-bot equipment overrides using a separate database table:         lucera_autobots_items Existing lucera_autobots remains the main saved-bot identity/state table. Equipment rows are linked to saved bots through bot_id. Added optional convenience view to show bot name together with equipment overrides:         lucera_autobots_items_view Added editable equipment slots in columns: Weapon Shield Helmet Chest Legs Gloves Boots Necklace Left/Right Earrings Left/Right Rings Equipment override values: 0 = use normal class/level profile item -1 = force slot empty >0 = equip that Item ID Custom equipment works only for saved database bots. Default class/level equipment profiles remain unchanged. Supports custom equipment from No Grade to S Grade, regardless of the bot's current level. Added validation for invalid item IDs and incompatible equipment slots. Added handling for: Two-handed weapons vs shields Full-body armor vs separate leggings Added all-grade Soulshots and Spiritshots to bot inventory/replenishment so custom lower-grade weapons still use the correct shots. Mage profiles that already use Blessed Spiritshots keep that behavior with all relevant grades available. First save the bot normally so it exists in table:         lucera_autobots Then open:         lucera_autobots_items Find the row with the same bot_id and edit only the equipment slots you want. Example: weapon_id = 6608 shield_id = -1 helmet_id = 0 chest_id = 0 legs_id = 0 gloves_id = 0 boots_id = 0 This means: weapon_id 6608 → custom weapon shield_id -1 → no shield all 0 values → keep normal default profile equipment After editing the DB, despawn and respawn the saved bot so M54 reloads its equipment overrides. Do not edit bot_id. Use it only to identify which saved bot the equipment row belongs to.   DOWNLOAD
    • It will be multi client so it will detect the client from the files and adapt the packets and asset loading. I am aiming for C4 and H5 after IL
    • this is just to simplify your life, time, and can be done for free by yourself just watch some tutorials, in case you don't wanna waste time check it out!   https://l2getwork.art   https://l2getwork.art/showcase.html  
    • Good job! Any chance for it to be downgradeable or at least compatible with older chronicles?
    • Fermata now runs in a web browser too. Try it here: https://web.fermata.gg/    
  • Topics

×
×
  • 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..