Technote (troubleshooting)
Problem(Abstract)
A list of common reasons for application bind errors and recommended solutions.
Cause
Several problems can cause these errors:
- PORT statement conflict (EACCES). Common causes are:
- The port you are using is defined in PORTRANGE
- The started application name doesn't match the application name defined in the PORT statement
- The user ID associated with the application does not have access to the SAF resource specified on the PORTRANGE statement.
- Socket already bound to the port (EADDRINUSE). Common causes are:
- SO_REUSEADDR was not used
- The socket is bound to same port/IP address pair, without SHAREPORT (only TCP)
- IP address conflict (EADDRNOTAVAIL). Common causes are:
- IP address not valid (for example, a broadcast or nonexistent IP address)
- Various DVIPA failures (for example, JRDVIPACONFLICTIPADDR - DVIPA already active on another stack that will not release it.)
Resolving the problem
Review the common causes and take appropriate action.
Rate this page:
Average rating
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.