Thanks Lukas,
I think I may have to go down that path.  I believe the interjection of pg_bouncer has broken my setup.  I'm going to try another run without pgb, since my tomcat-only setup at AWS has not had the prepared statement issue.

Clarification request: From jooq perspective the prep'd statement is sent every time? Who knows it, the prep'd, as "S_4"?


On 2/11/22 13:41, Lukas Eder wrote:
Hi Rob,

jOOQ doesn't cache anything. It just creates a JDBC PreparedStatement behind the scenes. Not sure what's causing this in your case. Perhaps, using StatementType.STATIC_STATEMENT in your Settings could help? That prevents using PreparedStatements in jOOQ and runs everything with inlined parameters and static JDBC Statement types...

Lukas

On Fri, Feb 11, 2022 at 9:11 PM Rob Sargent <[email protected]> wrote:

    On 2/11/22 12:44, Rob Sargent wrote:
    I'm using jooq3.14, pg_bouncer, tomcat, postgres.  I have a long
    running process (20 hours) which starts with a select by id, does
    a million simulations, then does the select again (it's in a
    stateless servlet) and blows up with

        SQL [select "base"."markerset"."id",
        "base"."markerset"."name", "base"."markerset"."chrom",
        "base"."markerset"."genome_id",
        "base"."markerset"."avg_theta",
        "base"."markerset"."std_theta" from "base"."markerset" where
        "base"."markerset"."id" = cast(? as uuid)]; ERROR: prepared
        statement "S_4" does not exist

    Or is this pg_bouncer?


    I should have mentioned that pg_bouncer is using

        pool_mode = transaction

    And the line generating the exception is

                markersetRec =
        
dslContext.selectFrom(MARKERSET).where(MARKERSET.ID.equal(mid)).fetchOne();


    Sub-note:  with only 10,000 simulations the entire process works -
    or at least the one test run did.


-- You received this message because you are subscribed to the Google
    Groups "jOOQ User Group" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected].
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/jooq-user/3166861f-a427-0682-b729-c42ae3b4d39c%40gmail.com
    
<https://groups.google.com/d/msgid/jooq-user/3166861f-a427-0682-b729-c42ae3b4d39c%40gmail.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO6HLkGTLEtZDS_0CEfXcurji44-NDzRuzj9Hu-DLOXCwA%40mail.gmail.com <https://groups.google.com/d/msgid/jooq-user/CAB4ELO6HLkGTLEtZDS_0CEfXcurji44-NDzRuzj9Hu-DLOXCwA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups "jOOQ User 
Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jooq-user/5e4110f3-a659-d36d-fda1-a3f39f3ad877%40gmail.com.

Reply via email to