May 30 09:10:35 JTAC rpd[2880]: RPD_RSVP_NBRDOWN: RSVP neighbor a.b.c.e down on interface aex.1 nbr-type Direct, neighbor timeout

May 30 09:10:35 JTAC rpd[2880]: RPD_LDP_SESSIONDOWN: LDP session a.b.d.f is down, reason: hold time expired

May 30 09:10:40 JTAC rpd[2880]: RPD_RSVP_NBRDOWN: RSVP neighbor a.b.c.g down on interface aey.1 nbr-type Direct, neighbor timeout

As per available logs, the RSVP/LDP neighbors went down immediately after the protect filter commit.

In the protect filter, there are no explicit terms for RSVP/LDP.

The default action, when there is no default term defined in filter, is to discard all traffic.

https://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/concept/firewall-filter-stateless-evaluate-packets.html

• "If the packet does not match any term in the firewall filter, the device implicitly discards the packet. "

So when there is no RSVP/LDP terms defined, the filter discarded those packet, which caused the session down. 

The RSVP/LDP sessions came up when the config rollback was done & commit was applied.