Win a copy of Spring Boot in Practice this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Unable to deploy cmp bean

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear All ,
I am unable to deploy the CMP Bean , getting the following error on staring the server.
Am using weblogic 6.1 app server .
The ejbname in deployment descriptor is correct .
Kindly let me know at the earliest .

====================================
<Mar 5, 2003 3:01:23 AM IST> <Error> <J2EE> <Error deploying application acct:
Unable to deploy EJB: containerManaged from acct.jar:
The DataSource with the JNDI name: MyPool could not be located. Please ensure th
at the DataSource has been deployed successfully and that the JNDI name in your
EJB Deployment descriptor is correct.
>
<Mar 5, 2003 3:01:23 AM IST> <Error> <Management> <InvocationTargetException set
ting attribute Deployed on MBean mydomain:Location=myserver,Name=acct,Type=Appli
cationConfig to value true. Method: public void weblogic.management.mbeans.custo
m.Application.setDeployed(boolean) throws weblogic.management.DeploymentExceptio
n,weblogic.management.UndeploymentException

Unable to deploy EJB: containerManaged from acct.jar:
The DataSource with the JNDI name: MyPool could not be located. Please ensure th
at the DataSource has been deployed successfully and that the JNDI name in your
EJB Deployment descriptor is correct.
 
reply
    Bookmark Topic Watch Topic
  • New Topic