Limited # of connections to DB with new build?
 

Not sure if this a problem with shared memory.

But, updated to the new shared memory code.

Now, I can load 32 zones but after that, the rest keep recycling with this:

---------------------------------------------
[04.08. - 09:47:25] Starting Log: logs/eqemu_error_zone_0452.log
[04.08. - 09:47:25] Failed to connect to database: Error: #2013: Lost connection to MySQL server at 'waiting for initial communication packet', system error: 22

btw, this runs on two servers. no problem until then.

DB on one server, game runs on another.

I just checked on my MySQL admin and it shows the remainder of the users trying to login as "unauthenticaed User"

Could this be because of 32 is the limit somewhere?

edit: just changed dynamic count to 32, stopped the looping of zone.exe logins and the "user connection" count in mysql dropped off all of the "unauthenticated users"

I second this on my XP server with the latest builds. There's a point where I have to reboot because the server gets caught up in an endless loop of rebooting launch zones and dynamic zones. When that happens everyone gets trapped in their current zone because all other zones are "Unavailable".

I noticed my client usage (Both UF and RoF) have exploded into 600-700 MB footprints too. Before they hovered around 150-200. Not sure if that's related but thought I'd throw that out there.

I don't remember having this issue before shared memory. Just an observation and additional feedback if it helps to troubleshoot.

The size problem is probably you're building debug modules, instead of release.

I don't think that's it because I use the Configuration Manager quite religiously to specifically use Release files for the entire build routinely.

I've noticed this size increase with my clients as well... (UF and RoF)

I'm trying to trace down another issue atm, that may or may not be related...