1 Reply Latest reply on Jul 23, 2002 7:58 AM by Mathias Rust

    Oracle 9i: OracleDS does not implement any Service methods

    Mathias Rust Newbie

      I am working with the boundle jboss3.0.0 + tomcat 4.0.3.
      I copied the oracle data source definition (OracleDS) from docs/examples to the deploy directory and then I modified it accordingly. I copied the classes12.jar file from oracle to the lib/ext directory.
      When I start jboss I'll get the following warning: "OracleDS does not implement any Service methods" (see attachment. I read in other forums that this was an error in jboss 3.0.0 rc1. Is this error solved in jboss 3.0.0. ?

        • 1. Re: Oracle 9i: OracleDS does not implement any Service metho
          Mathias Rust Newbie

          1) Ignore the warning: OracleDS does not implement any Service methods

          2) Copy the following oracle-service.xml to server/default/deploy. I can use CMP with Jboss 3.0.0 + Tomcat4.0.3.


          ----------------------------------------------------------
          <?xml version="1.0" encoding="UTF-8"?>

          <!-- ===================================================================== -->
          <!-- -->
          <!-- JBoss Server Configuration -->
          <!-- -->
          <!-- ===================================================================== -->



          <!-- ==================================================================== -->
          <!-- ConnectionManager setup for Oracle dbs -->
          <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
          <!-- Thanks to Steven Coy -->
          <!-- ==================================================================== -->




          <!-- Include a login module configuration named OracleDbRealm.
          Update your login-conf.xml, here is an example for a
          ConfiguredIdentityLoginModule:

          <application-policy name = "OracleDbRealm">

          <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
          <module-option name = "principal">yourprincipal</module-option>
          <module-option name = "userName">yourusername</module-option>
          <module-option name = "password">yourpassword</module-option>
          <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=OracleDS</module-option>
          </login-module>

          </application-policy>

          NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
          module-option name = "managedConnectionFactoryName"
          must match the object name of the ConnectionManager you are configuring here.
          -->

          <!--uncomment out this line if you are using the OracleDbRealm above
          OracleDbRealm
          -->

          <depends optional-attribute-name="ManagedConnectionFactoryName">
          <!--embedded mbean-->


          OracleDS



          <config-property name="ConnectionURL"
          type="java.lang.String">jdbc:oracle:thin:@creon4:1521:cmr2</config-property>
          <config-property name="DriverClass" type="java.lang.String">oracle.jdbc.driver.OracleDriver</config-property>
          <!--set these only if you want only default logins, not through JAAS -->
          <config-property name="UserName" type="java.lang.String">myUser</config-property>
          <config-property name="Password" type="java.lang.String">myPassword</config-property>




          <!--Below here are advanced properties -->
          <!--hack-->
          <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



          <depends optional-attribute-name="ManagedConnectionPool">
          <!--embedded mbean-->


          0
          50
          5000
          15
          <!--criteria indicates if Subject (from security domain) or app supplied
          parameters (such as from getConnection(user, pw)) are used to distinguish
          connections in the pool. Choices are
          ByContainerAndApplication (use both),
          ByContainer (use Subject),
          ByApplication (use app supplied params only),
          ByNothing (all connections are equivalent, usually if adapter supports
          reauthentication)-->
          ByContainer



          <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

          <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager

          java:/TransactionManager

          <!--make the rar deploy! hack till better deployment-->
          jboss.jca:service=RARDeployer