環境

Solaris 10 Enterprise
Weblogic 9.2.1.0

一、錯誤解決

今天上午，QA測試一同事的應用時，在建立JDBC連接池并綁定到JNDI時出錯，弄了許久，同事和QA都沒有辦法，同事把我拉過去幫忙看看如何解決，錯誤信息如下：
<2009-12-8 上午11時21分09秒 CST> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1260242468756' for task 'weblogic.deploy.configChangeTask.1'. Error is: 'weblogic.application.ModuleException: 'weblogic.application.ModuleException:at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:299)at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)Truncated. see log file for complete stacktrace weblogic.common.ResourceException: Failed to bind remote object (ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer null)/306 [weblogic.jdbc.common.internal.RemoteDataSource]) to replica aware stub at aidmm_ejb(ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer [6669962366907805753S::base_domain:AdminServer/289])/289 [weblogic.jdbc.common.internal.RemoteDataSource])at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:408)at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:144)at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:297)at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)Truncated. see log file for complete stacktrace > <2009-12-8 上午11時21分09秒 CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'aidmm_ejb'.> <2009-12-8 上午11時21分09秒 CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating activate task for application 'aidmm_ejb'.> <2009-12-8 上午11時21分09秒 CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004 weblogic.application.ModuleException:at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:299)at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)Truncated. see log file for complete stacktrace weblogic.common.ResourceException: Failed to bind remote object (ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer null)/306 [weblogi.jdbc.common.internal.RemoteDataSource]) to replica aware stub at aidmm_ejb(ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer [666996236907805753S::base_domain:AdminServer/289])/289 [weblogic.jdbc.common.internal.RemoteDataSource])at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:408)at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:144)at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:297)at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)Truncated. see log file for complete stacktrace > <2009-12-8 上午11時21分09秒 CST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException:at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:299)at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)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:815)at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:400)at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:63)at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:223)at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:125)at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:466)at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:720)at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) Caused by: weblogic.common.ResourceException: Failed to bind remote object (ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer null)/306[weblogic.jdbc.common.internal.RemoteDataSource]) to replica aware stub at aidmm_ejb(ClusterableRemoteRef(6669962366907805753S::base_domain:AdminServer [6669962 366907805753S::base_domain:AdminServer/289])/289 [weblogic.jdbc.common.internal.RemoteDataSource])at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:408)at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:144)at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:297)

原因/解決方法：

停止域（domain）。

進入$DOMAIN_HOME/servers/AdminServer目錄，清除其中 cache 目錄和 tmp 目錄下的所有內容。

重啟域。

問題解決。

<正文結束>

總結

以上是生活随笔為你收集整理的Weblogic - Failed to bind remote object 错误解决方法的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。