(AFAIk) There is no tool (as in Kernel for background job) to update session status later, once an execution is "wildly" broken (system shut down, process canceled from SM04/SM50 or interactively.) the session keeps its status forever, and forever can be long. The example you provided look as if someone tested the BDC and try to interrupt the transaction (with success...)
Hint: Don't use session for CAT2, better use the (already existing in 4.7) following BAPIs: BAPI_CATIMESHEETMGR_INSERT, DELETE and CHANGE (give the info to your dev.)
Regards,
Raymond