Forum Multiplayer Timer issues after long running instances

Discussion and help relating to the PlayerIO Multiplayer API.

Timer issues after long running instances

Postby Retimer » May 19th, 2015, 6:49 pm

Just a theory here, but I run timers on all rooms for checking for maintenance (to shut them all down when needed for an update), and in two separate projects, some instances that have been running for say 1-2 weeks, they aren't getting shut down during a maintenance.

There are no errors associated with it not shutting down, it's simply as if the timer just stopped working in those rooms...

Furthermore, those rooms are not processing database object savings properly. A lot of weird occurrences seem to be occurring around rooms that are open for long periods; my assumption is memory leaks, or communications simply breaking between the rooms and pIO/Gamesnet.

My solution since then was to have guild rooms auto reconnect all users every day after 4am, however this is not a solution that I can use on all room types, and was wondering if anyone else has run into this weirdness or had other insights?
Retimer
Paid Member
 
Posts: 14
Joined: March 9th, 2013, 2:53 pm

Return to Multiplayer



cron