We are having some occasional issues with a server application and Mad captures the exception but truncates the message ... well I think it is MAD that does, you might tell me other wise, although when we step through the code forcing a similar exception we can see the whole message. Here is an example of what's in the report:
exception class : EROInvalidStream
exception message : Invalid binary header. Either incompatible or not a binary message. <.h.t.m.l.>.<.h.e.a.d.>.<.t.i.t.l.e.>.I.n.t.e.r.n.a.l. .S.e.r.v.e.r. .E.r.r.o.r.<./.t.i.t.l.e.>.<./.h.e.a.d.>.<.b.o.d.y.>.<.h.1.>.I.n.t.e.r.n.a.l. .S.e.r.v.e.r. .E.r.r.o.r.<./.h.1.>.A.c.c.e.s.s.
any ideas gratefully received.
Thanks
Is there a way to extend the message length?
-
- Posts: 20
- Joined: Mon Feb 07, 2011 3:39 pm
Re: Is there a way to extend the message length?
From the top of my head I don't remember cutting the message length anywhere. Can you reproduce the problem on your development PC in any way?