Bug 1273454 - JDBC migration tool is missing JTA jar
Summary: JDBC migration tool is missing JTA jar
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Build
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: 6.6.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-20 13:13 UTC by Vojtech Juranek
Modified: 2022-05-31 22:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Vojtech Juranek 2015-10-20 13:13:11 UTC 
JDBC migration tool is missing java transaction API jar file, it fails with exception bellow. When added manually on class path, works fine.


Exception in thread "main" java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
        at org.infinispan.configuration.cache.TransactionConfigurationBuilder.<init>(TransactionConfigurationBuilder.java:32)
        at org.infinispan.configuration.cache.ConfigurationBuilder.<init>(ConfigurationBuilder.java:52)
        at org.infinispan.persistence.migrator.jdbc.JdbcUpgradeTool.initializeTargetStore(JdbcUpgradeTool.java:54)
        at org.infinispan.persistence.migrator.jdbc.JdbcUpgradeTool.<init>(JdbcUpgradeTool.java:48)
        at org.infinispan.persistence.migrator.jdbc.JdbcUpgradeTool.main(JdbcUpgradeTool.java:192)
Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        ... 5 more
Comment 3 Vojtech Juranek 2015-11-05 14:32:20 UTC 
JTA API jar is now added into the zip, but still fails with the same issue. If the JTA API jar needs to be added to the class path manually, it should be mentioned in README.txt, but I'd prefer it to be part of JDBC migrator jar.
Note You need to log in before you can comment on or make changes to this bug.