3 Replies Latest reply on Feb 17, 2004 7:45 AM by alaveth

    EJB's keep using DefaultDS

    [tone]

      I've configured an Oracle datasource on JBoss which works fine for the web modules of me ear file, but the EJB's insist on using DefaultDS.

      Here is my jboss.xml:

      <?xml version="1.0" encoding="UTF-8"?>
      <jboss>
       <enterprise-beans>
       <entity>
       <ejb-name>PatchEJB</ejb-name>
       <resource-ref>
       <res-ref-name>jdbc/ibbd</res-ref-name>
       <jndi-name>java:/OracleDS</jndi-name>
       <resource-name>DBResource</resource-name>
       </resource-ref>
       </entity>
       <session>
       <ejb-name>PatchSessionEJB</ejb-name>
       <resource-ref>
       <res-ref-name>jdbc/ibbd</res-ref-name>
       <jndi-name>java:/OracleDS</jndi-name>
       <resource-name>DBResource</resource-name>
       </resource-ref>
       </session>
       </enterprise-beans>
       <resource-managers>
       <resource-manager>
       <res-name>DBResource</res-name>
       <res-jndi-name>java:/OracleDS</res-jndi-name>
       </resource-manager>
       </resource-managers>
      </jboss>

      and my oracle-ds.xml:
      <?xml version="1.0" encoding="UTF-8"?>
      <datasources>
       <local-tx-datasource>
       <jndi-name>OracleDS</jndi-name>
       <connection-url>jdbc:oracle:thin:@{server}:1521:{sid}</connection-url>
       <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
       <user-name>{user}</user-name>
       <password>{password}</password>
       <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
       <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
       <!-- Checks the Oracle error codes and messages for fatal errors -->
       <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
       <security-domain>OracleDbRealm</security-domain>
       </local-tx-datasource>
      
      </datasources>


      Like I said, my war files are accessing the database without a problem. If I remove the hsqldb-ds.xml file I get the followin on startup:
      [EjbModule] Deploying PatchEJB
      [EjbModule] Deploying PatchSessionEJB
      [EntityContainer] No resource manager found for jdbc/ibbd
      [EntityInstancePool] Started jboss.j2ee:jndiName=PatchEJB,plugin=pool,service=EJB
      [EntityContainer] Started jboss.j2ee:jndiName=PatchEJB,service=EJB
      [StatelessSessionContainer] No resource manager found for jdbc/ibbd

      This is driving me insane, what have I overlooked? I'm using jboss 3.2.3 and an Oracle 8 database.

      [tone]


        • 1. Re: EJB's keep using DefaultDS

          Try using the resource-env-refs instead, they seem to work for me, the resource-refs always given me problems.

          • 2. Re: EJB's keep using DefaultDS
            jashwin

            From my point of view, the problem might be related to your ds-configuration because since ur using oracle-ds; deleting hsql-ds should not affect your modules.

            • 3. Re: EJB's keep using DefaultDS
              alaveth

               

              "JAshwin" wrote:
              From my point of view, the problem might be related to your ds-configuration because since ur using oracle-ds; deleting hsql-ds should not affect your modules.


              Could you please explain in greater detail?
              For I have the same problem, and being new to JBoss I do feel a bit overwhelmed. Any help would be greatly appreciated.
              I'm using JBoss 3.2.3 and Oracle 8i.