Encountered a new phenomenon with the ace module and ssl termination.
Four separate contexts, one admin and three server farm contexts. All three server farms terminate ssl on the ace front side.
First of all everything worked like configured. But after a while the active ace stops responding to ssl handshakes. Switching a context from the active module to the hot standby module fixes the situation. Swapping it back again produces the same behavior - no ssl handshake/setup. My only known workaround is to reload the primary/active ace module.
The behavior started after i enabled the third context with ssl termination. It works on all server farm contexts for about 30 minutes under traffic and then suddenly stops. This is really strange!
I captured some sniffer traces for the ssl setup on the ace context itself in condition working and non working and also capture the same setup situation from a client with wireshark.
I don't think my config is the problem because everything works in the first place. The certificate stores are exactly the same on both aces for each context. In my opinion this is a serious bug.
Is this already known? Couldn't find anything in the bug tool. Any chance to get around this?
I already upgraded my modules to 3.0(0)A1(4a) so no chance to go higher with a new release.
Thanks for reading