[
https://issues.jboss.org/browse/WFLY-4613?page=com.atlassian.jira.plugin....
]
ofbiz brazil reopened WFLY-4613:
--------------------------------
Without start="EAGER", how can I make sure a cache container will be there when
I look it up in JNDI? Our application does the JNDI lookup at startup, so that we can
detect missing cache configuration during deployment, but without start="EAGER"
it fails:
Caused by: javax.naming.NameNotFoundException: infinispan/container/zanata [Root exception
is java.lang.IllegalStateException]
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at
org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at org.zanata.util.ServiceLocator.getJndiComponent(ServiceLocator.java:82)
at org.zanata.cache.CacheContainerProducer.initialize(CacheContainerProducer.java:56)
... 38 more
Caused by: java.lang.IllegalStateException
at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:138)
at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
... 48 more
Infinispan cache container does not accept EAGER start
------------------------------------------------------
Key: WFLY-4613
URL:
https://issues.jboss.org/browse/WFLY-4613
Project: WildFly
Issue Type: Feature Request
Components: Build System, Clustering, ConfigAdmin, EE, Naming
Affects Versions: 9.0.0.CR1
Environment: Wildfly 9.0.0 CR1, Windows 7, Solaris, Java 8u40
Reporter: ofbiz brazil
Assignee: Paul Ferraro
At cache container the property start gives error if we set EAGER.
Message error:
WFLYCTL0248: Invalid value EAGER for start; legal values are [LAZY]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)