[
https://issues.apache.org/jira/browse/KNOX-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000410#comment-14000410
]
Kevin Minder edited comment on KNOX-365 at 5/19/14 12:26 PM:
-------------------------------------------------------------
The OUT rules should be OK but only testing will tell. You should also be
aware that every time your cluster.xml topology file's time stamp changes, the
rules (in rewrite.xml) that you changed will be regenerated and your changes
will be lost.
was (Author: kminder):
The OUT rules should be OK but only testing will tell. You should also be
aware that every time your cluster.xml topology file time stamp the rules that
you changed will be regenerated and your changes will be lost.
> NPE when using xinetd for port forwarding to Knox
> -------------------------------------------------
>
> Key: KNOX-365
> URL: https://issues.apache.org/jira/browse/KNOX-365
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Kevin Minder
> Fix For: 0.5.0
>
> Attachments: logs.zip, rewrite.xml.diff
>
>
> Has anyone had any success using a port forwarder (like xinetd) to forward
> 443 to knox gateway 8443?
> I keep getting this exception:
> 2014-05-13 17:41:13,976 ERROR hadoop.gateway
> (GatewayServlet.java:service(122)) - Failed to execute filter:
> javax.servlet.ServletException: org.apache.shiro.subject.ExecutionException:
> java.security.PrivilegedActionException: javax.servlet.ServletException:
> java.lang.NullPointerException
> My initial thought is that the knox url rewriting mechanism is expecting the
> port '8443' to exist?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
