On releases older than 3.0, such a crash could cause schema transformer to lose some 'in-flight' messages from ifmap server. As a result, those messages won't be processed resulting in lost functionality until schema transformer is restarted.
This problem is not there in 3.0 or later because schema transformer does not drop any in-flight messages. However, the traceback still needs to be handled in api server.
On releases older than 3.0, such a crash could cause schema transformer to lose some 'in-flight' messages from ifmap server. As a result, those messages won't be processed resulting in lost functionality until schema transformer is restarted.
This problem is not there in 3.0 or later because schema transformer does not drop any in-flight messages. However, the traceback still needs to be handled in api server.