Loïc Minier wrote:
Hi,Thanks for the patch and the investigation! What I don't understand is why I ran into this only one time. All messages I send to Mbuni are created by an application from scratch (ie. no headers are inherited from the Internet), and it doesn't set headers such as X-Mms-Transaction-Id (which might be the reason why it crashed in the first place): only X-Mms-Expiry is set.
now the X-Mmms-Transaction-Id is of course not transmitted in plain text, but as WBXML token. Mbuni decodes the known token. But it's value seems to be invalid.
I'm a bit surprized it only happened once, not for all messages, or when the problematic message was resent. :-/
good point, no idea how this happened "one time". BTW, this was via HTTP proxy transported, hence no Kannel WAP GW running in between? Would be great if we have the actual byte-content flowing to Mbuni as either wapbox.log or ethereal capture to analyze.
Stipe _______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
