[ 
https://issues.apache.org/jira/browse/APEXCORE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203410#comment-15203410
 ] 

ASF GitHub Bot commented on APEXCORE-399:
-----------------------------------------

GitHub user PramodSSImmaneni opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/278

    APEXCORE-399 Need better debug information in stram web service filter 
initializer

    @vrozov please see

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/PramodSSImmaneni/incubator-apex-core 
stram-ws-filter-debug

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-apex-core/pull/278.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #278
    
----
commit 9eba29de8143efd716aba8d2a4bdb085e298ab5a
Author: Pramod Immaneni <[email protected]>
Date:   2016-03-20T18:11:32Z

    Logging of proxy addresses at different computation stages for better 
debugging

----


> Need better debug information in stram web service filter initializer
> ---------------------------------------------------------------------
>
>                 Key: APEXCORE-399
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-399
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Pramod Immaneni
>            Assignee: Pramod Immaneni
>
> Stram web service filter initializer figures out the proxy addresses from 
> which to allow the initial requests. If these cannot be determined correctly 
> because of bad configuration or other reasons this will result in web service 
> requests getting denied. Need better debug information for the information 
> obtained at different stages so as to be able to find out the source of the 
> problem in normal and HA cases.



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

Reply via email to