SourceForge has been redesigned. Learn more.

#6 Player Lockup Prevents ACK on Command Handler

Current Release

If the player locks up, we are unable to return confirmation that a command has run (because we can't run it to completion), and we never return an ACK. This can freeze other programs dependant on the socket output.


  • Kevin Croker

    Kevin Croker - 2007-12-13
    • milestone: --> Current Release
  • Kevin Croker

    Kevin Croker - 2008-01-23

    Logged In: YES
    Originator: NO

    The only way I can think of to handle this is implement some sort of timeout everytime we try to invoke a player command. If the player command does not return in a timely fashion, we except to allow things downstream to flow, and perhaps restart the player?

  • KWUR Tech

    KWUR Tech - 2009-04-16
    • assigned_to: nobody --> jacob_evans
  • Kevin Croker

    Kevin Croker - 2010-01-15
    • priority: 5 --> 1
    • assigned_to: jacob_evans --> kwurtech
    • status: open --> open-out-of-date
  • Kevin Croker

    Kevin Croker - 2010-01-15

    This is not a huge issue now because the new player does not lock up :D
    Still, this is something that should be dealt with, probably via a timeout


Log in to post a comment.