-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
When building a Bootable JAR app that uses the ejb and ejb-dist-cache layers, a hybrid configuration seems to be generated, including both local and distributed configurations for the distributable-ejb and infinispan subsystem.
Specifically such hybrid configuration relates to infinispan-timer-managment named resources (transient, persistent, distributed are all there) in the distributable-ejb subsystem and to local-cache and distributed-cache resources in the infinispan subsystem.
Here's a snippet from the configuration that is generated when building a bootable jar application with the above mentioned layers:
cat standalone.xml | grep distributable-ejb -A10 <subsystem xmlns="urn:jboss:domain:distributable-ejb:1.0" default-bean-management="default"> <infinispan-bean-management name="default" cache-container="ejb" cache="passivation" max-active-beans="10000"/> <infinispan-client-mappings-registry cache-container="ejb" cache="client-mappings"/> <infinispan-timer-management name="persistent" cache-container="ejb" cache="persistent" max-active-timers="10000"/> <infinispan-timer-management name="transient" cache-container="ejb" cache="transient" max-active-timers="10000"/> <infinispan-timer-management name="distributed" cache-container="ejb" max-active-timers="10000"/> </subsystem>
The feature packs and WildFly in general has been built from the WFLY-7628 feature topic branch.
- is related to
-
WFLY-7628 Allow to use an Infinispan cache as EJB timer store
-
- Closed
-