Member since 
    
	
		
		
		10-21-2022
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                3
            
            
                Posts
            
        
                0
            
            
                Kudos Received
            
        
                0
            
            
                Solutions
            
        
			
    
	
		
		
		06-24-2025
	
		
		09:01 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @Aritra_arri As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-20-2022
	
		
		12:06 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 @AlexLasecki   The issue here is unrelated to the copy and paste action taken.  There is a bug in the code where the jsonPath cache is not cleared when the property value is changed after it has been initially set.  So the same issue happens even if you do not copy and paste a splitJson processor configured with json path property value.  All you need to do is change the json path value after after already having a value set.  Original json path property value that is cached still gets used.    The following bug jira has been created and work is already in progress to address the issue.   https://issues.apache.org/jira/browse/NIFI-10998    For now as a workaround, you'll need to create a new SplitJson processor anytime you want to change the json path property value.      If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.    Thank you,  Matt 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-21-2022
	
		
		02:09 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 The issue was not related to the size of the queue, but instead to the fact that when to destination that we are sending those logs to had connectivity issues (which was causing quite a lot of timeout errors), NiFi was using a lot of a significant number of threads to retry sending the logs to the InvokeHTTP destination. This high usage of threads was causing ListenSyslog to not function properly - it was dropping the logs that it was supposed to receive. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        
