Bug #25921

MYSQL wrapper crash opportunity

Added by Jman over 5 years ago. Updated about 5 years ago.

Status:Closed Start date:10/27/2011
Priority:Normal Due date:
Assignee:Jman % Done:


Target version:-


MYSQL wrapper crashes when the client disconnects then reconnects within a very short period of time say 2-3 seconds.
This crash opportunity has only happened once in several months of testing.

On investigation of the client and server logs this is due to the onPlayerDisconnected eventhandler script not completing it's running MYSQL tasks before the client reconnects and invokes the onPlayerConnected eventhandler script's MYSQL tasks. The clients pipe is not available.


Updated by Jman over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

On further investigation this issue is related to http://dev-heaven.net/issues/25281
Workaround implemented. Will reopen if issue reoccurs.

Updated by Jman over 5 years ago

Related issue link revised

Updated by Jman over 5 years ago

  • Status changed from Resolved to Feedback

Updated by firefly2442 over 5 years ago

Did you code a workaround to check for this? Is it just that on the Arma scripting side it doesn't know how to handle null return values from MySQL?

Updated by Jman over 5 years ago

It's instigated on the serverside when the player's onPlayerDisconnected script is triggered, launching a MYSQL call and then the player's onPlayerConnected script is still waiting for it's MYSQL result. As I say this crash opportunity is very rare and only happens if the player disconnects whilst the player's onPlayerConnected event has not yet returned. As to why the wrapper actually crashes I've no idea and to repo this is very hard to do since the onPlayerConnected and onPlayerDisconnected eventhandler MYSQL calls normally return a MYSQL result within one second. If it's a generic error caused by a null return value and the wrapper crash can be caught then that would be ideal. If I can repo this again I'll post the wrapper crash output.

Updated by Jman over 5 years ago

  • Category set to PersistentDB
  • Target version deleted (Version 1.0b)

Updated by Jman about 5 years ago

  • Status changed from Feedback to Closed

No longer relevent since persistentDB now uses Arma2NET with the Arma2NetMySQLPlugin

Also available in: Atom PDF