1:10 p.m.
I'm seeing the MEJB fail to deploy in the cts configuration due to the
CachedConnectionInterceptor not being found. Was this dropped in the
current jca refactoring?
11:05:02,492 INFO [EjbModule] Deploying MEJB
11:05:02,965 WARN [EjbModule] Could not load the
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
interceptor for this container
javax.management.InstanceNotFoundException:
jboss.jca:service=CachedConnectionManager is not registered.
at
org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:527)
at
org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:559)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.<init>(CachedConnectionInterceptor.java:78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:986)
at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:871)
at
org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.java:668)
at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:622)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:376)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167)
at $Proxy0.create(Unknown Source)
at
org.jboss.system.microcontainer.CreateDestroyLifecycleAction.installAction(CreateDestroyLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
2:38 p.m.
Its still defined in the jbossjca-service.xml so I need to drill into
whether the dependencies have changed.
Scott M Stark wrote:
I'm seeing the MEJB fail to deploy in the cts configuration due
to the
CachedConnectionInterceptor not being found. Was this dropped in the
current jca refactoring?
11:05:02,492 INFO [EjbModule] Deploying MEJB
11:05:02,965 WARN [EjbModule] Could not load the
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
interceptor for this container
javax.management.InstanceNotFoundException:
jboss.jca:service=CachedConnectionManager is not registered.
at
org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:527)
at
org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:559)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.<init>(CachedConnectionInterceptor.java:78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:986)
at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:871)
at
org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.java:668)
at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:622)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:376)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at
3 p.m.
Its the same dependency that has always existed when using the
CachedConnectionInterceptor. Its just been dropped from the ejb2
deployer. The EjbDeployer.deploy should be adding this to the list of
jmx service dependencies for legacy EjbModule mbean. I'll add that.
Scott M Stark wrote:
Its still defined in the jbossjca-service.xml so I need to drill
into
whether the dependencies have changed.
4:24 p.m.
This is fixed by adding a cachedConnectionManagerName property to the
EjbDeployer, which is propagated as a dependency to the EjbModules it
creates. If the ccm should not be used just remove the
cachedConnectionManagerName property from the EjbDeployer.
<bean name="EJB2xDeployer"
class="org.jboss.ejb.deployers.EjbDeployer">
<install bean="MainDeployer" method="addDeployer">
<parameter>
<this/>
</parameter>
</install>
<uninstall bean="MainDeployer" method="removeDeployer">
<parameter>
<this/>
</parameter>
</uninstall>
<!-- The EJBDeployer needs the JTA transaction manager service -->
<property
name="transactionManagerServiceName">jboss:service=TransactionManager</property>
<!-- The dynamic class loading simple web server -->
<property
name="webServiceName">jboss:service=WebService</property>
<!-- The CachedConnectionManager service used by the
CachedConnectionInterceptor -->
<property
name="cachedConnectionManagerName">jboss.jca:service=CachedConnectionManager</property>
</bean>
Scott M Stark wrote:
Its the same dependency that has always existed when using the
CachedConnectionInterceptor. Its just been dropped from the ejb2
deployer. The EjbDeployer.deploy should be adding this to the list of
jmx service dependencies for legacy EjbModule mbean. I'll add that.
6:17 a.m.
There is also another bug report about this.
http://jira.jboss.com/jira/browse/JBAS-3798
The EJBContainer/interceptors should
not be accessing external mbeans from "create",
this should be from "start" otherwise the CCM might not be initialised
properly.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
6604
days inactive
6605
days old
jboss-development@lists.jboss.org
4 comments
2 participants
participants (2)
-
Adrian -
Scott M Stark