Thanks Joe and Oleg for your inputs. The issue is mainly sending the email through PutEmail. Irrespective of the flow success or failure, the mail should trigger. In this case, when putemail receives intimation to trigger mail to the corresponding recipient, at that time it is failing due to connection timed out. I think it's because of network availability or network traffic.
It's purely about putemail processor not about transferring the file.I Provided correct host,username..etc details also. We can partially overcome this issue with the help of Re-try concept. Whenever putemail encountered the error, it will keep on try to connect for number of times which is set by us using expression language. In-between putemail should connect to host and send the email. What I am looking is there any other way in Putemail process itself to overcome this issue. Thanks, Sravani -----Original Message----- From: Joe Witt [mailto:joe.w...@gmail.com] Sent: Tuesday, November 15, 2016 6:54 PM To: users@nifi.apache.org Cc: jtsw...@gmail.com Subject: Re: Nifi- PutEmail processor issue Sravani, The flow you describe makes sense. So now lets focus on the PutEmail processor. Can you please clarify if when it fails to connect the flowfile is transferred to the 'failure' relationship or the 'success' relationship? If it flows to the 'failure' relationship then as Conrad points out you can just simply have failure loop back to that processor so it will continue to retry until it actually succeeds in transferring. If it flows to the 'success' relationship even though the email send fails then we need to look into it further and the stack trace oleg requests will be helpful. Thanks Joe On Tue, Nov 15, 2016 at 7:47 AM, Oleg Zhurakousky <ozhurakou...@hortonworks.com> wrote: > Sravani > > Would you be able to provide a full stack trace of the connection exception. > Also, while I assume you are providing the correct connection > properties (i.e., host,port etc) I would still recommend to check the > they are correct, but in any event the full stack trace would > definitely help and you cn find it the the wifi app logs. > > Cheers > Oleg > > On Nov 15, 2016, at 4:07 AM, Gadiputi, Sravani > <sravani.gadip...@capgemini.com> wrote: > > Thank you for your reply. > > My requirement is , I just try to send/copy the 3 different files from > source to destination through Nifi, and these jobs runs weekly once. > So I wanted to know which file is successfully moved through email. > In this process, I have configured putemail for each flow. There are > hardly > 3 notifications only. > Though files have been moved to destination, we could not receive the > notifications properly and giving the below error. > > Please suggest. > > Thanks, > Sravani > > > From: Jeff [mailto:jtsw...@gmail.com] > Sent: Tuesday, November 15, 2016 1:25 PM > To: users@nifi.apache.org > Subject: Re: Nifi- PutEmail processor issue > > Hello Sravani, > > Could it be possible that the SMTP server you're using is denying > connections due to the volume of emails your flow might be sending? > How many emails are sent per flow file, and how many emails do you > estimate are sent per minute? > > If this is the case, you can modify your flow to aggregate flowfiles > with a processor like MergeContent so that you can send emails that > resemble a digest, rather than a separate email for each flowfile that > moves through your flow. > > On Mon, Nov 14, 2016 at 11:59 PM Gadiputi, Sravani > <sravani.gadip...@capgemini.com> wrote: > > > Hi, > > I have used PutEmail processor in my project to send email > notification for successful/failure copying of a files. > Each file flow having corresponding PutEmail to send email > notification to respective recipients. > > Here the issue is, sometimes email notification will send to > respective recipients successfully for successful/failure job. > But sometimes for any one specific job email notification will not be > send to recipients though job is successful, due to below error. > > Error: > > Could not connect to SMTP host > Java.net.ConnectException: Connection timed out > > Could you please suggest me how we can overcome this error. > > > Thanks, > Sravani > > This message contains information that may be privileged or > confidential and is the property of the Capgemini Group. It is > intended only for the person to whom it is addressed. If you are not > the intended recipient, you are not authorized to read, print, retain, > copy, disseminate, distribute, or use this message or any part > thereof. If you receive this message in error, please notify the sender > immediately and delete all copies of this message. > > This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
