Hi, I contact you because I have a question about gsoap. I use it for an application to transmit messages from a Linux system (Fedora Core 6) to a Windows XP machine. I encounter some problems on the Windows side. The system transmits about 500.000 messages a month and for some reason the windows side freezes around every three of four weeks. It seems to stop (not crash, just block) in the deserialization of the message to a struct. That is somewhere in the soap_serve. I have a debug message just before soap_serve which I can see and a message in the implementation of the function described in my WSDL (my own implementation) which I do not see, so somewhere in the soap_serve it freezes (or gets in an infinite loop). I use gsoap version 2.7.9f and the main reason I do not want to step to the latest version is because I use the Borland C++ compiler and need to patch the generated code enormously to remove the warnings from the code. Apart from that, I did not find an entry is the changelog indicating this error was solved. I have been looking at the code for some time and cannot quit find what I am looking for, I was wondering if you could give me a lead. The soapserver application I build retreives the soapmessage, then deserializes it using the soap functions and delivers it to my own code which first serializes the struct to a string again because on this side I use the information further as a string. This sounded to me like a step I could skip. And since the error (freeze) I encounter in my application which seems to be in the deserialization step I would like to skip this step.
Is there a way to retreive the message that was send from the soapclient directly after the "soap_accept" function has received the message? I have not found the message as string somewhere in the soap- struct. I would be of great help for me if you could give me some kind of hint or direction where to look in the code or what function to use for this.
