Обсуждение: Re: [BUGS] BUG #6684: An I/O error occured while sending to the backend

wbrana  wrote:

> PostgreSQL 9.2devel JDBC4 (build 1000)

Just as a diagnostic step, can you check whether it still happens if
you use the latest production release?:

http://jdbc.postgresql.org/download.html#current

-Kevin

This is almost always a problem with a router or the network.

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca


On Mon, Jun 11, 2012 at 8:14 AM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> wbrana  wrote:
>
>> PostgreSQL 9.2devel JDBC4 (build 1000)
>
> Just as a diagnostic step, can you check whether it still happens if
> you use the latest production release?:
>
> http://jdbc.postgresql.org/download.html#current
>
> -Kevin
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc

Dave Cramer <pg@fastcrypt.com> wrote:
> This is almost always a problem with a router or the network.

I agree.  This is reinforced by the off-list response I got from the
OP [BTW, wbrana, please keep the list copied in the future], which
was that he was using the 9.2devel jar, but that when he tried the
current production jar he still got the error but at a different
point in the test.  I'm betting a firewall is shutting down the
connection.

-Kevin

Correct me if I am wrong but is this on a Windows machine ? If so is
the firewall on ?

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca


On Mon, Jun 11, 2012 at 10:13 AM, wbrana <wbrana@gmail.com> wrote:
> On Mon, Jun 11, 2012 at 4:00 PM, Kevin Grittner
> <Kevin.Grittner@wicourts.gov> wrote:
>> Dave Cramer <pg@fastcrypt.com> wrote:
>>> This is almost always a problem with a router or the network.
>>
>> I agree.  This is reinforced by the off-list response I got from the
>> OP [BTW, wbrana, please keep the list copied in the future], which
>> was that he was using the 9.2devel jar, but that when he tried the
>> current production jar he still got the error but at a different
>> point in the test.  I'm betting a firewall is shutting down the
>> connection.
>>
>> -Kevin
> Another version of jar didn't change point of error.
> Database server is running at same PC as client.
> I can't reproduce error with client written in C++, but I will try more.

On Mon, Jun 11, 2012 at 4:00 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Dave Cramer <pg@fastcrypt.com> wrote:
>> This is almost always a problem with a router or the network.
>
> I agree.  This is reinforced by the off-list response I got from the
> OP [BTW, wbrana, please keep the list copied in the future], which
> was that he was using the 9.2devel jar, but that when he tried the
> current production jar he still got the error but at a different
> point in the test.  I'm betting a firewall is shutting down the
> connection.
>
> -Kevin
Another version of jar didn't change point of error.
Database server is running at same PC as client.
I can't reproduce error with client written in C++, but I will try more.

Error occurs with 1.7.0_04; Java HotSpot(TM) 32-bit Client VM 23.0-b21,
but can't reproduce with 1.6.0_32; Java HotSpot(TM) 64-Bit Server VM 20.7-b02
Disconnect isn't related to COMMIT, but time.

On Mon, Jun 11, 2012 at 4:32 PM, Dave Cramer <pg@fastcrypt.com> wrote:
> Correct me if I am wrong but is this on a Windows machine ? If so is
> the firewall on ?
This is Linux machine. Firewall is on.

On Mon, Jun 11, 2012 at 5:30 PM, wbrana <wbrana@gmail.com> wrote:
> Error occurs with 1.7.0_04; Java HotSpot(TM) 32-bit Client VM 23.0-b21,
> but can't reproduce with 1.6.0_32; Java HotSpot(TM) 64-Bit Server VM 20.7-b02
> Disconnect isn't related to COMMIT, but time.
Error occurs with 1.6.0_32; Java HotSpot(TM) 32-bit Client VM 20.7-b02,
but can't reproduce with 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21
Time of disconnect is different between 1.7 and 1.6.