Replies: 3 comments 2 replies
-
Thanks for reaching out. I'm not a user of Looking at the code, there seems to be some interaction with entities while you work with |
Beta Was this translation helpful? Give feedback.
-
Hey @favna , this is a batch processing job and was set up such that it could work without transactions for the Essentially, And also important, it is a Greenplum database. And I don't understand why a Java 11 to Java 17 update would cause this problem. |
Beta Was this translation helpful? Give feedback.
-
Updating this thread with a link to a WIP repro. Sadly I have to actually properly reproduce the issue, as I'm currently running into a completely different problem, namely:
I suspect the dummy data I am generating is invalid somehow. |
Beta Was this translation helpful? Give feedback.
-
Hi there,
I'll preface by stating that I'm in the same team that @ArjanSchouten used to be in when he created #500 (he has since departed us, lest I'd first ask him directly)
I am updating one of our applications that uses the in #500 added
COPY IN
support from Java 11 to Java 17. As part of that I am now using the by this library provided methods in an update of our utility library that uses those functions. So far I've had success with this in other applications, however, the current one has the unique challenge of having to run within an@Transactional
and no matter what I try the process always completely halts by the time it gets to the part where it's supposed to do theCOPY IN
query.Our utility/wrapper class is as follows:
We call this function a few levels deep in our application so here's the relevant code bits:
Lastly, this is where the extract function from the block above gets called and as you can see I do block the reactive stream here, so it isn't just as simple as not subscribing/blocking.
The last log line that I see before the process hangs is from
log.debug("store :: extractionId={}, loadCycleId={}, queryId={}", extractionId, loadCycleId, queryId);
and if I write that particular function like so:Then I do see the rows being logged and they all look correct, which leads me to believe that the hanging process occurs somewhere in the
COPY IN
.I have also tried to change the syntax of the
copyIn
method inCopyInTemplate
to:so it doesn't use
Mono.usingWhen()
and doesn't close the connection in the asyncCleanup for that method but this still has the process hang.I'm absolutely entirely out of ideas on how to solve this issue and
COPY IN
really is a big must for us because we're talking about inserting upwards of 150_000 rows at the minimum or 700_000 at a more common occurrence and even that is with a vastly limited dataset so it's only going to grow and grow.All that said I could really use some help here to get the
COPY IN
functional within an@Transactional
.Some version info:
Beta Was this translation helpful? Give feedback.
All reactions