You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2015/09/12 06:47:45 UTC

[jira] [Commented] (NIFI-950) After importing a template parts of UI become very slow

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

Aldrin Piri commented on NIFI-950:
----------------------------------

I was not able to recreate this from some poking around with the template provided.  I could certainly see the Thread.sleep causing problems at specifically the places where you are attempting to configure, but on a "clean" build a cause evades me.

> After importing a template parts of UI become very slow
> -------------------------------------------------------
>
>                 Key: NIFI-950
>                 URL: https://issues.apache.org/jira/browse/NIFI-950
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Joseph Percivall
>         Attachments: self_reference_flow_fix.xml
>
>
> I created a flow that is a self referencing http loop. The flow was working fine but I wanted to save the template for later testing. I downloaded the the flow as a template. Then I tried testing a thread.sleep in the beginning of onConfigured, createSSLContext, and validate methods of StandardSSLContextService. I did a mvn clean install in the nifi-nar-bundles/nifi-standard-services/nifi-ssl-context-bundle/nifi-ssl-context-service directory. Then a mvn clean install in the nifi-assembly directory. After I imported the template the UI became very slow when clicking to different windows of the UI such as configuring a processor and the controller services window.
> I then stashed my changes and rebuilt the files. Once again I imported my template, and attempting to configure a processor or accessing the controller services window became very slow.
> The flow xml is attached. 



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