Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-2947

WSException on client side when server sends a 100-continue HTTP response code

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      Workaround on JBossWS client side:

      Edit server\viperats\deployers\jbossws.deployer\META-INF\standard-jaxws-client-config.xml and set "http://org.jboss.ws/http#chunksize" to "-1"

      Or else install SP2 on Windows 2003. Or else install the following IIS hotfix: http://support.microsoft.com/kb/898708

      Show
      Workaround on JBossWS client side: Edit server\viperats\deployers\jbossws.deployer\META-INF\standard-jaxws-client-config.xml and set "http://org.jboss.ws/http#chunksize" to "-1" Or else install SP2 on Windows 2003. Or else install the following IIS hotfix: http://support.microsoft.com/kb/898708

    Description

      JBossWS native 3.2.1 clients give an exception when they receive a HTTP "100-continue" response from the server. This is often the case when using a JBossWS client to call a .NET web service running on IIS version 6. This cannot be seen as an IIS bug since HTTP/1.1 clients should be able to deal with 100-continue response codes. Also see the following article:

      http://blogs.msdn.com/david.wang/archive/2006/04/05/HTTP-SYS-IIS-and-the-100-continue.aspx

      The exception I'm getting on the client side:

      Caused by: org.jboss.ws.WSException: Invalid HTTP server response [100] - Continue
      at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
      at org.jboss.ws.core.client.transport.NettyClient.invokeInternal(NettyClient.java:189)
      ... 79 more

      Attachments

        Activity

          People

            rhn-support-asoldano Alessio Soldano
            maffeis_jira Silvano Maffeis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: