[ https://issues.jboss.org/browse/JBTM-3209?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3209: ----------------------------------- Description: The JTA TM runs well on application servers where applications typically run for extended periods of time giving plenty of scope for the JIT compiler to optimise the bytecode. Frameworks like Quarkus are particularly well suited to running short duration applications due to the faster startup times and often lower resource footprint but they can miss out on the benefits that JIT provides. This task is to check whether or not there are opportunites to improve startup time (and resource usage). If/when such changes are identified please raise a linked JIRA so that we can track any specific changes. was: Applications that consume the quarkus-narayana-jta extension incur a significant resource footprint because things like: - Lots of reflection going on. - TransactionManagerStatus is initialised during build (can't be reconfigured - moving it to "part runtime" needs some work) - It's still logging that ports are being opened during native-image (this confuses people during presentations as we say that's impossible) This list is not exhaustive and the task is to investigate where we can improve things -- This message was sent by Atlassian Jira (v7.13.8#713008)