> On Nov 27, 2017, at 7:40 PM, Alex Buckley <alex.buck...@oracle.com> wrote: > > On 11/27/2017 5:22 PM, Michael Hall wrote: >>> On Nov 27, 2017, at 7:15 PM, Alex Buckley <alex.buck...@oracle.com >>> <mailto:alex.buck...@oracle.com>> wrote: >>> >>> --add-modules java.transaction >> >> Tried to simplify. >> >> java -cp . --patch-module java.transaction=jta.jar --add-modules >> java.transaction ModuleForClass javax.transaction.UserTransaction >> Error occurred during initialization of boot layer >> java.lang.LayerInstantiationException: Package javax.transaction.xa in >> both module java.transaction and module java.sql > > Oh yes, jta.jar includes the XA package, so force-patching that package into > java.transaction will conflict with the same package in java.sql. > > If your app doesn't use JDBC, then you could prevent java.sql from being > resolved by passing the JDK modules that you DO want to be resolved to the > --limit-modules option. Being precise about your app's use of JDK modules is > a down payment on writing its module declaration. > > But most likely, you need the new, XA-less JTA jar which is coming soon from > the JSR 907 Maintenance Lead. > > Alex
Thanks again, for the time. It is a little difficult for me to track these things. For now I will probably just omit java.corba and hope it isn’t really my problem with JMX attach. I will take a closer look at jconsole to try and figure that out. I will maybe check back on the newer JTA later.
