Failed to bind remote object Weblogic

Oracle Weblogic Server

If in weblogic while configuring datasources you get failed to bind remote object weblogic errors like below in Admin console or in weblogic server log files then follow below steps to eliminate or find out the usual reason’s behind this error.

On Admin Console:

An error occurred during activation of changes, please see the log for details. 	
 	 	weblogic.application.ModuleException: 	
 	 	Failed to bind remote object (ClusterableRemoteRef(-1468378860128516902S:10.64.204.33:10.64.204.33,10.64.204.175:IProd:server1221 null)/325
 [weblogic.jdbc.common.internal.RemoteDataSource]) to replica aware stub at prodDataSource(ClusterableRemoteRef(-1468378860128516902S:12.64.204.33:12.64.204.33,12.64.204.175:IProd:server1121 [-1468378860128516902S:10.64.204.33:12.64.204.33,12.64.204.175:IProd:server1121/298, 1196223903559177698S:12.63.204.175:[7101,7101,-1,-1,-1,-1,-1]:10.64.204.33,10.64.204.175:IProd:server1212/290])/298 

[weblogic.jdbc.common.internal.RemoteDataSource])

In server logs:

 

<Nov 10, 2011 9:55:23 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>

<Nov 10, 2011 9:56:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>

<Nov 10, 2011 9:56:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>

<Nov 10, 2011 9:56:16 PM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'prodDatasource'.

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(932890607684791438S:1.......
[weblogic.jdbc.common.internal.RemoteDataSource]) to replica aware stub at prod(ClusterableRemoteRef(932890607684791438S:10.64.204.174:10.64.......
[932890607684791438S:10.64.204.174:10.......298  [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

 

The above errors may come while activating the datasource or while restarting a server after configurations.

Usually the root cause for this kind of bind exceptions are becuase of duplicate entries or already existing entries which are conflicting with each other while getting active and acquiring connections.

Make sure all the existing datasource Names and JNDI names are unique. If you find any JNDI name duplicated then make sure to make it unique or use the already existing JNDI if it works and connects to the same DB.

Once all are checked restart the managed server to re-initiate all datasources.In case if you are getting this error in your weblogic log file its better to remove the faulty datasource and reconfigure freshly post managed server restart to avoid errors.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.

Leave a Reply