aspose file tools*
The moose likes BEA/Weblogic and the fly likes Are you man enough to answer this question? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Are you man enough to answer this question?" Watch "Are you man enough to answer this question?" New topic
Author

Are you man enough to answer this question?

Dave Alvarado
Ranch Hand

Joined: Jul 02, 2008
Posts: 436
Hi,

I'm using WL 9.2.2. I'm trying to create a datasource. I successfully tested the configuration, created my cluster with its server, and targeted the DS at the cluster. However, upon server startup, I get this baffling error ...

####<Sep 30, 2008 10:26:13 AM MDT> <Info> <JDBC> <rhonti> <nps-db-ms-1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1222791973180> <BEA-001517> <Connection Pool "NPS_HISTORY_DS" using Driver: "Oracle JDBC driver", Version: "10.2.0.2.0".>
####<Sep 30, 2008 10:26:16 AM MDT> <Info> <Common> <rhonti> <nps-db-ms-1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1222791976902> <BEA-000628> <Created "10" resources for pool "NPS_HISTORY_DS", out of which "10" are available and "0" are unavailable.>
####<Sep 30, 2008 10:26:16 AM MDT> <Info> <JDBC> <rhonti> <nps-db-ms-1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1222791976918> <BEA-001124> <Created Connection Pool named NPS_HISTORY_DS.>
####<Sep 30, 2008 10:26:16 AM MDT> <Info> <JDBC> <rhonti> <nps-db-ms-1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1222791976919> <BEA-001174> <Creating Data Source named NPS_HISTORY_DS, JNDI Name = NPS_HISTORY_DB,,.>
####<Sep 30, 2008 10:26:16 AM MDT> <Error> <Deployer> <rhonti> <nps-db-ms-1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1222791976973> <BEA-149231> <Unable to set the activation state to true for the application 'NPS_HISTORY_DS'.
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.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.common.ResourceException: is already bound
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)
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.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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)


What does it mean? Please let me know any additional info I should provide, - Dave
Philip Shanks
Ranch Hand

Joined: Oct 15, 2002
Posts: 189
Got me... is it a naming collision? That's what "weblogic.common.ResourceException: is already bound" suggests to me.


Philip Shanks, SCJP - Castro Valley, CA
My boss never outsources or has lay-offs, and He's always hiring. I work for Jesus! Prepare your resume!
David Karr
Greenhorn

Joined: Jan 06, 2008
Posts: 12
Did you ever resolve this? We're seeing the exact same symptom, in WL 9.2.2. A server that was working perfectly fine is now reporting this exception for both an Oracle and a DB2 datasource at startup (one other Oracle and two other Teradata DSes are perfectly fine). There's nothing unusual about the JNDI names we've defined for these two DSes. They obviously don't conflict with any other datasource. I'm going to file a support case, but I'm not hopeful they'll figure anything out quickly (if at all).
Dave Alvarado
Ranch Hand

Joined: Jul 02, 2008
Posts: 436
Hi, You have helped me out so many times in the Oracle/WebLogic group, I wish I could say this story had a happy ending. We never found the root cause to this. What we did instead was use an existing data source that was already running normally. We changed the permissions of that Oracle user to have access to the necessary data.

- Dave
John Page
Greenhorn

Joined: Oct 21, 2008
Posts: 1
This is a JNDI related exception. On the first page of your Weblogic JDBC/Data Source there is a text box for JNDI names. Fill this out very carefully paying special care to line breaks and blank spaces. The application parses this field and splits up entries that exist on separate lines as separate JNDI names. (You're allowed to have more than one) If, for example you have two extra line breaks after your JNDI names in the text field , Weblogic will complain that you already named a resource "" and can't have two resources registered as "".
David Karr
Greenhorn

Joined: Jan 06, 2008
Posts: 12
I found the problem in my domain, and it was because of the multiple jndi-name entries (the second one being blank). I sincerely doubt this has anything to do with newlines in the jndi name field. I've seen this happen in two different datasources that were working perfectly fine before. However, other fields were changed in the datasources since they had been working before. I expect there is a bug in the code that saves the datasource config that results in creation of additional jndi-name elements in the resulting XML descriptor.
pascal betz
Ranch Hand

Joined: Jun 19, 2001
Posts: 547
For me it was an additional line break in the JNDI Name field of the DataSource. Took me a while...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Are you man enough to answer this question?
 
Similar Threads
deployment in weblogic 10.1
Failed to start JMS Server
Servlet: "action" failed to preload on startup in Web application: "MyAPPName"
Does Struts have a log? Can't figure out why ActionServlet is not initializing
Geting Errors while Loading the Server