problem syn/ack to client Instead of RST

We are having an issue with this as well. We route Tibco EMS through 2 VIP's to allow us to update EMS servers without effecting client configurations (as each client knows the DNS names of the two EMS hosts). We also terminate the SSL connection on the LTM using our PKI signed certificate. To do this we had to change from Performance L4 type, to Standard type. This causes the SYN, SYN-ACK, ACK, RST behavior when the EMS server is down (pool is unavailable). The Tibco EMS client is expecting SYN, RST, and when it doesn't follow that path, the Agent thinks the server is up, but can't talk to it. It then fails to try the secondary server. I am thinking this is a Tibco Client bug, but it would be nice to address this on the LTM.

We could go back to Performance L4 and move the certificate and prvate key to the EMS servers. This seems to be my best option at the moment.

Ideas?

DeVon