Overview | Package | Class | Tree | Deprecated | Index | Help

3.00.12
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD

## interbase.interclient
Class CommunicationException

    java.lang.Object
      |
      +--java.lang.Throwable
            |
            +--java.lang.Exception
                  |
                  +--java.sql.SQLException
                        |
                        +--interbase.interclient.SQLException
                              |
                              +--interbase.interclient.CommunicationException

All Implemented Interfaces:
  Serializable

public final class CommunicationException
extends interbase.interclient.SQLException

Networked I/O subsystem communication failure.

InterServer must be running, either as a service or an application. If you are using Local InterBase, you must run InterServer as an application so it can talk to the Local InterBase application.

InterServer can be run either as an application (on Windows 95/98 and NT), or as a service (NT and Unix only). On Windows NT the InterServer service may be started using the InterServer Configuration Utility in the InterClient program group. Alternatively, the InterServer application may be started by selecting the InterServer icon in the InterClient program group

Check the InterServer service configuration, and verify that the port number for InterServer is 3060.

On UNIX, inetd must be running. For both Windows and UNIX, interserver must be configured as a TCP service, listening on port 3060.

- On NT, check your WINDIR\system32\drivers\etc\services file.
- On 95, check your WINDIR\services file.
- On UNIX, check your /etc/services and /etc/inetd.conf files.

In general, this exception represents an error of the underlying I/O subsystem, and can occur for the following reasons.

- An IO or socket exception occurred while trying to open or close a TCP/IP socket connection to the server.
- An IO exception occurred during a normal socket read or write, as InterClient tries to communicate across a TCP/IP socket.
- An IO exception occurred while reading from a user supplied input stream.
- An unexpected EOF occurred while reading from a user supplied input stream. A user supplied input stream to a prepared statement must provide at least as many bytes as are specified in the length parameter of methods PreparedStatement.setBinaryStream() and setAsciiStream().

The error code associated with this exception is `ErrorCodes.communication`.

Since:
  Extension, since InterClient 1.0
See Also:
  Serialized Form

Methods inherited from class java.sql.SQLException
`getErrorCode, getNextException, getSQLState, setNextException`

Methods inherited from class java.lang.Throwable
`fillInStackTrace, getLocalizedMessage, getMessage, printStackTrace, printStackTrace, printStackTrace, toString`

Methods inherited from class java.lang.Object
`clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait`

Overview | Package | Class | Tree | Deprecated | Index | Help

3.00.12
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD

Send comments or suggestions to interclient@borland.com