[JBoss JIRA] Created: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
4:34 p.m.
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
Priority: Blocker
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
7:54 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2884:
----------------------------------
Fix Version/s: jbossws-native-3.3.0
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
6:12 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Jim Ma commented on JBWS-2884:
------------------------------
Hi Chris,
Looks the server side does not properly handle chunked request. Adding the disable chunk
mode code in client side to see if that helps in your case:
ChunkedEncodingFeature feature = new ChunkedEncodingFeature(false);
wsrpService.getPort(WSRPV1ServiceDescriptionPortType.class,
feature).getServiceDescription(...);
Jim
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
9:45 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2884:
--------------------------------------
Jim I think the problem will be validResponseCodes doesn't contain 503
(http://en.wikipedia.org/wiki/List_of_HTTP_status_codes):
public class HTTPMessageUnMarshaller implements UnMarshaller
{
private static List<Integer> validResponseCodes = new
ArrayList<Integer>();
static
{
validResponseCodes.add(HttpServletResponse.SC_OK);
validResponseCodes.add(HttpServletResponse.SC_ACCEPTED);
validResponseCodes.add(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
}
...
}
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
9:47 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2884:
--------------------------------------
Forget my above comment. It seems service should be invocable and you shouldn't get
503 at all.
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
1:44 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
What is the benefit of chunked requests? Is it normal for a JAX-WS web service to not
support them? If yes, is there a way to query it to know if that's the case (doubt
it)?
I'm asking because my code connects dynamically to potentially several different
servers which might or might not support chunked encoding and I'd rather not have to
deactivate it globally if it has benefits.
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
3:50 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Jim Ma commented on JBWS-2884:
------------------------------
"What is the benefit of chunked requests? Is it normal for a JAX-WS web service to
not support them? If yes, is there a way to query it to know if that's the case (doubt
it)?"
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 doubt 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
3:53 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
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
3:53 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Jim Ma updated JBWS-2884:
-------------------------
Comment: was deleted
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
2:55 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
ChunkedEncodingFeature is a JBossWS-proprietary feature as I'd like our code to stay
stack-independent, it's not feasible for me to use that feature. I see that the
property StubExt.PROPERTY_CHUNKED_ENCODING_SIZE can be set on the request context, which
is what I will use without referencing StubExt of course, which is quite annoying since
I'll have to hardcode the property name.
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
4:20 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
I've added:
((BindingProvider)service).getRequestContext().put("http://org.jboss.ws/http#chunksize",
0);
to my code and I still get the 503 error.
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
9:13 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Jim Ma commented on JBWS-2884:
------------------------------
I tried the following code to connect to the oracle service , I get the HTTP 200.
WSRPV1ServiceDescriptionPortType port =
wsrpService.getPort(WSRPV1ServiceDescriptionPortType.class);((BindingProvider)port).getRequestContext().put("http://org.jboss.ws/http#chunksize",
0);
port.getServiceDescription(...);
Did I miss something ?
((BindingProvider)port).getRequestContext().put("http://org.jboss.ws/http#chunksize",
0) to disable the chunk encoding is not stack-independent . It does not work cxf or metro
stack .
If you just using the client side code to call webservice , you do not need to make the
client side stack-independent, you can use native client code to call other soap stack
service , even .Net service.
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
12:54 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
Hmm, that is what I do: let me check again, I tried it quite late last night so might have
missed something.
Concerning, client-side stack independence: the goal is AS portability so tying the client
to a particular stack if we can avoid it is a no-no. I know that it wouldn't impact
portability as far as requests go.
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
1:47 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
Just tried again and verified that the property is set on the request context but I still
get a 503 error code in response. :(
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
2:15 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Thomas Heute commented on JBWS-2884:
------------------------------------
The only way I could make it work was by setting http://org.jboss.ws/http#chunksize to 0
in:
server/default/deployers/jbossws.deployer/META-INF/standard-jaxws-client-config.xml
I didn't figure out how to do that programmatically.
I looked at the method "createRemotingMetaData" in:
http://anonsvn.jboss.org/repos/jbossws/stack/native/tags/jbossws-native-3...
I was trying to set chunksize prior to the call to getServiceDescription in the method
getUnmanagedServiceDescription in:
http://anonsvn.jboss.org/repos/gatein/components/wsrp/trunk/consumer/src/...
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
3:25 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Chris Laprun commented on JBWS-2884:
------------------------------------
It's done programmatically in
http://anonsvn.jboss.org/repos/gatein/components/wsrp/trunk/consumer/src/...
line 112.
But it doesn't seem to work if I don't set the chunksize to 0 in
standard-jaxws-client-config.xml.
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
3:40 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBWS-2884:
---------------------------------------
The chunk size can be modified programmatically (either using the webservice feature
-jaxws2.1- or using the message context property) just starting from jbossws-native 3.2.0,
as that's implemented in https://jira.jboss.org/jira/browse/JBWS-2694 . Before that
you need to either modify the default jaxws client configuration
(server/default/deployers/jbossws.deployer/META-INF/standard-jaxws-client-config.xml) or
provide your own jaxws client config file along with the deployment and refer to it using
the setConfigFile/setConfig name of org.jboss.ws.core.ConfigProvider (you need to cast the
port to that interface or to StubExt).
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
5:55 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2884) JBoss WS cannot connect to a remote service with a 503 HTTP response when SOAPUI can connect just fine...
[
https://jira.jboss.org/jira/browse/JBWS-2884?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2884:
----------------------------------
Fix Version/s: (was: jbossws-native-3.3.0.Beta5)
Setting empty fix version on rejected issues
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
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
5215
days inactive
5281
days old
jbossws-issues@lists.jboss.org
17 comments
5 participants
participants (5)
-
Alessio Soldano (JIRA) -
Chris Laprun (JIRA)
-
Jim Ma (JIRA)
-
Richard Opalka (JIRA)
-
Thomas Heute (JIRA)