If your web service calls involve uber-uber-huge SOAP request messages,
yes, memory errors could potentially be kicking in (although it is rare
that SOAP calls get *that* huge). What I would recommend doing is using
Wireshark[1] to trap the SOAP request of a message that raises this
exception, than copy that SOAP request into soapUI and try to replicate
the error.
Once you can replicate it via soapUI, more detective work is needed.
Get that SOAP request to the smallest possible SOAP request that
replicates the error--it could be that it's not the size being the error
but some strange incoming character that is causing the marshalling
error to occur. Or, as Dan wrote, it may be that the web service is
fine, it's always accepting whatever soapUI feeds it but your actual
customer's SOAP client is timing out.
Is it weblogic[2] related? Possibly, as it may use different parsing
libraries than vanilla Tomcat would. Another potential check is to run
your webservice on Tomcat[3] and see if the error repeats there.
HTH,
Glen
[1] http://www.jroller.com/gmazza/entry/soap_calls_over_wireshark
[2] http://www.jroller.com/gmazza/entry/deploying_webservices_on_weblogic
[3] http://www.jroller.com/gmazza/entry/web_service_tutorial
On 02/13/2012 10:41 AM, fachhoch wrote:
Please advice me what could cause this error ? is this anything to do with
weblogic ? Anything with heap size ?
--
View this message in context:
http://cxf.547215.n5.nabble.com/Unknown-server-error-MarshalException-tp5473778p5479605.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza
