You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Cyrille Le Clerc (JIRA)" <ji...@apache.org> on 2009/11/16 16:23:39 UTC
[jira] Created: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Proposal : enhancement of HTTP exceptions messages
--------------------------------------------------
Key: CXF-2537
URL: https://issues.apache.org/jira/browse/CXF-2537
Project: CXF
Issue Type: Improvement
Components: Transports
Affects Versions: 2.2.3
Reporter: Cyrille Le Clerc
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : {{java.io.IOException: Not Found}}
** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
{noformat:title=Current HTTP 404 exception message}
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
{noformat}
{noformat:title=Enhanced HTTP 404 exception message}
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc updated CXF-2537:
----------------------------------
Description:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : java.io.IOException: Not Found
** Enhanced Message : java.io.IOException: HTTP response '404: Not Found
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
Current HTTP 404 exception message
==============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
Enhanced HTTP 404 exception message
===============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
was:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : {{java.io.IOException: Not Found}}
** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
Current HTTP 404 exception message
==============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
Enhanced HTTP 404 exception message
===============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc updated CXF-2537:
----------------------------------
Description:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : java.io.IOException: Not Found
** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
Current HTTP 404 exception message
==============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
Enhanced HTTP 404 exception message
===============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
was:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : java.io.IOException: Not Found
** Enhanced Message : java.io.IOException: HTTP response '404: Not Found
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
Current HTTP 404 exception message
==============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
Enhanced HTTP 404 exception message
===============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc reopened CXF-2537:
-----------------------------------
Assignee: Cyrille Le Clerc (was: Daniel Kulp)
SSL related exceptions don't benefit of the enhanced message :
{noformat:title=Current (2.2.6) exception}
javax.xml.ws.WebServiceException: Could not send Message.
...
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
Caused by: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
{noformat}
{noformat:title=Enhanced exception, the invoked url is added}
javax.xml.ws.WebServiceException: Could not send Message.
...
Caused by: javax.net.ssl.SSLHandshakeException: SSLHandshakeException invoking https://localhost/services/helloWorldService:
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
...
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
Caused by: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
...
{noformat}
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Assignee: Cyrille Le Clerc
> Fix For: 2.1.9, 2.2.6
>
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc resolved CXF-2537.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.6)
(was: 2.1.9)
2.2.7
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Assignee: Cyrille Le Clerc
> Fix For: 2.2.7
>
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc updated CXF-2537:
----------------------------------
Attachment: CXF-2537.patch
Proposed patch. Modifications :
HttpConduit.handleResponseInternal() : add details for 404 exception
HTTPConduit.WrappedOutputStream.close() : add intermediate IOException with the invoked URL
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : {{java.io.IOException: Not Found}}
> ** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2537:
--------------------------------
Assignee: Daniel Kulp
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Assignee: Daniel Kulp
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2537.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.6
2.1.9
I made a slight change to the patch to make an attempt to keep the same exception type. (SocketTimeoutException remains a SocketTimeoutException instead of a generic IOException).
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
> Assignee: Daniel Kulp
> Fix For: 2.1.9, 2.2.6
>
> Attachments: CXF-2537.patch
>
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : java.io.IOException: Not Found
> ** Enhanced Message : java.io.IOException: HTTP response '404: Not Found'
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/this-page-does-not-exist.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2537) Proposal : enhancement of HTTP
exceptions messages
Posted by "Cyrille Le Clerc (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cyrille Le Clerc updated CXF-2537:
----------------------------------
Description:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : {{java.io.IOException: Not Found}}
** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
Current HTTP 404 exception message
==============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
Enhanced HTTP 404 exception message
===============================
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
was:
Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
Here is a proposal of enhancements of the exception messages :
* Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
** Current message : {{java.io.IOException: Not Found}}
** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
* Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
{noformat:title=Current HTTP 404 exception message}
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: Not Found
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
{noformat}
{noformat:title=Enhanced HTTP 404 exception message}
javax.xml.ws.WebServiceException: Could not send Message.
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
at $Proxy67.sayHi(Unknown Source)
...
at java.lang.Thread.run(Thread.java:637)
Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
... 62 more
Caused by: java.io.IOException: HTTP response '404: Not Found'
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
... 71 more
{noformat}
> Proposal : enhancement of HTTP exceptions messages
> --------------------------------------------------
>
> Key: CXF-2537
> URL: https://issues.apache.org/jira/browse/CXF-2537
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.2.3
> Reporter: Cyrille Le Clerc
>
> Troubleshooting of client side HTTP exceptions is often difficult for development, integration and troubleshooting teams.
> Here is a proposal of enhancements of the exception messages :
> * Add the HTTP error code for 404 exceptions in addition to the message returned by the server.
> ** Current message : {{java.io.IOException: Not Found}}
> ** Enhanced Message : {{java.io.IOException: HTTP response '404: Not Found'}}
> * Add intermediate IOException with the invoked URL in the stack of causes of the "WebServiceException: Could not send Message." exception.
> Current HTTP 404 exception message
> ==============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: Not Found
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
> Enhanced HTTP 404 exception message
> ===============================
> javax.xml.ws.WebServiceException: Could not send Message.
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135)
> at $Proxy67.sayHi(Unknown Source)
> ...
> at java.lang.Thread.run(Thread.java:637)
> Caused by: java.io.IOException: IOException invoking http://localhost:8080/jmx-demo/faults/this-page-does-not-exist-404.jsp
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1984)
> ... 62 more
> Caused by: java.io.IOException: HTTP response '404: Not Found'
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2115)
> ... 71 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.