Hi Thorsten, Thank you very much for your thorough analysis. As if we needed another reason for getting rid of JAXB :) jOOQ 3.12, which finally officially supports Java 11+ will have replaced the JAXB implementation by our own, internally, to get rid mostly of the numerous issues caused by the removal of JAXB from the JDK. Great to hear that your issue will likely also be solved by jOOQ 3.12 - at least if you're going to run it on Java 11+
If there's anything you think we should fix on our side in the existing JAXB integration, please let us know. This seems to be difficult to reproduce, so if you can offer a test case / MCVE that would be great, of course: https://github.com/jOOQ/jOOQ-mcve. For example, this particular fix seems to be easy to implement: https://stackoverflow.com/a/3285931/521799. If you could patch your version and try this fix to see if this OOM still happens, we'd love to apply the patch to 3.11 and 3.10. On Sun, Jun 2, 2019 at 3:05 PM Thorsten Schöning <[email protected]> wrote: > So these jOOQ-classes got my attention and it seems that I'm suffering > from the same problem like mentioned on SO. The only problem is I > didn't find anyone else having the same problem with jOOQ and Java 8, > which makes me wonder. > Indeed, I'm not aware of any such issue yet > If my investigation is correct and others simply did not run into > this pretty often yet, jOOQ might want to consider backporting one of > the SO-fixes mentioned to older versions as well. I'm afraid that is unlikely going to happen. The path towards this MiniJAXB replacement was rocky, and even in jOOQ 3.12, when JAXB is on the classpath, that will be preferred over MiniJAXB, the latter being a replacement only in cases where the tedious transitive dependency has not already been added. jOOQ 3.11 has had its 11th patch release, so I would not want to introduce anything as big as an entire dependency replacement now this late in the patch release "chain" given that the expectation for an upgrade to a high patch release number is to be increasingly riskless. Working around the problem directly using a workaround like the above linked one seems more desireable for 3.11 > Because fomr my > understanding of the problem, everyone should run into this in > persistent environment with long-running JVMs sooner or later. > I'm quite convinced that a lot of people use jOOQ in long-running JVMs. Given that this particular issue has not popped up on this list, stack overflow, or github yet, I think this might just not be such a frequent issue. What jOOQ/JAXB feature are you using at runtime? The main reason for the JAXB dependency is for the code generator to load XML. There are more edge-casey reasons around using the InformationSchema types, or Settings... -- 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/CAB4ELO6M2pW43DhMbDsLmqzN67NFH9w5N6v9-fZNcMiX6n0kjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
