[
https://issues.jboss.org/browse/WFLY-4562?page=com.atlassian.jira.plugin....
]
xiaodong xie commented on WFLY-4562:
------------------------------------
Sure, @Paul. I'm working on creating a test case that could reproduce this issue.
But it seems I cannot reproduce it right now. The thing that I noticed, is that, when I
failed to inject with @Resource, there is no log output "ISPN000128: Infinispan
version: Infinispan 'Insanely Bad Elf' 7.2.3.Final". So I suspect, the
Infinispan module was not ready, when the application tried to get a cache injected.
I'll continue to dig deeper, to see if I could find anything else...
Deprecate Infinispan container/cache start mode
-----------------------------------------------
Key: WFLY-4562
URL:
https://issues.jboss.org/browse/WFLY-4562
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Beta2
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 9.0.0.CR1
start="EAGER" was only added to the Infinispan subsystem for use by JDG - so
that a given container or cache service would install as ACTIVE rather than ON_DEMAND. In
the context of WildFly, we would never want this since the modules referenced by cache
entries may not yet be loaded. Many users configure start="EAGER" and
inevitably have issues during redeploy. Consequently, we should drop this from the
subsystem XSD altogether and deprecate it from the model.
Effectively, only start="LAZY" will be supported.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)