| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Michal Politowski <mpol+pg(at)meep(dot)pl> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Mixed up protocol packets in server response? | 
| Date: | 2011-06-03 13:53:59 | 
| Message-ID: | 25344.1307109239@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general pgsql-jdbc | 
Michal Politowski <mpol+pg(at)meep(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-03 14:09:33 | Re: Hidden Risk w/ UPDATE Cascade and Trigger-Based Validation | 
| Previous Message | Dean Rasheed | 2011-06-03 13:53:17 | Re: Hidden Risk w/ UPDATE Cascade and Trigger-Based Validation | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michal Politowski | 2011-06-03 14:13:48 | Re: Mixed up protocol packets in server response? | 
| Previous Message | Michal Politowski | 2011-06-03 13:03:57 | Re: Mixed up protocol packets in server response? |