1 Reply Latest reply on Sep 20, 2002 2:15 AM by db

    javax.naming.NameNotFoundException: DefaultDS not bound

    db
    db Mar 6, 2002 9:09 PM

      I have an error when loading my EJBs, everything works fine, but it would be nice to understand where the error is coming from. I get a NameNotFoundException: Default not bound - have looked at my jboss.jcml where I set up the jdbc info, and can't seem to figure it out. See error below.

      Any insight would be appreciated!

      Thanks,

      Dan


      <03/06/02*17:58:20> DEBUG [Container factory] Container Invoker Server SocketAddr='Default'
      <03/06/02*17:58:20> DEBUG [Container factory] Container Invoker Optimize='true'
      <03/06/02*17:58:20> DEBUG [Container factory] Begin java:comp/env for EJB: AccountEJB
      <03/06/02*17:58:20> DEBUG [Container factory] TCL: java.net.URLClassLoader@77fa9a
      <03/06/02*17:58:20> DEBUG [Container factory] javax.naming.NameNotFoundException: DefaultDS not bound
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.server.NamingServer.getBinding(NamingServer.java:473)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.server.NamingServer.getBinding(NamingServer.java:481)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.server.NamingServer.getObject(NamingServer.java:487)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:349)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:333)
      <03/06/02*17:58:20> DEBUG [Container factory] at javax.naming.InitialContext.lookup(Unknown Source)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.Container.setupEnvironment(Container.java:539)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.Container.init(Container.java:332)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.EntityContainer.init(EntityContainer.java:202)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.Application.init(Application.java:202)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:368)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:304)
      <03/06/02*17:58:20> DEBUG [Container factory] at java.lang.reflect.Method.invoke(Native Method)
      <03/06/02*17:58:20> DEBUG [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      <03/06/02*17:58:20> DEBUG [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.java:486)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:464)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:208)
      <03/06/02*17:58:20> DEBUG [Container factory] at java.lang.reflect.Method.invoke(Native Method)
      <03/06/02*17:58:20> DEBUG [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      <03/06/02*17:58:20> DEBUG [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379)
      <03/06/02*17:58:20> DEBUG [Container factory] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217)
      <03/06/02*17:58:20> DEBUG [Container factory] at java.lang.Thread.run(Unknown Source)
      <03/06/02*17:58:20> WARN [Container factory] No resource manager found for DDiveMySQLPool

      • 2227 Views
      • Tags:
        • 1. Re: javax.naming.NameNotFoundException: DefaultDS not bound
          db
          db Sep 20, 2002 2:15 AM (in response to db)

          In case this helps anyone else who might stumble on to this. I finally came back to take a look at this and the fix was to add a resource-manager object into the jboss.xml file for the EJB.

          <resource-managers>
          <resource-manager res-class="">
          <res-name>DDiveMySQLPool</res-name>
          <res-jndi-name>java:/DDiveMySQLPool</res-jndi-name>
          </resource-manager>
          </resource-managers>

            • Actions