Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10655

Xerces tries to parse HTTP response from oneway invocation: "Premature end of file"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • EAP_EWP 5.3.0.ER1
    • EAP_EWP 5.2.0
    • Web Services
    • None
    • JBossWS Native

    • Hide
      In previous versions of JBoss EAP 5 it was found that when invoking a one-way endpoint, the JBossWS client tried to unmarshal the response, however the response body was empty, causing this to be logged by Xerces with the followign error:
      <screen>
      11:33:19,110 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.
      </screen>
      This error did not affect the operation of the client, though it indicated that the client was doing unnecessary processing. This issue has been resolved in this release.
      Show
      In previous versions of JBoss EAP 5 it was found that when invoking a one-way endpoint, the JBossWS client tried to unmarshal the response, however the response body was empty, causing this to be logged by Xerces with the followign error: <screen> 11:33:19,110 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file. </screen> This error did not affect the operation of the client, though it indicated that the client was doing unnecessary processing. This issue has been resolved in this release.
    • Documented as Resolved Issue
    • NEW

      When invoking a one-way endpoint, the JBossWS client tries to unmarshal the response, but the response body is empty, causing this to be logged by Xerces:

      11:33:19,110 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file.
      

      This doesn't affect the operation of the client, but it indicates that the client is doing unnecessary processing that should probably be cleaned up.

              ehugonne1@redhat.com Emmanuel Hugonnet
              rh-ee-klape Kyle Lape
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: