2 Replies Latest reply: Apr 2, 2013 1:56 PM by 979497 RSS

    Error with JNDI when creating new data source

    979497
      Hi :

      This weekend, while adding new applications to the production environment we ran into a problem where the JNDI tree of the new managed servers was unreachable.

      The error message we saw was:

      ####
      <1364066840022> <BEA-149231> <Unable to set the activation state to true for the application 'EOI'.
      weblogic.application.ModuleException:
      at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:349)
      at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
      at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
      at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
      at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
      at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
      at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
      at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
      at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
      at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
      weblogic.common.ResourceException: is already bound
      at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:387)
      at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:136)
      at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:97)
      at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:346)
      at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
      at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
      at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
      at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
      at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
      at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
      at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
      at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
      at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
      at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
      at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
      at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)


      We traced the issue to a new data source that was added were we found that along with the the expected jndi name entry in the jdbc xml file, there were two blank entries:

      <jndi-name>weblogic.jdbc.DataSource.EOI</jndi-name>
      <jndi-name></jndi-name>
      <jndi-name></jndi-name>


      The data source was deleted, consoles restarted, the data source recreated and the issue occured again. To get by the issue we had to manually remove the blank tags from the xml file.

      We created 2 new data sources, and it only happened on the one. The same data source each time. Additionally, this issue did not occur when these changes were made in our lower (development, qa) regions.

      The version is the same in all three regions.

      WebLogic Version:     
      WebLogic Server Temporary Patch for 9324911 Wed Feb 03 22:38:01 PST 2010
      WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967


      Is this a known issue? And if so, is there a way to avoid it, other than to start constantly checking the newly created XML files?

      Thank you

      ted