WebLogic Boot: Weblogic.application.ModuleException__web

####<2012-9-12 03:53 P.M. 01 sec cst> <Error> <Deployer> <pangmc-PC> <AdminServer> <[ ACTIVE] Executethread: ' 0 ' for queue: ' Weblogic.kernel.Default (self-tuning) ' > <<wls kernel>> <> & Lt;> <1347436381984> <BEA-149231> <unable to set the activation state to true for the application ' DataS Ource0 '.
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)
>

When you configure a JDBC data source, Back-next's repeated clicks cause the Jndi name to wrap, so that files are automatically generated when the data source is created: Datasource0-3883-jdbc.xml
Path: D:\BEA\USER_PROJECTS\DOMAINS\BASE_DOMAIN\CONFIG\JDBC

Multiple <jndi-name></jndi-name> appear at the following location after opening the file, and the number is determined by the Jndi name newline blank line, such as:
<jdbc-data-source-params>
<jndi-name>jndi/db2bi</jndi-name>
<jndi-name></jndi-name>
<jndi-name></jndi-name>
<global-transactions-protocol>OnePhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>

As long as you delete or modify and re-create the data source, be aware that the Jndi name is not wrapped in a random line.