Unsupported record version Unknown-47.115


A commonly logged error from openfire




Daryl Herzmann
December 13, 2016, 8:33 PM

This "issue" is back again, a current master build WARN log entry

Guus der Kinderen
December 17, 2015, 12:14 AM

The change in this PR should make the exception message more descriptive:

Guus der Kinderen
December 8, 2015, 8:53 PM

What the RFC is not clear on is what the initiating party should do in both instances. Where the receiving party is closing the socket without sending data, it's probably best to not send data as the initiating party either?

Guus der Kinderen
December 8, 2015, 7:51 PM

I am experimenting with a fix in this pull request:

Guus der Kinderen
December 8, 2015, 6:29 PM

So, according to RFC6120, there is a significant difference between:

  • section Failure Case, such as malformed commands and internal server errors.

  • section STARTTLS Failure, which includes TLS errors such as bad_certificate or handshake_failure.

There is an important difference in how the receiving entity should respond. section Failure Case states:

MUST return a <failure/> element (...) close the XML stream, and terminate the underlying TCP connection.

On the other hand, section STARTTLS Failure reads:

MUST terminate the TCP connection (...) MUST NOT send a closing </stream> tag before terminating the TCP connection

I don't believe that Openfire makes a distinction between Failure Case and STARTTLS Failure: STARTTLS is assumed successful, unless an exception is thrown. Handling of both cases is probably similar in each implementation (S2S and C2S have different implementation) - from what I gather (in, Openfire always sends a <failure/> element.

Is the root cause of this issue the lack of distinct handling of both cases?



Guus der Kinderen


Daryl Herzmann