RE: Exception Thrown: java.lang.Exception: Unrecognized WBXML version

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

Traveler uses WBXML instead of regular XML to save on bandwidth (which is a good thing to do). When Traveler goes to turn the WBXML back into XML for processing, the WBXML is invalid and throws this exception.

From the looking at the data, it is not valid WBXML. This is normally caused by mismatched compression. The HTTP request should have Content-Encoding to indicate that the data is compressed. Then, Traveler must decompress the data before doing the WBXML conversion. If the Content-Encoding header is missing, Traveler will not try to decompress the data and will start with the WBXML conversion and fail. I have seen this most when proxies are in use and the proxy is stripping/losing the Content-Encoding HTTP header. This is the first place to look. You can enable the http thread logs to check the headers in HTTP (tell http debug thread all), and you can change the logging for the user to be FINEST and look in the Traveler servlet logs (http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Gathering_log_files_for_support_LNT853).

Feedback response number RSSN8PXJCN created by ~Michelle Umapuloni on 12/27/2011

Return to top

Exception Thrown: java.lang.Excepti... (~Wei Umkizenako... 27.Dec.11)

. . RE: Exception Thrown: java.lang.Exc... (~Manny Ekrevero... 27.Dec.11)

Printer-friendly

Search this forum

Member Tools

RSS Feeds

RSS feeds

	All forum posts RSS
	All main topics RSS