Failed to write to an IPC Port: The pipe is being closed.

Question

0.00/5 (No votes)

See more:

I am getting above exception after approximately 6 hrs or more continuous traffic flow through one of my service. The Service is responsible to listen TCP/IP request and pass those messages to an another componant through a port 5024. At the same time if any response recieved from the componant it conveys the message to the same port.

Any guidence/clue on this will be a great help.

Posted 21-Jun-11 3:23am

InamulHussain

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-06-21T07:13:00

This is the usual message in IPC communication via named pipes when the other side of the channel closes the pipe. It's hard to tell you more about it; you simply need to check up your logic. If you can create a really short testable sample which compiles and manifest this problem (for goodness sake, not all your code), it would not be too hard to solve the problem. If you still have this problem and can prepare the sample application, please post it. Use "Improve question".

You can also sort things out by yourself using Debugger, but it could be tricky. Better yet, log all key points in the communication from both parts in a single event log using System.EventLog. To find out the source of the problem, you need to understand the order of operation as it is supposed to be.

—SA