3147647 - AS2 communication channel: Channel matched for incoming message… but channel is in Inactive state

You are using AS2 Adapter to configure some new interfaces in PI/PO system. Most AS2 communication channels are set as inactive state before go-live. You notice that some messages related to existing old interfaces are triggered even the new and old interfaces are configured differently, such as expected URL, subject and sender AS2Name. What's more, the AS2 communication channel shows warning like "Channel matched for incoming message... but channel is in inactive state".

XPI Inspector trace:
10:00:53:204    ⇨ with <4000c808-aea3-4d2f-8842-68da23cdcfc6@ECODAS2>
10:00:53:210  Thread[HTTP Worker [@447400742],5,D~ ~ler.PropertyHandler.PropertyHandler ⇦
10:00:53:210    ⇨
10:00:53:210   ~herServlet.getChannelsForRequestUrl state inactive of channel <AS2ChannelName> is not active
10:00:53:210   ~ra.api.pdu.AS2MessageId.getIdJoined ⇦
10:00:53:210    ⇨ with <6d72ec89-e685-45b5-904f-448d1fc2d1ad@ECODAS2>
10:00:53:222  Thread[HTTP Worker [@981144815],5,D~ ~ler.PropertyHandler.PropertyHandler ⇦
10:00:53:222    ⇨
10:00:53:222   ~herServlet.getChannelsForRequestUrl state inactive of channel <AS2ChannelName> is not active

• SAP NetWeaver
• SAP Process Integration

AS2 communication channel, AS2, Channel matched for incoming message, but channel is in Inactive state, Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX , KBA , BC-XI-CON-B2B-AS2 , Applicability Statement Protocol Adapter , Problem