Log message "Cannot find flow corresponding to session" should not be a warning

Description

It happens when flows restart and the old sessions messages still arrive from a peer. Should probably be INFO.

[WARN ] 2019-02-15T05:34:54,976Z [flow-worker] statemachine.MultiThreadedStateMachineManager.onExistingSessionMessage - Cannot find flow corresponding to session ID SessionId(toLong=6672999284068293558). {actor_id=corda, actor_owning_identity=OU=Corda, O=Perf-10.155.0.4, L=London, C=GB, actor_store_id=NODE_CONFIG, fiber-id=15555339, flow-id=f4a21271-d04a-4ff5-8a47-59a10f177dc9, invocation_id=9a7be347-16d4-4289-9de6-789f2c110151, invocation_timestamp=2019-02-15T05:34:32.916Z, origin=corda, session_id=2909c1cd-008e-478e-9821-26e5c6445fa9, session_timestamp=2019-02-15T03:05:09.403Z, thread-id=722, tx_id=FC8815B6D12AD0C866B839C6911ABD3DB4EF6CA29846F3860BC74B31259262CC}

Status

Assignee

Katarzyna Streich

Reporter

Rick Parker

Labels

None

Priority

Medium

Fix versions

Ported to...

None

Feature Team

Corda Core

CVSS Vector

None

Severity

Medium

Affects versions

Configure