Read timeout error when invoking webservice

Question

When I test one of our RPC style webservices from my Java
client, I get this error at random intervals :
org.xml.sax.SAXParseException: Unbalanced ELEMENT got:detail expected:init at
weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseException(SAXElementFactory.java:67)
at weblogic.xml.babel.parsers.StreamParser.streamParseSome(StreamParser.java:136)
at weblogic.xml.babel.parsers.BabelXMLEventStream.parseSome(BabelXMLEventStream.java:46)
at weblogicx.xml.stream.SubEventStream.parseSome(SubEventStream.java:48) at weblogicx.xml.stream.SubElementEventStream.parseSome(SubElementEventStream.java:38)
at weblogicx.xml.stream.SubEventStream.parseSome(SubEventStream.java:48) at weblogicx.xml.stream.SubElementEventStream.parseSome(SubElementEventStream.java:38)
at weblogicx.xml.stream.XMLEventStreamBase.hasNext(XMLEventStreamBase.java:135)
at weblogicx.xml.stream.helpers.TextBuilder.process(TextBuilder.java:23) at weblogic.soap.codec.SoapEncodingCodec.decode(SoapEncodingCodec.java:194)
at weblogic.soap.codec.SoapEncodingCodec.decode(SoapEncodingCodec.java:145) at
weblogic.soap.codec.CodecFactory.decode(CodecFactory.java:66) at weblogic.soap.codec.Operation.read(Operation.java:97)
at weblogic.soap.codec.SoapMessage.readOperation(SoapMessage.java:200) at weblogic.soap.codec.SoapMessage.read(SoapMessage.java:130)
at weblogic.soap.WebServiceProxy.receive(WebServiceProxy.java:480) at weblogic.soap.WebServiceProxy.invoke(WebServiceProxy.java:431)
at weblogic.soap.SoapMethod.invoke(SoapMethod.java:186)
it seems to be caused by a read time out :
Server side error: java.io.InterruptedIOException:
Read timed out at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:86)
at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:124) at
weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:97)
at java.io.FilterInputStream.read(FilterInputStream.java:114) at java.io.PushbackInputStream.read(PushbackInputStream.java:164)
at java.io.FilterInputStream.read(FilterInputStream.java:93) at weblogic.xml.babel.reader.XmlReader.(XmlReader.java:247)
at weblogic.xml.babel.reader.XmlReader.createReader(XmlReader.java:124) at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:98)
at weblogic.xml.babel.parsers.StreamParser.(StreamParser.java:42) at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(BabelXMLEventStream.java:28)
at weblogic.soap.server.servlet.StatelessBeanAdapter.getXMLStream(StatelessBeanAdapter.java:216)
at weblogic.soap.server.servlet.StatelessBeanAdapter.getInputMessage(StatelessBeanAdapter.java:151)
at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:113)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Does anybody have som hints for this situation?
Regards,
Per Mengshoel

Answer 1

Hi all,
as many developers I have encountered the famous "java.rmi.MarshallException:(1)Missing end tag for Body or Envelope" during the development of my WS app for J2ME (JSR 172).
It is correct that is the empty tag <soapenv:Header /> causing this error.
To fix this error, it is necessary to stop the server to generate this empty header in the response stream.
I have fixed this error for Axis2: unfortunaly it is necessary to modify a class in Axiom library. This library is used in Axis2 to produce the SOAP response, you can download the source code at http://ws.apache.org/commons/axiom/source-repository.html.
Here the class to modify:
axiom\modules\axiom-impl\src\main\java\org\apache\axiom\soap\impl\llom\soap11\SOAP11Factory.java
by commenting the line 273 in the method called getDefaultEnvelope() to prevent the empty header insertion in SOAP response:
public SOAPEnvelope getDefaultEnvelope() throws SOAPProcessingException {
        OMNamespace ns =
                new OMNamespaceImpl(
                        SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI,
                        SOAP11Constants.SOAP_DEFAULT_NAMESPACE_PREFIX);
        SOAPEnvelopeImpl env = new SOAPEnvelopeImpl(ns, this);
        //createSOAPHeader(env); the line to be commented
        createSOAPBody(env);
        return env;
    }Finally you have to recompile Axiom using Maven to obtain the fixed package axiom-impl.jar and to replace this package on the lib repository of your Axis2 server.
A little tricky to fix this bug but now my app runs perfectly ;)
Enjoy!
Romain Pellerin
http://www.gasp-mobilegaming.org