CachedConnectionInterceptor missing
by Scott M Stark
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)
19 years, 4 months
RE: [jboss-dev] Change to use pooled invoker as default invoker forJBossAS 4.2.0
by Dimitris Andreadis
AFAIR, I opened the task to record a request by acoliver. I agree we
don't really have to make this change, because of JB5.
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Tom Elrod
> Sent: Tuesday, November 28, 2006 5:14 AM
> To: JBoss.org development list
> Subject: Re: [jboss-dev] Change to use pooled invoker as
> default invoker forJBossAS 4.2.0
>
> Guess Dimitris would the best person to answer that since he
> entered the issue, but think it came out of discussion with
> Andy Oliver and myself.
> Some of the points made where that it can handle server
> bounces better (which is no longer true with the retry
> interceptor logic Brian added) and that performance is better
> based on casual testing (however I think Clebert and Phillip
> found unified invoker with jboss serialization to be the fastest?).
>
> I personally don't know if is worth the change on the 4.x
> branch since already have change to unified invokers for jbossas 5.
>
> Scott M Stark wrote:
> > Depends on what the driving motivation for switching to the pooled
> > invoker is.
> >
> > Tom Elrod wrote:
> >> For JBossAS 4.2.0.CR1, pooled invoker needs to be set to be the
> >> default detached invoker (per
> >> http://jira.jboss.com/jira/browse/JBAS-3733). This is
> pretty straight
> >> forward as far as standardjboss.xml is concerned, but
> there are many
> >> other places the jrmp invoker is referenced such as the
> >> 'jboss:service=ClientUserTransaction' service, the jmx
> invoker adaptor, and sprinkled throughout the testsuite and
> other places.
> >>
> >> So is a blanket change to pooled invoker required or just for the
> >> standardjboss.xml?
> >
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> >
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
19 years, 4 months
