Michal Politowski <mpol...@meep.pl> writes:
> Thinking aloud: If this is, as it is to be suspected, an application-side
> problem,
> there is at first sight not much space in the application where it could
> hide. The data is
> mixed up in a driver buffer, two method calls from the standard library
> socket code. There is the VisibleBufferedInputStream there. Could it do
> something like this? Maybe if the connection was erroneously used from two
> threads
> concurrently? The connections are pooled via commons-dbcp BasicDataSource
> and queries are executed via Spring JdbcTemplate within Spring-configured
> transaction. No passing connections by hand anywhere, everything should be
> nicely thread-bound. Still, if not here, where could it go wrong?
You'd probably be better off asking these questions in pgsql-jdbc ...
a lot of us here don't even speak Java.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
