Understanding RestartLimit for non critical ressource

Hello,

we have some trouble with our oracle listener process. sometimes the listener is killed by vcs. We dont know why.

xxx VCS ERROR V-16-2-13027 (node1) Resource(lsnr-ORADB1) - monitor procedure did not complete within the expected time.
xxx VCS ERROR V-16-2-13210 (node1) Agent is calling clean for resource(lsnr-ORADB1) because 4 successive invocations of the monitor procedure did not complete within the expected time.
xxx VCS NOTICE V-16-20002-42 (node1) Netlsnr:lsnr-ORADB1:clean:Listener(LISTENER) kill TERM  2342
xxx VCS INFO V-16-2-13068 (node1) Resource(lsnr-ORADB1) - clean completed successfully.
xxx VCS INFO V-16-2-13026 (node1) Resource(lsnr-ORADB1) - monitor procedure finished successfully after failing to complete within the expected time for (4) consecutive times.
xxx VCS INFO V-16-1-10307 Resource lsnr-ORADB1 (Owner: unknown, Group: ORADB1) is offline on node1 (Not initiated by VCS)

However, Resource(lsnr-ORADB1) is set to non-critical, to prevent an failover.  I'll now set an RestartLimit for Resource(lsnr-ORADB1) to let the cluster try to restart the listener, but what happen if this failed? Will the Ressouce still staying offline or initiate the cluster an failover for the whole ResourceGroup?

thanks in advance for any help!