Comments on: A Bridge Too Far

By: Mikhail

Mikhail — Thu, 08 Jan 2009 00:26:19 +0000

I think we just run into another of those combinations with generics where
matching is not done properly in BridgeMethodResolver. We are using spring 2.5.5.

Stack trace for "Unable to locate bridged method for bridge method"

Caused by: java.lang.IllegalStateException: Unable to locate bridged method for bridge method 'public volatile void com.bnpp.pb.tiger.dao.JournalSpaceDAO.cl
ear(java.lang.Object)'
at org.springframework.core.BridgeMethodResolver.findBridgedMethod(BridgeMethodResolver.java:89)
at org.springframework.transaction.interceptor.AbstractFallbackTransactionAttributeSource.computeTransactionAttribute(AbstractFallbackTransactionAtt
ributeSource.java:143)
at org.springframework.transaction.interceptor.AbstractFallbackTransactionAttributeSource.getTransactionAttribute(AbstractFallbackTransactionAttribu
teSource.java:100)
at org.springframework.transaction.interceptor.TransactionAttributeSourcePointcut.matches(TransactionAttributeSourcePointcut.java:36)
at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:214)
at org.springframework.aop.support.AopUtils.canApply(AopUtils.java:253)
at org.springframework.aop.support.AopUtils.findAdvisorsThatCanApply(AopUtils.java:287)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findAdvisorsThatCanApply(AbstractAdvisorAutoProxyCreator.java:113)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.findEligibleAdvisors(AbstractAdvisorAutoProxyCreator.java:85)
at org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreator.getAdvicesAndAdvisorsForBean(AbstractAdvisorAutoProxyCreator.java:66)

at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.wrapIfNecessary(AbstractAutoProxyCreator.java:360)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.postProcessAfterInitialization(AbstractAutoProxyCreator.java:324)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBe
anFactory.java:361)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1343)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)

JournalSpaceDAO doesn't declare method clear. It just inherits it from parent generic class.

public class JournalSpaceDAO extends GigaSpaceDAO {
}

public abstract class GigaSpaceDAO
extends NonCachingGigaSpaceDAO implements GenericCachingDAO
{
@Override
public void clear(
Collection entities_)
{
}

@Override
public void clear(
T entity_)
{
}

}

Thanks

By: Krishnadas

Krishnadas — Wed, 04 Jul 2007 14:08:44 +0000

Hi Rob Harrop,

i am getting a class cast exception.

here is senario….
i have an interface OMSApplicationController
public interface OMSApplicationController {
public String getName();
public void setName(String name);
public void init() throws OMSApplicationControllerException;
public void start() throws OMSApplicationControllerException;
public void stop()throws OMSApplicationControllerException;
public void processRequest(Object request);
}

and i am implementing this interface as one of my bean(Spring).

i am calling this bean from a message driven bean(TestTransactionApplicationController) like
testTransactionApplicationController = (TestTransactionApplicationController) getBeanFactory().getBean("testTransactionApplicationController");

when i annotate(@Transactional) any of the function in this bean
i get classcastexception error is given below

java.lang.ClassCastException: $Proxy161
at Listener.TestTransactionMsgListenerBean.onEjbCreate(TestTransactionMsgListenerBean.java:64)
at org.springframework.ejb.support.AbstractMessageDrivenBean.ejbCreate(AbstractMessageDrivenBean.java:79)
at Listener.TestTransactionMsgListenerBean.ejbCreate(TestTransactionMsgListenerBean.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.jee.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:325)
at com.bea.core.repackaged.springframework.jee.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:319)
at com.bea.core.repackaged.springframework.jee.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:313)
at com.bea.core.repackaged.springframework.jee.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMeta
data.java:592)
at weblogic.ejb.container.injection.EjbProxyMetadata.invokeLifecycleMethods(EjbProxyMetadata.java:160)
at com.bea.core.repackaged.springframework.jee.intercept.InterceptionMetadata$AdvisorChainProxyControl.invokeLifecycl
eMethod(InterceptionMetadata.java:544)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductio
nInterceptor.java:104)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocatio
n.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy158.invokeLifecycleMethod(Unknown Source)
at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:147)
at weblogic.ejb.container.injection.EjbComponentCreatorImpl.getBean(EjbComponentCreatorImpl.java:79)
at weblogic.ejb.container.manager.BaseEJBManager.createNewBeanInstance(BaseEJBManager.java:216)
at weblogic.ejb.container.manager.BaseEJBManager.allocateBean(BaseEJBManager.java:233)
at weblogic.ejb.container.manager.MessageDrivenManager.createBean(MessageDrivenManager.java:286)
at weblogic.ejb.container.pool.MessageDrivenPool.createBean(MessageDrivenPool.java:165)
at weblogic.ejb.container.pool.Pool.createInitialBeans(Pool.java:295)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDrivenManager.java:571)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerStart(MessageDrivenBeanInfoImpl.java:1140)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessageDrivenBeans(MessageDrivenBeanInfoImpl.java:
1092)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1676)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:1496)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:513)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentRecei
verCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCal
lbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallback
Deliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

By: Marc

Marc — Wed, 11 Apr 2007 07:18:24 +0000

Informtaive article, particularly as am having some issues with BridgeMethodResolver when resolvibg methods with Java 5.0 generics. I have posted a full explanation on Spring Forum (http://forum.springframework.org/showthread.php?t=37218) and would be most helpful if you take a look.
Thanks.

By: Marc

Marc — Tue, 10 Apr 2007 09:17:46 +0000

Very informative, particularly as I have recently had to look at BridgeMethodResolver due to an exception occuring within our Spring enabled application.
If possible could you have a look at the forum entry I have posted, and advise if this is one of the "complex cases that we have not yet accounted for" or just an error of usage by myself.
http://forum.springframework.org/showthread.php?t=37218

By: Erwin Vervaet

Erwin Vervaet — Wed, 17 Jan 2007 08:33:25 +0000

Nice article Rob!