[jbossws-issues] [JBoss JIRA] Created: (JBWS-2931) OneWay invocations to a webservice result in ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.

Boris Belovic (JIRA) jira-events at lists.jboss.org
Thu Feb 11 06:24:09 EST 2010


OneWay invocations to a webservice result in ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.
--------------------------------------------------------------------------------------------------------

                 Key: JBWS-2931
                 URL: https://jira.jboss.org/jira/browse/JBWS-2931
             Project: JBoss Web Services
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: jbossws-native
    Affects Versions: jbossws-native-3.2.1
         Environment: SOA Platform 5, CR1
            Reporter: Boris Belovic


When tried to invoke Oneway method on WS endpoint I got this exception. The invocation of Oneway method itself is correct (all statements in Oneway method are executed), but after this invocation there is a Premature end of file error in the client. (See following stacktrace).

[java] Exception in thread "main" com.sun.xml.internal.ws.streaming.XMLStreamReaderException: XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
     [java] Message: Premature end of file.
     [java] 	at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:242)
     [java] 	at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:70)
     [java] 	at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:85)
     [java] 	at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:75)
     [java] 	at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:167)
     [java] 	at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:149)
     [java] 	at com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:121)
     [java] 	at com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
     [java] 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158)
     [java] 	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
     [java] 	at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:581)
     [java] 	at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:540)
     [java] 	at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:525)
     [java] 	at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:422)
     [java] 	at com.sun.xml.internal.ws.client.Stub.process(Stub.java:235)
     [java] 	at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:120)
     [java] 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:230)
     [java] 	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210)
     [java] 	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
     [java] 	at $Proxy26.oneWayMethod(Unknown Source)
     [java] 	at org.jboss.soa.esb.samples.quickstart.ws_i.client.HelloWorldClient.main(Unknown Source)
     [java] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
     [java] Message: Premature end of file.
     [java] 	at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:588)
     [java] 	at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(XMLStreamReaderFilter.java:78)
     [java] 	at com.sun.xml.internal.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:51)
     [java] 	... 19 more

This issue came as a part of SOA-1945. There were problems with our WISE SOAPClient, after these were solved Premature end of file appeared in the server console. It was tracked down that this issue originates in JBossWS (see linked issue for details)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list