You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2016/04/07 14:51:25 UTC

[jira] [Updated] (NIFI-1739) Stack trace shown in UI

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

Matt Gilman updated NIFI-1739:
------------------------------
    Description: 
When configured for LDAP based username and password login exceptions are returned to the user when it has been misconfigured.

{code}
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <title>Error 503 Service Unavailable</title> </head> <body><h2>HTTP ERROR 503</h2> <p>Problem accessing /nifi-api/controller/identity. Reason: <pre> Service Unavailable</pre></p><h3>Caused by:</h3><pre>org.eclipse.jetty.servlet.ServletHolder$1: org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;accessResource&apos; defined in class path resource [nifi-web-api-context.xml]: Cannot resolve reference to bean &apos;loginIdentityProvider&apos; while setting bean property &apos;loginIdentityProvider&apos;; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;loginIdentityProvider&apos;: FactoryBean threw exception on object creation; nested exception is org.apache.nifi.authorization.exception.ProviderCreationException: ....
{code}

This appears to be due to the fact that the Spring beans are lazily initialized [1]. If this wasn't the case this likely would have failed at startup which is probably more appropriate in this case.

[1] https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/resources/nifi-web-api-context.xml#L16

  was:
When configured for LDAP based username and password login exceptions are returned to the user when it has been misconfigured.

{noformat}
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <title>Error 503 Service Unavailable</title> </head> <body><h2>HTTP ERROR 503</h2> <p>Problem accessing /nifi-api/controller/identity. Reason: <pre> Service Unavailable</pre></p><h3>Caused by:</h3><pre>org.eclipse.jetty.servlet.ServletHolder$1: org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;accessResource&apos; defined in class path resource [nifi-web-api-context.xml]: Cannot resolve reference to bean &apos;loginIdentityProvider&apos; while setting bean property &apos;loginIdentityProvider&apos;; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;loginIdentityProvider&apos;: FactoryBean threw exception on object creation; nested exception is org.apache.nifi.authorization.exception.ProviderCreationException: ....
{noformat}

This appears to be due to the fact that the Spring beans are lazily initialized [1]. If this wasn't the case this likely would have failed at startup which is probably more appropriate in this case.

[1] https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/resources/nifi-web-api-context.xml#L16


> Stack trace shown in UI
> -----------------------
>
>                 Key: NIFI-1739
>                 URL: https://issues.apache.org/jira/browse/NIFI-1739
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Matt Gilman
>            Priority: Trivial
>
> When configured for LDAP based username and password login exceptions are returned to the user when it has been misconfigured.
> {code}
> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <title>Error 503 Service Unavailable</title> </head> <body><h2>HTTP ERROR 503</h2> <p>Problem accessing /nifi-api/controller/identity. Reason: <pre> Service Unavailable</pre></p><h3>Caused by:</h3><pre>org.eclipse.jetty.servlet.ServletHolder$1: org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;accessResource&apos; defined in class path resource [nifi-web-api-context.xml]: Cannot resolve reference to bean &apos;loginIdentityProvider&apos; while setting bean property &apos;loginIdentityProvider&apos;; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name &apos;loginIdentityProvider&apos;: FactoryBean threw exception on object creation; nested exception is org.apache.nifi.authorization.exception.ProviderCreationException: ....
> {code}
> This appears to be due to the fact that the Spring beans are lazily initialized [1]. If this wasn't the case this likely would have failed at startup which is probably more appropriate in this case.
> [1] https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/resources/nifi-web-api-context.xml#L16



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