Hi Francoise
Essentially form the previous link .
HP ERROR 233 .
When a new connect request arricves at the local tcp and it is immediately followed by a RESET from the remote system , the server application is awakened twice by the request to perform ( accept ( ) calls ) . Each is returned bu ENOBUFS or HP Error 233. The problem is the acceptin server application should not be awakened twice . This was caused by mishandling the connection id in the TPI messages . The problem is fixed by correctly tracking the connection id between the socket and TCP layers.
There is a PATCH also which HP recommends loading PHNE_23456 to resolve this problem
Manoj Srivastava