[jboss-jira] [JBoss JIRA] (AS7-2397) Infinispan subsystem is not functional unless the jpa one activated.

[Paul Ferraro (Reopened) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro reopened AS7-2397:
-------------------------------


    
> Infinispan subsystem is not functional unless the jpa one activated.
> --------------------------------------------------------------------
>
>                 Key: AS7-2397
>                 URL: https://issues.jboss.org/browse/AS7-2397
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, JPA / Hibernate
>    Affects Versions: 7.1.0.Alpha1
>         Environment: Technically it was Alpha 2.
>            Reporter: Shane Johnson
>            Assignee: Paul Ferraro
>              Labels: Infinispan
>
> Problem: Can't start a custom cache container without starting Hibernate.
> I now realize that I could not get at the Infinispan cache via JNDI because of AS7-1656. I've decided to simply start it eagerly.
> However, if I start an Infinispan cache eagerly then I get an exception that transactions are required and a transaction manager has not been properly configured. Seems that the default Infinispan cache configuration is transactional, but the allowed values to override this do NOT include non transactional like the standard Infinispan configuration does.
> Caused by: org.infinispan.CacheException: This is transactional cache but no transaction manager could be found. Configure the transaction manager lookup properly.
> The only way to get this to work is to add a persistence.xml file and configure the transaction manager and second level cache. I need to first deploy my application. Then I can go back and add the infinispan resource (via Maven). Since Hibernate is up and running, my custom cache container is able to start.
> Solution: Remove the coupling between Hibernate/Transactions and Infinispan.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira