ResendRequest message ( 35=2) received from Sender was ignored in QuickFIXJ

Fix session was interrupted due to network issue... Both side FIX processes ( Client, Sender) did not know about the n/w issue. The Client side was continuously sending logon request to other side... Once the n/w issue was resolved the connectivity was established. However, the sequence was not in sync at this time . Hence , The sender sent resend request (35=2) immediately after successful logon response.
But this 35=2 request was not processed by quick fix engine at my side ( Client side). I can see the message in quickfix messages.log arrived from sender but not traceability on what had happened with this message.
Only what i can see , the Client side ( fix engine) sent 35=2 for which the sender has responded with sequencereset i.e., 35=4. I think , the sender on the other side responded well with the Admin messages sent by my quickFix engine.

the problem is why my fix engine (i.e., the client ) did not respond to 35=2 resent request given by sender ? . I am expecting my Fix engine should have responed with 35=4 like my Sender's engine . I am using QuickfixEngineJ 1.5.3

Some one kindly help please. The below the sequence of FIX messaged traced in messages.log/

Response from Sender:
8=FIXT.1.19=72 35=A 34=75098 49=456 52=20190516-23:30:20.382 56=123 98=0 108=30 1137=9 10=178

Resent request from sender ( problem where I did not respond for this message)
8=FIXT.1.19=66 35=2 34=75099 49=456 52=20190516-23:30:20.38256=123 7=74910 16=0 10=154

Resent request from Client (i.e., by my quick fix engine )
8=FIXT.1.19=66 35=2 34=74963 49=123 52=20190516-23:30:20.436 56=456 7=75019 16=0 10=154

reset request responded by sender:
8=FIXT.1.19=99 35=434=75019 43=Y 49=456 52=20190516-23:30:20.489 56=123 122=20190516-23:30:20.489 36=75100 123=Y 10=043