Hi Madhav,
Is EOIO mandatory for your scenario?. If not, you could uncheck EOIO in ICO's Interface Determination step
Regarding your issue:
As far as I understand, sometimes messages fail due to a temporary glitch at adapter level and due to this EOIO interface messages stuck in holding status. The temporary glitch error message either get's restarted automatically with a defined job (or) due to manual restart action. And hence EOIO stuck messages need a manual restart, since there is no automatic job for restarting such holding status messages
Best Regards,
Praveen Gujjeti