Bug 779569 (SOA-1945)

Summary: OneWay invocations to a webservice result in ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Boris Belovic <bbelovic>
Component: JBossWSAssignee: trev <tkirby>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0.0 CR1   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1945
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 22:01:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
ws_oneway.tar.bz2 none

Description Boris Belovic 2010-02-10 15:21:15 UTC
Date of First Response: 2010-02-10 10:21:51
project_key: SOA

The stacktrace is as follows.

        org.apache.xerces.util.DefaultErrorHandler.printError(java.lang.String, org.apache.xerces.xni.parser.XMLParseException) line: not available
        org.apache.xerces.util.DefaultErrorHandler.fatalError(java.lang.String, java.lang.String, org.apache.xerces.xni.parser.XMLParseException) line: not available
        org.apache.xerces.impl.XMLErrorReporter.reportError(org.apache.xerces.xni.XMLLocator, java.lang.String, java.lang.String, java.lang.Object[], short, java.lang.Exception) line: not available
        org.apache.xerces.impl.XMLErrorReporter.reportError(org.apache.xerces.xni.XMLLocator, java.lang.String, java.lang.String, java.lang.Object[], short) line: not available
        org.apache.xerces.impl.XMLErrorReporter.reportError(java.lang.String, java.lang.String, java.lang.Object[], short) line: not available
        org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(org.apache.xerces.xni.parser.XMLInputSource) line: not available
        org.apache.xerces.parsers.XIncludeAwareParserConfiguration(org.apache.xerces.parsers.XML11Configuration).parse(boolean) line: not available
        org.apache.xerces.parsers.XIncludeAwareParserConfiguration(org.apache.xerces.parsers.XML11Configuration).parse(org.apache.xerces.xni.parser.XMLInputSource) line: not available
        org.apache.xerces.parsers.DOMParser(org.apache.xerces.parsers.XMLParser).parse(org.apache.xerces.xni.parser.XMLInputSource) line: not available
        org.apache.xerces.parsers.DOMParser.parse(org.xml.sax.InputSource) line: not available
        org.apache.xerces.jaxp.DocumentBuilderImpl.parse(org.xml.sax.InputSource) line: not available
        org.jboss.wsf.common.DOMUtils.parse(org.xml.sax.InputSource) line: 222
        org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(javax.xml.soap.SOAPMessage, java.io.InputStream, boolean) line: 84
        org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(javax.xml.soap.MimeHeaders, java.io.InputStream, boolean) line: 294
        org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(java.io.InputStream, java.util.Map) line: 82
        org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(java.util.Map, java.util.Map, org.jboss.remoting.marshal.UnMarshaller, java.io.InputStream) line: 584
        org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(java.net.HttpURLConnection, java.lang.Object, java.util.Map, org.jboss.remoting.marshal.Marshaller, org.jboss.remoting.marshal.UnMarshaller) line: 381
        org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(java.net.HttpURLConnection, java.lang.String, java.lang.Object, java.util.Map, org.jboss.remoting.marshal.Marshaller, org.jboss.remoting.marshal.UnMarshaller, boolean) line: 232
        org.jboss.remoting.transport.http.HTTPClientInvoker.transport(java.lang.String, java.lang.Object, java.util.Map, org.jboss.remoting.marshal.Marshaller, org.jboss.remoting.marshal.UnMarshaller) line: 162
        org.jboss.remoting.transport.http.HTTPClientInvoker(org.jboss.remoting.MicroRemoteClientInvoker).invoke(org.jboss.remoting.InvocationRequest) line: 167
        org.jboss.remoting.Client.invoke(java.lang.Object, java.util.Map, org.jboss.remoting.InvokerLocator) line: 1917
        org.jboss.remoting.Client.invoke(java.lang.Object, java.util.Map) line: 768
        org.jboss.remoting.Client.invokeOneway(java.lang.Object, java.util.Map, boolean) line: 817
        org.jboss.ws.core.client.SOAPProtocolConnectionHTTP(org.jboss.ws.core.client.HTTPRemotingConnection).invoke(org.jboss.ws.core.MessageAbstraction, java.lang.Object, boolean) line: 228
        org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(org.jboss.ws.core.MessageAbstraction, java.lang.Object, boolean) line: 71
        org.jboss.ws.core.jaxws.client.ClientImpl(org.jboss.ws.core.CommonClient).invoke(javax.xml.namespace.QName, java.lang.Object[], boolean) line: 339
        org.jboss.ws.core.jaxws.client.ClientImpl.invoke(javax.xml.namespace.QName, java.lang.Object[], java.util.Map<java.lang.String,java.lang.Object>) line: 231
        org.jboss.ws.core.jaxws.client.ClientProxy.invoke(javax.xml.namespace.QName, java.lang.Object[], java.lang.Class, java.util.Map<java.lang.String,java.lang.Object>) line: 162
        org.jboss.ws.core.jaxws.client.ClientProxy.invoke(java.lang.Object, java.lang.reflect.Method, java.lang.Object[]) line: 148
        $Proxy411.sendOneWay() line: not available

Comment 1 Kevin Conner 2010-02-10 15:21:51 UTC
First came to light in SOA-1756.

Comment 2 Kevin Conner 2010-02-10 15:21:51 UTC
Link: Added: This issue is related to SOA-1756


Comment 3 Boris Belovic 2010-02-10 16:17:28 UTC
Possible reproducer attached, but  still can't get stacktrace above.

Comment 4 Boris Belovic 2010-02-10 16:17:28 UTC
Attachment: Added: ws_oneway.tar.bz2


Comment 5 Boris Belovic 2010-02-10 16:23:50 UTC
By reproducer I meant I got [Fatal Error] :-1:-1: Premature end of file, but still can't see the stacktrace.

Comment 6 Kevin Conner 2010-02-10 16:52:18 UTC
The stacktrace was generated through a debugger, it was not seen in the logs.

Looks like we definitely need a JBossWS issue for this now, thanks for creating the test.


Comment 7 Kevin Conner 2010-02-10 16:55:30 UTC
Changing reporter, Boris found this one.

Comment 8 Boris Belovic 2010-02-11 11:23:01 UTC
Link: Added: This issue related JBWS-2931