Hi,
i have used wirte and read the same named pipe with multiple input link in the different jobs. in this case the jobs has been running state only.....
Can someone please help me in debugging the issue
Read And Wirte the same named pipe in different jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi,
We are trying to first write to a named pipe file using one job and then read from the same named pipe file using another job having multiple input links in the job which writes.
In the above case the job which writes aborts with a broken pipe error and the screenshot for the error we get is attached in this
can you please help?
Thanks.
We are trying to first write to a named pipe file using one job and then read from the same named pipe file using another job having multiple input links in the job which writes.
In the above case the job which writes aborts with a broken pipe error and the screenshot for the error we get is attached in this
can you please help?
Thanks.
The named pipe mechanism requires that you have both a writer process and a reader process running at the same time. You have timeout or wait attributes that control how much time you have available before you get a "broken pipe".
So a question would be "are you certain you are running the 2 jobs at the same time?" and that you are using the same physical fifo file.
So a question would be "are you certain you are running the 2 jobs at the same time?" and that you are using the same physical fifo file.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
There are two threads on this subject - here is the other. Has some of the background left out of this one.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers