Github user YolandaMDavis commented on the issue:

    https://github.com/apache/nifi/pull/690
  
    @markap14 during testing I am seeing unexpected behaviors/errors and wanted 
to validate my test case. My configuration is as follows:
    
    - 1 standalone nifi server with a Processor Group and an output port
    - A 2 node cluster with a Processor Group containing an input port and a 
Remote Processor Group that points to the standalone server
    
    The goal of the test was to ensure that if an attempt is made to create a 
new connection from the Remote Processor Group to the Processor Group on the 
cluster, and the output port on the standalone (remote pg) is removed just 
before the add, then the system will display/log IllegalArgumentException 
(specifically related to the source not found).
    
    During my tests the behavior has been mostly the following:
    
    1) A NullPointerException occurs just before the verifyCreate method in 
StandardConnectionDAO is called
    2) If the port is removed a few seconds before creating a connection then 
the connection is created successfully with no logged errors.
    
    Both errors prevented me from testing that IllegalArgumentExceptions would 
be thrown in this case (since the nullpointer exception happened 
    
    Attached are snapshots of the nifi-user.log with the nullpointer exception 
that occurred on several of the runs.
    
    Is this test a feasible one and appropriate for this case? If so I would 
recommend resolution of this issue before restesting.
    
[node2-nifi-user-snapshot.log.txt](https://github.com/apache/nifi/files/395231/node2-nifi-user-snapshot.log.txt)
    <img width="1440" alt="unexpectedconnectionsuccess" 
src="https://cloud.githubusercontent.com/assets/1371858/17317043/8df4bc98-5847-11e6-8d1e-39fc4703bd29.png";>
    Also have video of errors if needed
    
    
    
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to