[ https://issues.redhat.com/browse/TEIIDSB-155?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-155: ---------------------------------------- The take-aways: 1. The underlying exception is misleading. It's not an authorization issue, it's that if the cache would be created using the default template it would not support transactions. 2. You have to use an xml configuration (or install a cache template) that specifies a transactional cache. It also must specify locking PESSIMISTIC as the default OPTIMISTIC requires versioning. I do not see any built-in cache templates that are transactional. This means that our connection code is effectively responsible for fully defining the cache - which does not seem ideal. That probably needs externalized in some way. 3. getCache will throw an exception in the transactional case rather than returning a null cache. The connection code needs to be updated accordingly. -- This message was sent by Atlassian Jira (v7.13.8#713008)