ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-01-30 16:14:39 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

ENT-3504 Do not throw exception for missing fiber and log instead - OS version

Browse Source 
Change to `SingleThreadedStateMachineManager`.

Instead of throwing an exception when a flow's fiber cannot be found,
just log the message at info level.

(cherry picked from commit 70b2a94fda4e1b4f4ee7aff2e369d87fb1c9f7f5)
This commit is contained in:
Dan Newton 2019-07-16 11:31:37 +01:00 committed by LankyDan
parent 6913a80fc4
commit 8ac472b933
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
node/src/main/kotlin/net/corda/node/services/statemachine/SingleThreadedStateMachineManager.kt
View File

@ -452,12 +452,12 @@ class SingleThreadedStateMachineManager(
}
} else {
// It happens when flows restart and the old sessions messages still arrive from a peer.
logger.info("Cannot find flow corresponding to session ID $recipientId.")
logger.info("Cannot find flow corresponding to session ID - $recipientId.")
}
} else {
val flow = mutex.locked { flows[flowId] }
?: throw IllegalStateException("Cannot find fiber corresponding to ID $flowId")
flow.fiber.scheduleEvent(Event.DeliverSessionMessage(sessionMessage, deduplicationHandler, sender))
mutex.locked { flows[flowId] }?.run {
fiber.scheduleEvent(Event.DeliverSessionMessage(sessionMessage, deduplicationHandler, sender))
} ?: logger.info("Cannot find fiber corresponding to flow ID $flowId")
}
} catch (exception: Exception) {
logger.error("Exception while routing $sessionMessage", exception)