Closed SATISHEEEK closed 1 month ago
Try to minimize the number of moving parts. You seem to perform several upgrades at the same time. Maybe you should attempt a step by step upgrade approach with only one upgrade at a time, to see which upgrade introduces the problem.
I hope this helps. Teodor
Dear @teodord, thank you for your response. Unfortunately I have been able to isolate the problem. It's been related to Quarkus update, but the transaction is lost once it enters Jasper engine.
I did notice that JasperFillManager.fillReport() is a static method, but calling fill method like this unfortunately doesn't help either:
JasperFillManager manager = JasperFillManager.getInstance ( DefaultJasperReportsContext.getInstance() );
return manager.fill(reportFile, parameters, con);
We did not change anything in our JDBC query executers recently.
@teodord Thank you for fast reply. I'll keep digging in Quarkus changes to see why we're loosing the transaction in the process..
would you be, please, that kind and had a look at my follow-up question in https://github.com/TIBCOSoftware/jasperreports/issues/460
Thank you!
Dear Jasper devs, I am sorry to bother you again, but this whole migration has been huge challenge for us and I need your help once again... :(
We're getting a following SQLException while trying to execute a report.
This combination used to work fine with Quarkus2 + Jasper 6, unfortunately with Quarkus 3 + Jasper 7 we're getting an issue with an active transaction
Thank you for any hint!
log: