Error Writing To Pipe Block Mode Broken Pipe
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Dennis Stevenson bracke Craig Borysowich DukeGanote Richard PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Dell Software Panaya Inc. Oracle VAI View All Topics View All Members View All Companies Toolbox for IT Topics Data Warehouse Groups Ask a New Question Ab Initio The Ab Initio group is for the discussion of issues that arise during the implementation, configuration, administration, or daily use of Ab Initio software. Home | Invite Peers | More Data Warehouse Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Broken Pipe issue. Unknown User asked Jul 28, 2003 | Replies (3) Hi, I am testing the Hub and Spoke model. I am using a Unix batch script for the same I am having an error while i try to write to the data hub using remote component. The graph just reformats a 60GB file and makes an extract worth 5GB to write to the hub. However whenever it is in the process of writing it errors out with the message below. Pls let me know if you know the solution. Thanks in advance. Deepak Mangani. 804-986-0566. Failed writing 5676 bytes to flow: Broken pipe Flow = "Flow_1.007" connected to output port "out" of "Flow_1.in.adaptor.007" 562686420 bytes written previously. ABINITIO (2.10.15): Mon Jul 28 18:13:37 2003 ABINITIO: Rolling back ... Done. ABINITIO: Join this group Popular White Paper On This Topic Best Practices for a BI and Analytics Strategy 3Replies Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... GD replied Jul 29, 2003 Hi Deepak, Can you ch
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Dennis Stevenson bracke Craig Borysowich DukeGanote Richard PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Dell Software Panaya Inc. Oracle VAI View All Topics View All Members View All http://datawarehouse.ittoolbox.com/groups/technical-functional/abinitio-l/broken-pipe-issue-302365 Companies Toolbox for IT Topics Data Warehouse Groups Ask a New Question Ab Initio The Ab Initio group is for the discussion of issues that arise during the implementation, configuration, administration, or daily use of Ab Initio software. Home | Invite Peers | More Data Warehouse Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken http://datawarehouse.ittoolbox.com/groups/technical-functional/abinitio-l/broken-pipe-error-2202752 If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Broken Pipe Error Murali Pinnamaneni asked Jun 26, 2008 There are two extreme cases where broken pipe occurs w.r.t DB Loads: First: The failing component starts to shut down, and an upstream component sees the pipe to close, which signals abinitio to shutdown the process before seeing the "real" error. Second: Hard crash of the loader, where db component hasn't flushed it's messages to its log output. For you to capture the exact error, you could increase the delay time using AB_AGENT_ERROR_DELAY to a higer value or you can have the loader to write directly to the log file by using AB_DB_LOGFILE. (only used for debugging, not as a fix). If you are not familiar with what I'm talking about, involve support at abinitio.. Thanks Murali Pinnamaneni Join this group Popular White Paper On This Topic Delivering Information Faster: In-Me
Posted: Thu, 26 Apr 2007 @ 09:38:20 GMT
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What causes the Broken Pipe Error? up vote 42 down vote favorite 12 I know that broken pipe error is thrown when the socket on the peer side is closed. But, in my test I have noted that an immediate 'send' call on this side when the peer side is closed doesn't always lead to a broken pipe error. E.g.: After closing the socket on peer side (I have tried clean closing by calling close and also abnormal closing by killing the peer), if I try to send 40 bytes, then I don't get a broken pipe, but, if I try to send 40000 bytes then it immediately gives broken pipe error. What exactly causes broken pipe and can it's behavior be predicted? c broken-pipe share|improve this question edited Jun 9 at 7:53 Robert Siemer 7,10433455 asked Jan 3 '11 at 13:39 Jay 10.6k1551106 add a comment| 3 Answers 3 active oldest votes up vote 32 down vote accepted It can take time for the network close to be observed - the total time is nominally about 2 minutes (yes, minutes!) after a close before the packets destined for the port are all assumed to be dead. The error condition is detected at some point. With a small write, you are inside the MTU of the system, so the message is queued for sending. With a big write, you are bigger than the MTU and the system spots the problem quicker. If you ignore the SIGPIPE signal, then the functions will return EPIPE error on a broken pipe - at some point when the broken-ness of the connection is detected. share|improve this answer answered Jan 3 '11 at 16:55 Jonathan Leffler 439k62511823 3 @varevarao: I don't think that queueing transmissions and sending at specific intervals is a workaround. Queuing transmissions until there's more than the MTU to send might be a workaround if your application can live with the delays. –Jonathan Leffler Dec 13 '12 at 16:10 add a comment| up vote 6 down vote The current state of a socket is determined by 'keep-alive' activity. In your case, this is possible that when you are issuing the send call, the keep-alive activity tells that the socket is active and so the send call will write the required data (40 bytes) in to