| Author |
Message
|
| dileep1985 |
 Posted: Sat Jul 15, 2017 9:05 am Post subject: FTP Connection issue to remote FTP server |
 |
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
Hi All,
One of our FLOW is establishing a connection to remote FTP server using File input node. We are able to make connection to the remote FTP server and able to pick and process the files.
File input node ---> compute node --> MQ
But if we are losing connection to the FTP server, why the flow is not re- establishing the connection automatically. Connection established again to the remote FTp server again only after restarting the flow. Why IIB is not establishing the connection without restarting the flow.
'
Continuous error as 'File node 'FLI_read' in message flow ' MF_File_Read' could not connect to remote FTP Server 'xysz' . Reason: 'timeout(60000): Connection refused. |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Mon Jul 17, 2017 12:19 am Post subject: Re: FTP Connection issue to remote FTP server |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
Hi Dileep,
I assume you are using IIB 10.0.0.x as we faced the same issue and got it fixed as part of Apar (IT17570).
PS: I'm not able to post the Apar url here but google should help.
Regards,
Abhi |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Jul 18, 2017 6:51 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
@abhi_thri,
If you are saying you just didn't know how to put the url here, then this will help.
If you have a non-technical reason, well then there is that... |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 18, 2017 7:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| JosephGramig wrote: |
| If you have a non-technical reason, well then there is that... |
The non-technical reason is that that's his first post.
@dileep1985 - If I see "connection refused", I think network firewall not IIB problem.
Assuming it is an IIB problem, raise a PMR quoting that APAR number. There's no guarantee you're on the same OS (even if you are using v10) as @abhi_thri and you should get an APAR specific for you, or better still upgrade to a fix pack that contains it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dileep1985 |
| Posted: Tue Jul 18, 2017 7:58 pm Post subject: |
|
|
Novice
Joined: 15 Jul 2017
Posts: 15
|
Thanks for the response. We are planning to apply the fix pack. Currently we are running in 10.0.0.3 and planning to put fix pack to the next level 10.0.0.8.
Also currently under Retry tab for the File input node we have set it as Failure . We are planning to set Long Retry interval property before a Failure to be reported. Eventhough this method wont resolve the issue if FTP is not available for a longer period of time, but atleast hoping that can re connect if FTP is not available for lesser time.
Yes there was a network issue in the FTP side at first time but after sometime issue at FTp side resolved but still IIB didnt able to make the subsequent connection. So the doubt has raised why IIB is not making the subsequent connection automatically even after FTP is up. It requires a manual restart of the flow to enable to connection again to FTP.
Any further inputs other than fix pack , please let me know |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jul 19, 2017 12:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's often better to push files to the broker, than it is to "poll" for them.
That way you don't get polling latency and you don't get errors when the origin service is down for whatever reason.
Either way it's best to write the file and then rename it, looking only for the renamed file in the input node. This avoids partial file processing.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
