ClientDispatcher.java is throwing a out of memory exception in the client application logs.
I cannot find any exception on the server side logs.
This laeds me to believe that ClientDispatcher.java is responsible for serialising the remote object into XML before it sends it over HTTP to the server.
Am I correct, or is ClientDispatcher.java part opf the identify or deserialise operation on the server side.
Thanks for any help
Tony =================================================================================== Exception Class...:uk.gov.ir.eric.SystemException Conversation ID...:SA100_POS_01-ATT-5mb.xml Exception Message.:IOException Failing Class.....:uk.gov.ir.eric.attachmentSeperator.AttachmentSeperator Failing Method....:seperateAttachment Failing File......:AttachmentSeperator.java Failing Line No...:103 Previous Exception:java.rmi.RemoteException The source of this problem is shown below =================================================================================== Exception Class...:java.rmi.RemoteException Exception Message.:SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.OutOfMemoryError (see Fault Detail for stacktrace) Detail: <detail> <bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.lang.OutOfMemoryError </bea_fault:stacktrace> </detail>; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Exception during processing: java.lang.OutOfMemoryError (see Fault Detail for stacktrace) Failing Class.....:uk.gov.ir.eric.webservice.antivirus.client.AntiVirusProcessPort_Stub Failing Method....:checkForViruses Failing File......:AntiVirusProcessPort_Stub.java Failing Line No...:31 Previous Exception:javax.xml.rpc.soap.SOAPFaultException The source of this problem is shown below =================================================================================== Exception Class...:javax.xml.rpc.soap.SOAPFaultException Exception Message.:Exception during processing: java.lang.OutOfMemoryError (see Fault Detail for stacktrace) Failing Class.....:weblogic.webservice.core.ClientDispatcher Failing Method....:receive Failing File......:ClientDispatcher.java Failing Line No...:314 Previous Exception:null > <01-Jun-2006 15:18:31 o'clock BST> <Info> <Trace> <000000> <Performance.MetricsFile: Metrics file C:\ericOutputsSA_TPVS\csadomain\outputs\Metrics\sasvr01\20060601\151831Summary.csv created>
After reading those traces several times, I see why you are wondering exactly where the fault is occuring. It looks to me like this is a report of an exception occurring on the server, but why the server logs dont show an out of memory error - I have no idea. It is the line:
that looks pretty conclusive to me. I think the normal SOAPFaultException mechanism is working properly and your client is processing a SOAP fault correctly.
Now as to why the server runs out of memory, I have no idea.
Joined: Jun 29, 2002
I think SOAP does not handle large files very well. And it is falling over when it attempts to deserialise the XML back into java.