[
https://issues.apache.org/jira/browse/CXF-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420681#comment-13420681
]
Glen Mazza commented on CXF-4440:
---------------------------------
Please ask your question on the CXF-User's list first, to determine that this
is indeed a bug in CXF instead of within your code. Note CXF is not a JAX-RPC
implementation, it's a JAX-WS one; Axis 1.x may be better fit for your needs.
> Webservice Unavailable - Internal Server Error (Response code 500) not
> handled in HTTPConduit.java (One way webservice)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-4440
> URL: https://issues.apache.org/jira/browse/CXF-4440
> Project: CXF
> Issue Type: Bug
> Reporter: Amol Deshpande
>
> Hi,
> I am working on a CXF client for a one way JAX-RPC webservice.
> I am testing a scenario where, the webservice is unavailable (The application
> for the webservice on the server is stopped)
> In this case, the server sends back a response Internal server error
> (Response code 500)
> This response code is not handled by the httpConduit.handleResponseInternal()
> function because it does not throw an error for response code 500.
> if (responseCode == HttpURLConnection.HTTP_NOT_FOUND
> && !MessageUtils.isTrue(outMessage.getContextualProperty(
> "org.apache.cxf.http.no_io_exceptions"))) {
> throw new IOException("HTTP response '" + responseCode +
> ": " + connection.getResponseMessage() + "'");
> }
> Can you please let me know if this is a known issue or if there is a
> workaround to handle this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
