I'm gonna tell on myself on this one... and it embarrases me more than
I can say.
I had written a DBManager class that manages connections. It was a
first iteration and I was just using the simple
DriverManager.getConnection(....) method before tackling connection
pooling.
In the DBManager class where I had my "getConnection()" method, I had
my standard JDBC try... catch... finally.... block. I got the
connection, but in my finally block... like I ALWAYS do when I write a
try... catch... finally.... block, I closed the resources. One of
which was the "connection".... :(
Hence, the IO error.....
Thanks for the answer.... once I began looking at the code to give you
an example, I found it.
Stephen McConnell
--- Oliver Jowett <oliver@opencloud.com> wrote:
> Stephen McConnell wrote:
>
> > Exception: java.io.IOException: Stream closed
> > Stack Trace:
> > java.io.IOException: Stream closed
>
> > Others have said this is a TCP/IP problem with a firewall, but it's
> > pretty apparent that since I'm accessing "localhost"
> > (jdbc:postgresql://localhost:5432/test_database) that It's not a
> > "firewall" problem UNLESS there's a problem with the Windoz XP
> > firewall.
>
> No, it doesn't look like a firewall problem -- that usually manifests
> as
> a connection refused or a connection reset by peer. This looks like
> the
> driver is closing the connection itself, but not invalidating the
> connection. I'd suspect an earlier error on the connection is causing
> this.
>
> Do you have a complete testcase I can try?
>
> -O
>
=====