Deadlock when AR is aborted during AR-Startup

If an AR is aborted at the time the Connect Req is still handled, the Protocol Stack might become stuck with CMSU waiting for Close of the Statemachines. The problem can be triggered with the following setup:

• An application which performs check indication handling (e.g. enable all check indications). The Check Responses must be generated with some delay
• Profinet IO Tester V2.2 (new Release) CMDEV Testcases

The problem is mainly triggered by the AR RERUN Abort Case. The CMDEV Testcases should be run repeatedly until the problem occurs