3 Replies Latest reply on Aug 7, 2002 9:27 AM by kalpesh

    OracleDS not bound, but it was until I set up SSL...

    Jessica Farnham Newbie

      I feel like I'm going a bit crazy here... I'm running JBoss 3.0 with Tomcat & Jboss.net, and connecting to an Oracle 8i datasource. Until yesterday, I had absolutely no problem connecting to the Oracle datasource under the name 'java:/OracleDS'. The only change I made (or remember making...) yesterday was to edit tomcat4-service.xml and jboss-service.xml so that Tomcat runs with SSL. Now, the exact same piece of code fails, with an error message saying that OracleDS is not bound. However, from the JBoss output, it looks like it still is being bound. The output below is the result of redeploying oracle-service.xml, then trying to access the datasource. I've also included the oracle-service.xml file, most of which came straight out of a post in these forums I think. I would greatly appreciate hearing from anyone who has dealt with something similar, or who can point me to the stupid mistake that I am undoubtedly making. Thanks!

      10:09:38,640 INFO [MainDeployer] Undeploying file:/var/jboss/server/all/deploy/oracle-service.xml
      10:09:38,641 INFO [JBossManagedConnectionPool] Stopping
      10:09:38,641 INFO [JBossManagedConnectionPool] Stopped
      10:09:38,642 INFO [LocalTxConnectionManager] Destroying
      10:09:38,776 INFO [LocalTxConnectionManager] Destroyed
      10:09:38,778 INFO [JBossManagedConnectionPool] Destroying
      10:09:38,779 INFO [JBossManagedConnectionPool] Destroyed
      10:09:38,783 INFO [MainDeployer] Cleaned Deployment file:/var/jboss/server/all/deploy/oracle-service.xml
      10:09:38,785 INFO [MainDeployer] Undeployed file:/var/jboss/server/all/deploy/oracle-service.xml
      10:09:38,787 INFO [MainDeployer] Starting deployment of package: file:/var/jboss/server/all/deploy/oracle-service.xml
      10:09:39,064 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=OracleDS does not implement any Service methods
      10:09:39,067 INFO [JBossManagedConnectionPool] Creating
      10:09:39,068 INFO [JBossManagedConnectionPool] Created
      10:09:39,070 INFO [JBossManagedConnectionPool] Starting
      10:09:39,072 INFO [JBossManagedConnectionPool] Started
      10:09:39,073 INFO [MainDeployer] Successfully completed deployment of package: file:/var/jboss/server/all/deploy/oracle-service.xml
      10:09:49,472 INFO [Engine] JBossAxisServlet: init
      10:09:49,957 INFO [JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityDomain@da2737
      10:09:49,960 INFO [JaasSecurityManagerService] setCachePolicy, c=org.jboss.util.TimedCachePolicy@4492fb
      10:09:49,962 INFO [JaasSecurityManagerService] Added other, org.jboss.security.plugins.SecurityDomainContext@dd4c8 to map
      10:09:50,976 INFO [STDOUT] javax.ejb.CreateException: Can't load requested account
      10:09:51,210 INFO [STDOUT] java.sql.SQLException: Connection failure: javax.naming.NameNotFoundException: OracleDS not bound
      10:09:51,212 INFO [STDOUT] Create: javax.ejb.CreateException

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

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


      <config-property name="ConnectionURL" type="java.lang.String">jdbc:oracle:thin:@sunshine:1521:ORCL</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">username</config-property>
      <config-property name="Password" type="java.lang.String">password</config-property>

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

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


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

      <!--make the rar deploy! hack till better deployment-->

        • 1. Re: OracleDS not bound, but it was until I set up SSL...
          David Jencks Master

          Well, there's something wrong somewhere with your oracle-service.xml, since you aren't seeing the log message "...bound to java:/OracleDS"

          If you upgraded to a later version of jboss, such as 3.0.1 or Branch_3_0, the
          <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager

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

          Other than that, I hope you keep your entire project under version control.

          • 2. Re: OracleDS not bound, but it was until I set up SSL...
            Jessica Farnham Newbie

            Thanks for the response. Switching

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


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

            worked for me. Thanks!

            • 3. Re: OracleDS not bound, but it was until I set up SSL...
              kalpesh Newbie

              if you have shifted from jboss-3.0.0RC1 to jboss-3.0.0_tomcat-4.0.3 then the deployment descriptor has changed a little. check these 3 things

              1)classes12.jar is in %jbosshome%\lib
              2)if you are using LocalTxConnectionManager then put the jboss-local-jdbc.rar in server\deploy directory
              3) the DS configuration have changed a little


              is changed to
              <config-property name="" type="" value="">