1.50.39

interbase.interclient
Class CommunicationException

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

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.

On Windows 95/NT the InterServer service must be started by the InterServer Configuration Utility 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.

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

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

Since:
Extension
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
 


1.50.39

Send comments or suggestions to icsupport@interbase.com