I'm using AXIS2 and I'm getting the following error message - I know the reason for it. I can see the whole error message when sniffing the traffic with wireshark:
Unexpected character 'S' (code 83) in prolog; expected '<' Whenever there is an AxisFault or an error like that I have to start up wireshark and sniff the traffic since the stack trace only logs the first character in the error message. This is ok for now but for productional environment this will be very difficult. In case a one-time error will occur that I'll not be able to reproduce, I'll not have any idea what went wrong :confused:. Does anyone have any suggestions or know if it is possible to retrieve whole server response error message and log it? Besides stack trace I would like to see the actual server response from which I'll know the actual error, i.e.: "Server was unable to process request. ---> Exception has been thrown by the target of an invocation. ---> The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100." Any help would be grately appreciated. Regards, Lidija -- View this message in context: http://www.nabble.com/AxisFault-Unexpected-character---retrieve-whole-server-response-error-message-tp21214129p21214129.html Sent from the Axis - Dev mailing list archive at Nabble.com.
