| Summary | Socket error in Orbix with the reason Channel has been shutdown |
|---|---|
| Article Number | 17478 |
| Environment | Orbix 3.x All Supported Operating Systems Orbix C Runtime |
| Question/Problem Description | Socket error in Orbix with the reason Channel has been shutdown 10088-- Communication failure - TCP/IP Socket interface failure Reason: Channel has been shutdown |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | This error is seen when an attempt was made to send a message down a connection that has just been shutdown from the other side of the socket (outside of the senders process space). This is most likely due to the server which the message has been sent to exiting or closing the connection via an Active Connection Management configuration. |
| Resolution | Identify the server which exited and confirm why it has shutdown. This may be for a number of reasons. |
| Workaround | |
| Notes | TCP packet analysis tools such as wireshark will be useful to identify where the call to close the socket came from. In some instances sockets can be closed by tools such as firewalls due to inactivity. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#KnowledgeDocs
#Orbix
