[jboss-jira] [JBoss JIRA] (WFLY-6674) Infinispan subsystem cache configuration is lost when cache is created
[
https://issues.jboss.org/browse/WFLY-6674?page=com.atlassian.jira.plugin....
]
Ariel Carrera updated WFLY-6674:
--------------------------------
Steps to Reproduce:
1- Clone my test project from https://github.com/arielcarrera/test-infinispan-wildfly10
2- Install Wildfly 8 and Wildfly 10
3- Compile my test project.
5- Start wildfly 10.
6- Run my-project/config.cli to add infinispan subystem configuration to
standalone-full.xml (or standalone.xml).
7- Restart wildfly.
8- Deploy my test project into wildfly 10
9- Test open a browser with this get url:
http://localhost:8080/test-infinispan-wildfly10/test
10- Check the output.
11- Repeat the process with Wildfly 8.
12- Compare outputs (expected behavior like wildfly 8).
was:
1- Clone my test project from https://github.com/arielcarrera/test-infinispan-wildfly10
2- Install Wildfly 8 and Wildfly 10
3- Compile my test project.
5- Start wildfly 10.
6- Run my-project/config.cli to add infinispan subystem configuration to
standalone-full.xml (or standalone.xml).
7- Restart wildfly.
8- Deploy my test project into wildfly 10
9- Test open a browser with this get url:
http://localhost:8080/test-infinispan-wildfly10/test
10- Check the output steps.
11- Repeat the process with Wildfly 8.
12- Compare outputs (expected behavior like wildfly 8).
Infinispan subsystem cache configuration is lost when cache is
created
----------------------------------------------------------------------
Key: WFLY-6674
URL: https://issues.jboss.org/browse/WFLY-6674
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.Final
Environment: Windows 10
Wildfly 10.0.0.Final
Java 8
Reporter: Ariel Carrera
Assignee: Paul Ferraro
Labels: cache, configuration, infinispan
Infinispan subsystem configuration is lost when cache is created.
If it is helpful.
After startup and created the cache, it is not configured with the specified settings in
Wildfly's Infinispan Subsystem.
This can be verified by monitoring the jboss.infinispan nodes with JConsole retrieving
the cache settings or running my simple test project.
Entities never expire/invalidate. The lifespan/max-entries are set to -1.
I made a simple test project to validate the problem. It is prepared to run with Wildfly
8 and 10.
https://github.com/arielcarrera/test-infinispan-wildfly10
I found an old issue (https://issues.jboss.org/browse/WFLY-3858) about wildfly 8 but this
problem talks about a security config problem and is a little different. It is a problem
about wildfly 10 configuration and it is working OK on wildfly 8.2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)