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

[Shane Johnson (Updated) (JIRA)]

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

Shane Johnson updated AS7-2397:
-------------------------------

    Description: 
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.

  was:
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.

If I try to get at an Infinispan cache container via @Resource using the JNDI mapped name, it is not found because it is in fact not created despite the subsystem being activated. It is only created if I add a persistence.xml file to my deployment with L2 caching enabled in order to activate the JPA subsystem. Once the JPA subsystem is activated it seems that the Infinispan subsystem is able to create the cache container and add the JNDI reference.

The Infinispan subsystem should not be dependent on the JPA subsystem.


    
> 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: Modules
>    Affects Versions: 7.1.0.Alpha1
>         Environment: Technically it was Alpha 2.
>            Reporter: Shane Johnson
>            Assignee: David Lloyd
>              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