You are viewing a plain text version of this content. The canonical link for it is here.

Posted to portalapps-dev@portals.apache.org by "Woonsan Ko (JIRA)" <ji...@apache.org> on 2014/11/11 00:45:34 UTC

[jira] [Updated] (APA-68) DefaultHttpReverseProxyServlet swallows Exception if config cannot be loaded

     [ https://issues.apache.org/jira/browse/APA-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko updated APA-68:
--------------------------
    Fix Version/s:     (was: apa-webcontent-2.0)

> DefaultHttpReverseProxyServlet swallows Exception if config cannot be loaded
> ----------------------------------------------------------------------------
>
>                 Key: APA-68
>                 URL: https://issues.apache.org/jira/browse/APA-68
>             Project: Portals Apps
>          Issue Type: Bug
>          Components: apa-webcontent
>    Affects Versions: apa-webcontent-1.3
>            Reporter: Jonas
>            Assignee: Woonsan Ko
>            Priority: Minor
>             Fix For: apa-webcontent-1.4
>
>
> DefaultHttpReverseProxyServlet#loadConfiguration has a catch Block for Exceptions occuring during load of the config (Lines 809-830). Unfortunately, that Exception isn't included in any way in the ServletException that is thrown (neither Exception message nor stack trace), which makes troubleshooting difficult.
> Wouldn't it make sense to add the Exception to the ServletException (as cause), or - if that isn't possible for some reason - to at least log that Exception?
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)