The DataSource with the JNDI name could not be found
Ram
Hi,
I hv created my domain and was trying to test the example applications by moving
the example folder to my directory.
My directory is E:\bea\user_projects\mywork and in this directory I hv placed
the examples directory.Hence it look like,E:\bea\user_projects\mywork\examples
I hv modified the examples.properties to accomodate these changes.
I was able to build and run Stateless and Stateful session beans,but when i try
to run CMP it gives the error saying the datasource could not be found and hence
JNDI could not locate home interface class file.
It says it could not fine demoPool.
I hv not changed the descriptor files.
<data-source-name>examples-dataSource-demoPool</data-source-name>
Pl.advise.
Regards,
Ram
Rob Woollen
Connection pool. My guess is the connection pool was named demoPool,
and it failed. check the logfile for errors.
If you need more help, please post your server's log file.
-- Rob
Ram
Rob Woollen <rwoo...@please.noemail.com> wrote:
>CMP typically needs a DataSource. The DataSource needs a JDBC
>Connection pool. My guess is the connection pool was named demoPool,
>
>and it failed. check the logfile for errors.
>
>If you need more help, please post your server's log file.
>
I think the problem is the creation of Datasource only.Actually I am trying to
run the examples given in the default examples server from my user_projects instance
'Ram'.
The log file is:
==========
####<Feb 5, 2004 10:50:40 AM GMT+05:30> <Notice> <Security> <ram> <myserver> <main>
<<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
####<Feb 5, 2004 10:50:40 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<main> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "myserver"
for domain "ram">
####<Feb 5, 2004 10:50:53 AM GMT+05:30> <Warning> <JDBC> <ram> <myserver> <main>
<<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for
pool "Ram_A": Unable to connect to any hosts due to exception: java.net.ConnectException:
Connection refused: connect>
####<Feb 5, 2004 10:50:54 AM GMT+05:30> <Error> <JDBC> <ram> <myserver> <main>
<<WLS Kernel>> <> <BEA-001150> <Connection Pool "Ram_A" deployment failed with
the following error: 0:Could not create pool connection. The DBMS driver exception
was: Unable to connect to any hosts due to exception: java.net.ConnectException:
Connection refused: connect.>
####<Feb 5, 2004 10:50:54 AM GMT+05:30> <Error> <JDBC> <ram> <myserver> <main>
<<WLS Kernel>> <> <BEA-001151> <Data Source "Ram_B" deployment failed with the
following error: DataSource(Ram_JNDI) can't be created with non-existent Pool
(connection or multi) (Ram_A).>
####<Feb 5, 2004 10:51:05 AM GMT+05:30> <Warning> <Deployer> <ram> <myserver>
<ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004>
<Failures were detected while initiating Deploy task for application _appsdir_ejb20_basic_containerManaged_ear.>
####<Feb 5, 2004 10:51:05 AM GMT+05:30> <Error> <Deployer> <ram> <myserver> <ExecuteThread:
'3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed
to complete the deployment task with ID 1 for the application _appsdir_ejb20_basic_containerManaged_ear.
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for ejb20_basic_containerManaged.jar
Module: ejb20_basic_containerManaged.jar Error: Exception activating module:
EJBModule(ejb20_basic_containerManaged.jar,status=PREPARED)
Unable to deploy EJB: containerManaged from ejb20_basic_containerManaged.jar:
[EJB:011028]The DataSource with the JNDI name: examples-dataSource-demoPool could
not be located. Please ensure that the DataSource has been deployed successfully
and that the JNDI name in your EJB Deployment descriptor is correct.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2549)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2349)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2511)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for ejb20_basic_containerManaged.jar
Module: ejb20_basic_containerManaged.jar Error: Exception activating module:
EJBModule(ejb20_basic_containerManaged.jar,status=PREPARED)
Unable to deploy EJB: containerManaged from ejb20_basic_containerManaged.jar:
[EJB:011028]The DataSource with the JNDI name: examples-dataSource-demoPool could
not be located. Please ensure that the DataSource has been deployed successfully
and that the JNDI name in your EJB Deployment descriptor is correct.
]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2523)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
####<Feb 5, 2004 10:51:07 AM GMT+05:30> <Warning> <DRS> <ram> <myserver> <ExecuteThread:
'3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current
version 13 for DataIdentifier DataIdentifierID: 1 does not match with incoming
version 14 for a one-phase update.>
####<Feb 5, 2004 10:51:12 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<main> <<WLS Kernel>> <> <BEA-000360> <Server started in RUNNING mode>
####<Feb 5, 2004 10:51:12 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<ListenThread.Default> <<WLS Kernel>> <> <BEA-000355> <Thread "ListenThread.Default"
listening on port 7001, ip address *.*>
####<Feb 5, 2004 10:58:37 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<Graceful shutdown task> <<WLS Kernel>> <> <BEA-000365> <Server state changed
to SUSPENDING>
####<Feb 5, 2004 10:58:37 AM GMT+05:30> <Notice> <HTTP> <ram> <myserver> <Graceful
shutdown task> <<WLS Kernel>> <> <BEA-101278> <There are no active sessions. The
Web service is ready to suspend.>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Alert> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000228>
<The disabling of server logins has been requested by <WLS Kernel>>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Alert> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000229>
<Server logins have been disabled.>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000352>
<Thread "ListenThread.Default" stopped listening on port 7001>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000365>
<Server state changed to STANDBY>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000365>
<Server state changed to SHUTTING_DOWN>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Alert> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000218>
<Server shutdown has been requested by <WLS Kernel>>
####<Feb 5, 2004 10:58:39 AM GMT+05:30> <Alert> <WebLogicServer> <ram> <myserver>
<ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000219>
<The shutdown sequence has been initiated.>
========
Pl.advise
Ram
The server log is:
============
Rob Woollen
Ram wrote:
> Rob Woollen <rwoo...@please.noemail.com> wrote:
>
>>CMP typically needs a DataSource. The DataSource needs a JDBC
>>Connection pool. My guess is the connection pool was named demoPool,
>>
>>and it failed. check the logfile for errors.
>>
>>If you need more help, please post your server's log file.
>>
>
>
> I think the problem is the creation of Datasource only.Actually I am trying to
> run the examples given in the default examples server from my user_projects instance
> 'Ram'.
>
> The log file is:
> ==========
> ####<Feb 5, 2004 10:50:40 AM GMT+05:30> <Notice> <Security> <ram> <myserver> <main>
> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
>
> ####<Feb 5, 2004 10:50:40 AM GMT+05:30> <Notice> <WebLogicServer> <ram> <myserver>
> <main> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "myserver"
> for domain "ram">
> ####<Feb 5, 2004 10:50:53 AM GMT+05:30> <Warning> <JDBC> <ram> <myserver> <main>
> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for
> pool "Ram_A": Unable to connect to any hosts due to exception: java.net.ConnectException:
> Connection refused: connect>
Your JDBC Connection Pool is failing right here. It looks like it can't
connect to the database.
> ####<Feb 5, 2004 10:50:54 AM GMT+05:30> <Error> <JDBC> <ram> <myserver> <main>
> <<WLS Kernel>> <> <BEA-001150> <Connection Pool "Ram_A" deployment failed with
> the following error: 0:Could not create pool connection. The DBMS driver exception
> was: Unable to connect to any hosts due to exception: java.net.ConnectException:
> Connection refused: connect.>
> ####<Feb 5, 2004 10:50:54 AM GMT+05:30> <Error> <JDBC> <ram> <myserver> <main>
> <<WLS Kernel>> <> <BEA-001151> <Data Source "Ram_B" deployment failed with the
> following error: DataSource(Ram_JNDI) can't be created with non-existent Pool
> (connection or multi) (Ram_A).>
And this is telling you the DataSource failed because it's pool failed
previously.
-- Rob
Ram
Yes.Rob.
Finally I was able to make it run.
I hv one basic question since I am new to EJB.
What is the requirement of deploying .EAR,.WAR,.JAR files and what circumstances
they need to be deployed ?
Regards,
Ram
Slava Imeshev
"Ram" <ramp...@yahoo.com> wrote in message news:402719fc$1...@newsgroups.bea.com...
> I hv one basic question since I am new to EJB.
You need to get a better understanding than. There is a couple of good
books on EJB that I always recommend:
1. Ed Roman "Mastering Enterprise Java Beans"
http://www.amazon.com/exec/obidos/tg/detail/-/0471417114
2. O'Reilly "Enterprise Java Beans"
http://www.amazon.com/exec/obidos/tg/detail/-/0596002262
> What is the requirement of deploying .EAR,.WAR,.JAR files and what circumstances
> they need to be deployed ?
These are questions that require certain background to understand answers.
I suggest you to read the books above - it's likely these and many other questions
will be cleared.
Regards,
Slava Imeshev
Ram
hi,
sorry for raising this question.
By mistake i hv posted this question.
Basically I wanted to know how to call session bean and entity bean from message
driven bean.
Actually I am doing a pilot project,in that from onMessage() ,I have to call one
session bean followed by one CMP.
Any suggestions?.
Ram
Slava Imeshev
> sorry for raising this question.
>
> By mistake i hv posted this question.
>
> Basically I wanted to know how to call session bean and entity bean from message
> driven bean.
>
> Actually I am doing a pilot project,in that from onMessage() ,I have to call one
> session bean followed by one CMP.
>
> Any suggestions?.
Yes, there are. Read these books:
1. Ed Roman "Mastering Enterprise Java Beans"
http://www.amazon.com/exec/obidos/tg/detail/-/0471417114
2. O'Reilly "Enterprise Java Beans"
http://www.amazon.com/exec/obidos/tg/detail/-/0596002262
Regards,
Slava Imeshev
Akilah McIntyre
2)Make sure you add your JDBC drivers to the beginning of CLASSPATH in either setDomainenv.cmd or setEnv.cmd
3)What really helped was BEA support and playing with BEA's JDBC example that shows how to create and deploy and use a data source.