https://issues.apache.org/bugzilla/show_bug.cgi?id=56299
--- Comment #6 from Martin Studer <[email protected]> --- Forgot to mention that after having received that error, retrying to connect generally seems to work (In reply to Martin Studer from comment #5) > We were using 2.4.7 before and ran into the "infinite loop" issue > https://issues.apache.org/bugzilla/show_bug.cgi?id=56145 which led us to > upgrade to 2.4.9 (without trying 2.4.8 first). > > The behavior we are observing is that websocket connections initially work, > however that reopening the connection after a while leads to a "AH02447: > err/hup on backconn". This leads to the following error on the client side > (Google Chrome): > > WebSocket connection to 'wss://...' failed: Connection closed before > receiving a handshake response > > > > (In reply to Eric Covener from comment #1) > > Weird, the 2.4.9 change here did not introduce this error or increase its > > severity. I actually noticed that it seemed to be at an unnecesarrily high > > level, and the corresponding msg for the client side is TRACE1 instead of > > NOTICE. > > > > Was 2.4.8 just unusable for you so you never saw it? Just trying to make > > sure this is simply "is NOTICE too high?" vs. "broke in 2.4.9" -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
