| From: | "Vinay S (vinas)" <vinas(at)cisco(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com>, Kevin Wooten <kdubb(at)me(dot)com> |
| Cc: | Dave Cramer <davecramer(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC executeBatch() hangs without error |
| Date: | 2013-09-26 17:49:44 |
| Message-ID: | 3D2CB312427D204EAC2BCEB9771CB1951E3F5172@xmb-aln-x01.cisco.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
That sounds about right.
So, I'll try to play around with private static final int MAX_BUFFERED_QUERIES and update you guys.
Thanks a bunch.
- Vinay
-----Original Message-----
From: Kris Jurka [mailto:books(at)ejurka(dot)com]
Sent: Thursday, September 26, 2013 11:18 PM
To: Kevin Wooten
Cc: Vinay S (vinas); Dave Cramer; List
Subject: Re: [JDBC] JDBC executeBatch() hangs without error
On Thu, 26 Sep 2013, Kevin Wooten wrote:
> Could this be related to the note in QueryExecutorImpl.java ~ line 287
> titled "Deadlock Avoidance"?
> If I remember correctly it's specifically related to batched queries
> and synchronous TCP.
Almost certainly. The thing to look at is setting the network buffer sizes to use to large values to avoid the deadlock. The default values are machine dependent which also explains it working or not on different machines. These are unfortunately not documented, but were introduced in this commit:
https://github.com/pgjdbc/pgjdbc/commit/4e7f65b91e95d6249c78de6944f09cd34ef1ae87
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vinay S (vinas) | 2013-09-26 18:14:10 | Re: JDBC executeBatch() hangs without error |
| Previous Message | Kris Jurka | 2013-09-26 17:48:03 | Re: JDBC executeBatch() hangs without error |