[EJB/JBoss] - Error installing to Configured: name=EJB3EntityEvictionConfi
by Danives
Hi,
I am posting this question as I cannot find any other data or information regarding this error. We are using JBoss Beta4 and sometimes when we attempt to start up our JBoss client, we are presented with the following error
2009-01-13 16:47:52,829 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Configured: name=EJB3EntityEvictionConfig state=Instantiated
| java.lang.UnsupportedOperationException
| at java.util.AbstractList.add(AbstractList.java:151)
| at java.util.AbstractList.add(AbstractList.java:89)
| at org.jboss.beans.metadata.plugins.AbstractCollectionMetaData.getValue(AbstractCollectionMetaData.java:115)
| at org.jboss.kernel.plugins.dependency.PropertyDispatchWrapper.execute(PropertyDispatchWrapper.java:82)
| at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108)
| at org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:108)
| at org.jboss.kernel.plugins.dependency.ConfigureAction.setAttributes(ConfigureAction.java:88)
| at org.jboss.kernel.plugins.dependency.ConfigureAction.installActionInternal(ConfigureAction.java:45)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46)
| at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
| at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398)
| at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:69)
| at org.jboss.system.deployers.TempBeanMetaDataDeployer.deploy(TempBeanMetaDataDeployer.java:48)
| at org.jboss.system.deployers.TempBeanMetaDataDeployer.deploy(TempBeanMetaDataDeployer.java:35)
| at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
| at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
| at org.jboss.Main.boot(Main.java:208)
| at org.jboss.Main$1.run(Main.java:534)
| at java.lang.Thread.run(Thread.java:595)
| 2009-01-13 16:47:53,751 INFO [org.jboss.invocation.unified.server.UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha
|
This happens at the very start of JBoss start-up. Originally we believed it to be because we had specified too many regions in the ejb3-entity-cache-beans.xml file...however we have now reduced this to just 5 regions. I assume that there must be something wrong with the file, however I fail to understand why sometimes JBoss accepts it fine, and other times it does not. Can anyone possibly help me discover what is causing this issue? Here is the ejb3-entity-cache-beans.xml contents:
<?xml version="1.0" encoding="UTF-8"?>
|
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
|
| <!-- First we create a Configuration object for the cache -->
| <bean name="EJB3EntityCacheConfig"
| class="org.jboss.cache.config.Configuration">
|
| <!-- Externally injected services -->
| <property name="runtimeConfig">
| <bean name="EJB3EntityCacheRuntimeConfig" class="org.jboss.cache.config.RuntimeConfig">
| <property name="transactionManager"><inject bean="jboss:service=TransactionManager" property="TransactionManager"/></property>
| <property name="muxChannelFactory"><inject bean="JChannelFactory"/></property>
| </bean>
| </property>
|
| <property name="multiplexerStack">${jboss.multiplexer.stack:udp}</property>
|
| <property name="clusterName">${jboss.partition.name:DefaultPartition}-EntityCache</property>
|
|
|
| <!--
| Node locking level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <property name="isolationLevelString">REPEATABLE_READ</property>
|
| <!-- Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| -->
| <property name="cacheModeString">REPL_SYNC</property>
|
| <!-- The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <property name="stateRetrievalTimeout">15000</property>
|
| <!-- Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <property name="syncReplTimeout">20000</property>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <property name="lockAcquisitionTimeout">15000</property>
|
| <property name="exposeManagementStatistics">true</property>
|
| <!-- Must be true if any entity deployment uses a scoped classloader -->
| <property name="useRegionBasedMarshalling">true</property>
| <!-- Must match the value of "useRegionBasedMarshalling" -->
| <property name="inactiveOnStartup">true</property>
|
| <!-- Specific eviction policy configurations. This is LFU -->
| <property name="evictionConfig">
| <bean name="EJB3EntityEvictionConfig" class="org.jboss.cache.config.EvictionConfig">
| <property name="defaultEvictionPolicyClass">org.jboss.cache.eviction.LFUPolicy</property>
| <property name="wakeupIntervalSeconds">10</property>
| <property name="evictionRegionConfigs">
| <list>
| <!-- Default region will never timeout -->
| <bean name="EJB3EntityDefaultEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/_default_</property>
| <property name="evictionPolicyConfig">
| <bean name="EJB3EntityDefaultLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
|
| <!-- EJB3 integration code will programatically create other
| regions as beans are deployed -->
|
| <!-- Manual addition to prevent eviction queue issue -->
| <bean name="RegionOneEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/capital_spreads/region1</property>
| <property name="evictionPolicyConfig">
| <bean name="RegionOneLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
|
| <bean name="RegionTwoEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/capital_spreads/region2</property>
| <property name="evictionPolicyConfig">
| <bean name="RegionTwoLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
|
| <bean name="RegionThreeEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/capital_spreads/region3</property>
| <property name="evictionPolicyConfig">
| <bean name="RegionThreeLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
|
| <bean name="RegionFourEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/capital_spreads/region4</property>
| <property name="evictionPolicyConfig">
| <bean name="RegionFourLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
|
| <bean name="RegionFiveEvictionRegionConfig" class="org.jboss.cache.config.EvictionRegionConfig">
| <property name="regionName">/capital_spreads/region5</property>
| <property name="evictionPolicyConfig">
| <bean name="RegionFiveLFUConfig" class="org.jboss.cache.eviction.LFUConfiguration">
| <property name="maxNodes">10000</property>
| </bean>
| </property>
| </bean>
| </list>
| </property>
| </bean>
| </property>
|
| </bean>
|
| <!-- Now we use the above configuration to construct the cache itself -->
| <bean name="EJB3EntityCache" class="org.jboss.cache.jmx.CacheJmxWrapper">
|
| <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.cache:service=EJB3EntityTreeCache", exposedInterface=org.jboss.cache.jmx.CacheJmxWrapperMBean.class, registerDirectly=true)</annotation>
|
| <property name="configuration"><inject bean="EJB3EntityCacheConfig"/></property>
|
| </bean>
|
| </deployment>
|
We are using JBoss Beta 4, hopefully soon to be moving to GA - however I'd like to know if there is a possible solution as oposed to 'move to GA and see'. Thank you very much :)
Dan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202532#4202532
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202532
17 years, 5 months
[Microcontainer] - Re: Service POJO JNDI Binding Problem
by ralfsteppacher
"alesj" wrote :
| Try using my first suggestion with creating real AspectManager bean.
| Name it 'RealAspectManager' and then use this name in aspect/advice/interceptor.
|
No luck. This is the summary after server start-up:
| 16:59:18,472 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
|
| JndiBinding
| -> JndiAspect{Configured:**ERROR**}
|
| ModuleConfService
| -> HibernateConfigService{Configured:**ERROR**}
|
| ServiceLifeCycleDelegate
| -> ModuleConfService{Configured:Instantiated}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| JndiAspect -> java.lang.IllegalArgumentException: Null name | **ERROR**
|
| HibernateConfigService -> java.lang.VerifyError: Cannot inherit from final class | **ERROR**
|
Do you want me to post the full stacktrace?
My aop.xml now looks like this:
| <bean name="AOPJBossIntegration" class="org.jboss.aop.asintegration.jboss5.JBoss5Integration"/>
|
| <bean name="DefaultAspectManager" class="org.jboss.aop.microcontainer.beans.metadata.DefaultAspectManager">
| <property name="managerBean">AspectManager</property>
| <property name="managerProperty">aspectManager</property>
| </bean>
|
| <bean name="AspectManager" class="org.jboss.aop.deployers.AspectManagerJDK5">
| <constructor>
| ...
| </bean>
|
| <!-- Simplify name usage -->
| <bean name="RealAspectManager">
| <constructor factoryMethod="getAspectManager"><factory bean="AspectManager"/></constructor>
| </bean>
|
My jboss-beans.xml points to RealAspectManager for injection.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202530#4202530
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202530
17 years, 5 months
[Microcontainer] - Re: Service POJO JNDI Binding Problem
by alesj
"ralfsteppacher" wrote :
| Yes, aop.xml in the default server conf directory creates a bean with the name AspectManager and type org.jboss.aop.deployers.AspectManagerJDK5.
| Wich brings us back to square 1.
| org.jboss.aop.microcontainer.beans.Aspect and org.jboss.aop.microcontainer.beans.IntroductionBinding expect an org.jboss.aop.AspectManager to be injected. However, the injected Aspectmanager is of type org.jboss.aop.deployers.AspectManagerJDK5 (as defined in aop.xml).
|
|
| | java.lang.RuntimeException: Error configuring property: manager for JndiAspect
| | Caused by: java.lang.IllegalArgumentException: Wrong arguments. setManager for target org.jboss.aop.microcontainer.beans.Aspect@a43bbd expected=[org.jboss.aop.AspectManager] actual=[org.jboss.aop.deployers.AspectManagerJDK5]
| |
| | java.lang.RuntimeException: Error configuring property: manager for JndiIntroduction
| | Caused by: java.lang.IllegalArgumentException: Wrong arguments. setManager for target org.jboss.aop.microcontainer.beans.IntroductionBinding@96ea7d expected=[org.jboss.aop.AspectManager] actual=[org.jboss.aop.deployers.AspectManagerJDK5]
| |
|
Hmmm ... there is some misunderstanding here.
Either aspect/advice/inteceptor beans expect
- AspectManagerJDK5 + it has getAspectManager() method
- direct AspectManager bean
Try using my first suggestion with creating real AspectManager bean.
Name it 'RealAspectManager' and then use this name in aspect/advice/interceptor.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202517#4202517
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202517
17 years, 5 months