GenericTransactionManager detects incorrect transaction manager in GlassFish ---------------------------------------------------------------------------- Key: JBCACHE-1354 URL: http://jira.jboss.com/jira/browse/JBCACHE-1354 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Transactions Affects Versions: 2.1.1.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA "... a Glassfish internal TX manager is "found" resulting in lots of "not-implemented exceptions". The simple fix is to change the lookup order from private static String[][] knownJNDIManagers = { {"java:/TransactionManager", "JBoss, JRun4"}, {"java:comp/TransactionManager", "Resin 3.x"}, {"java:pm/TransactionManager", "Borland, Sun"}, {"java:appserver/TransactionManager", "Sun Glassfish"}, {"javax.transaction.TransactionManager", "BEA WebLogic"}, {"java:comp/UserTransaction", "Resin, Orion, JOnAS (JOTM)"}, }; to private static String[][] knownJNDIManagers = { {"java:/TransactionManager", "JBoss, JRun4"}, {"java:comp/TransactionManager", "Resin 3.x"}, {"java:appserver/TransactionManager", "Sun Glassfish"}, {"java:pm/TransactionManager", "Borland, Sun"}, {"javax.transaction.TransactionManager", "BEA WebLogic"}, {"java:comp/UserTransaction", "Resin, Orion, JOnAS (JOTM)"}, }; ... " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira