[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...

[Jim Ma (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503761#action_12503761 ] 

Jim Ma commented on JBWS-2884:
------------------------------

The main benefit of chunked transfer-coding is it does not need sender to buffer the entire message , there is no Content-Length specified. The chunked encoding is the HTTP/1.1 feature. and most of JAX-WS stack support it . I do not know why the oracle's service can not handle it . I suspect the this service is deployed in a HTTP/1.0 support only container or the service is running in a soap stack which can not handle the chunked request .

Anyway , I think the deactivation chunk mode will be way to go to get interoperability. 

> JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBWS-2884
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2884
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.1.2
>            Reporter: Chris Laprun
>            Assignee: Jim Ma
>            Priority: Blocker
>             Fix For: jbossws-native-3.3.0
>
>
> I get:
> Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable
> 	at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:570)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:369)
> 	at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:231)
> when attempting to connect to a remote webservice with JBoss WS but I can access it just fine using SOAPUI.
> The remote service is defined by: http://portalstandards.oracle.com/portletapp/portlets?WSDL
> I'm trying to access the getServiceDescription method.
> SOAP body as generated by JBoss WS is:
> <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription>
> Requesting:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:oasis:names:tc:wsrp:v1:types">
>    <soapenv:Header/>
>    <soapenv:Body>
>       <getServiceDescription xmlns="urn:oasis:names:tc:wsrp:v1:types"><registrationContext xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/><desiredLocales>en-US</desiredLocales><desiredLocales>en</desiredLocales></getServiceDescription>
>    </soapenv:Body>
> </soapenv:Envelope>
> in SOAP UI results in the expected result:
> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="urn:oasis:names:tc:wsrp:v1:types">
>    <env:Body>
>       <ns0:getServiceDescriptionResponse>
>          <ns0:requiresRegistration>true</ns0:requiresRegistration>
>          <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:edit_defaults">
>             <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:edit_defaults">
>                <ns0:value>This mode signifies that the portlet should render a screen to set the default values for the modifiable preferences that are typically changed in the EDIT screen. Calling this mode requires that the user must have administrator rights.</ns0:value>
>             </ns0:description>
>          </ns0:customModeDescriptions>
>          <ns0:customModeDescriptions itemName="urn:javax:portlet:mode:custom:about">
>             <ns0:description xml:lang="en" resourceName="urn:javax:portlet:mode:custom:about">
>                <ns0:value>This mode should be used by the portlet to display information on the portlet's purpose, origin, version, etc.</ns0:value>
>             </ns0:description>
>          </ns0:customModeDescriptions>
>       </ns0:getServiceDescriptionResponse>
>    </env:Body>
> </env:Envelope>
> JBoss WS fails on with the above error.

-- 
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