HI Marco, If I read the code correct, it tries to create versions based on timestamps, so not 2 versions (created by a single session) have the same timestamp. Given non-granular timestamps (Windows would be problematic here) and a high frequency of calls could lead to delays to arrive at the next timestamp.
Alternatively, can you check if you have a "jcr:date" with a timestamp in the future in the node you want to checkin? Jörg Am Do., 12. Dez. 2024 um 08:40 Uhr schrieb Marco Piovesana < [email protected]>: > Hi Jörg, > yes I'm using the same session across multiple threads, multiple rest > requests to be more precise. They're not done at high frequency though, > they're requests coming from user's and the app was used by just a couple > of them. The machine it's running Ubuntu 20.04. > > Marco. > > On Wed, Dec 11, 2024 at 11:20 PM Jörg Hoh <[email protected]> > wrote: > > > Hi Marco, > > > > wild guess: Are you using the same session across multiple threads and > > doing this operation at a high frequency? Are you running that on > Windows? > > > > Jörg > > > > Am Mi., 11. Dez. 2024 um 14:26 Uhr schrieb Marco Piovesana < > > [email protected]>: > > > > > Hi Manfred, > > > here is the dump (I removed from the stacktrace the calls to our > > > proprietary classes since I'm not sure what I can share about them) > > > > > > 2024-12-10 16:27:52 > > > Full thread dump OpenJDK 64-Bit Server VM (11.0.12+7 mixed mode): > > > [...] > > > > > > > > > -- > > https://cqdump.joerghoh.de > > > > -- > <https://25.esteco.com> > -- https://cqdump.joerghoh.de
