I have a web service which I send files to, when I send a file of 5m or more, I get a javax.xml.soap.SOAPFaultException. I am deploying my webservice with Weblogic 8.1.
Monitoring the Client and Server memory usage, I notice that the Client JVM Memory heap spikes when the client serialises the java into XML, and then the Server JVM spikes when it attempts to serialises the XML back into Java.
Hi Ulf it returns 500 error code (Internal Server Error). Looking at the net it seems that it is better to pass files as attachments rather than in the message body.
Since I am passing a array of string, I will have to use a DataHandler.
Is it a case of in the calling client program, I transfer the Array of String into a DataSource, wrap it in a DataHandler, pass the DataHandler as a parameter and in the server extract the datahandler and the datasource.
I think in Weblogic if they see a parameter as a DataHandler it is treated automaticaly as a attachment and I do not have to add anything to the servicegen.