%META:TOPICPARENT{name="ErrorMessagesN"}%

=Network read error (JDBC)=

JDBC "network read" errors most often occur when incorrect port numbers are used in connection URLs. If you receive "network read" errors, insure that you pass the <nop>OpenLink Request Broker "Listen" port, 5000 by default, in your URL. This setting may have been changed during installation and configuration of the Multi-Tier components. If you do not know which port is utilized by your Broker, take the following action:

# Access the machine which contains your <nop>OpenLink server components installation.
# Open your Rulebook (default, {{{oplrqb.ini}}} in the {{{$OPENLINK_INSTALL/bin/}}} directory) in a text editor.
# Locate the {{{[Protocol TCP]}}} section of the file.
# Record the value passed to {{{Listen}}}, if you use Release 4.x or later. If you use Release 3.x or earlier, record the value passed to {{{PortLow}}}. (Often the {{{Listen}}} and {{{PortLow}}} values are identical.)
# Exit the file.
# Pass the appropriate port number in your JDBC connection strings.

These errors may also be caused by resource exhaustion on the Broker or JDBC client host.  Kernel tuning may resolve the issue, by increasing open file, network handle, and other limits.  Specific tuning varies with the environment, including the operating system, hardware, and other software running thereon.

 <i><b>Release 3.x and earlier users only:</b> If the problem persists, confirm that the appropriate JDBC agent is specified in your connection URLs. URLs targeting Unix Brokers should always use {{{JDBCAGENT=judbc}}}. In most instances, URLs targeting Windows Brokers should use {{{JDBCAGENT=jodbc}}}. However, some SQLServer users will find that {{{JDBCAGENT=judbc}}} resolves "network read" errors.</i>


==Evidence==

* JDBC Connect String
* Request Broker Rulebook
* Request Broker Log