[
https://issues.apache.org/jira/browse/KNOX-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14148579#comment-14148579
]
Kevin Minder edited comment on KNOX-365 at 9/26/14 1:10 AM:
------------------------------------------------------------
Best case I think we can verify that it fails more gracefully. The current
rewrite rules will still require the presence of a port. That being said we
should verify this for 0.5.0. We should file a different jira if we want to
support Knox behind xinetd.
was (Author: kminder):
Best case I think we can verify that it fails more gracefully. The current
rewrite rules will still require the presence of a port.
> 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.3.4#6332)
