3 Replies Latest reply on Mar 6, 2003 9:17 AM by David Jencks

    Don’t understand the following LocalTxConnectionManager warn

    Anthony Cavanagh Newbie

      I am currently setting up a MS SQL Server datasource.

      I have carried out the following steps.

      1 Modified the mssql-ds.xml:


      <local-tx-datasource>
      <jndi-name>jdbc/webconnect</jndi-name>
      <connection-url>jdbc:microsoft:sqlserver://stl00895:1433;DatabaseName=webconnect</connection-url>
      <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
      <user-name></user-name>

      </local-tx-datasource>


      I added this file along with my JDBC driver jar mssqlserver.jar into the server directory I am using :
      C:\jboss-3.2.0RC2_tomcat.4.1.18\server\default\deploy.

      I then get the following warning message :

      10:25:00,453 WARN [LocalTxConnectionManager]
      Please change your datasource setup to use TransactionManagerService with object name jboss.tm:service=Transaction ManagerService instead of TransactionManager with value java:/TransactionManager

      ------------------------
      10:25:00,453 WARN [LocalTxConnectionManager] ----------------------------------

      I admit I do not know what this message means.

      The jms-service.xml file contains the following line
      java:/TransactionManager, but this is to do with JMS not datasource.

      Do I need to add a similar line to my datasource file mssql-ds.xml:

      Thanks for any help Tony

        • 1. Re: Don?t understand the following LocalTxConnectionManager
          Anthony Cavanagh Newbie

          As well as adding mssql-ds.xml should I also use the mssql-service.xml file.

          So far as I have already written I have just deployed the modified mssql-ds.xml file and the mssqlserver.jar.

          I have no idea what else I should do to get the datasource set up.

          Cheers For any help Tony

          • 2. Re: Don?t understand the following LocalTxConnectionManager
            Anthony Cavanagh Newbie

            I have a feeling that the warning may just be a red herring.

            When I try to run the application I get the following error :

            java.rmi.RemoteException: Unable to get shortcut DAO: Unable to get data source: Unable to get datasource for <jdbc/webconnect>: javax.naming.NameNotFoundException: jdbc not bound.

            So I do have a datasource problem.

            This is my datasource file mssql-ds.xml


            <local-tx-datasource>
            <jndi-name>jdbc/webconnect</jndi-name>
            <connection-url>jdbc:microsoft:sqlserver://stl00895:1433;DatabaseName=webconnect</connection-url>
            <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
            <user-name></user-name>

            </local-tx-datasource>



            Do I need to add anything to my jboss.xml

            <?xml version="1.0" encoding="UTF-8" ?>
            -
            - <enterprise-beans>
            -
            <ejb-name>ShortcutManager</ejb-name>
            <jndi-name>ejb/com/smartstream/webconnect/business/ejb/ShortcutManagerHome</jndi-name>

            -
            <ejb-name>DashboardManager</ejb-name>
            <jndi-name>ejb/com/smartstream/webconnect/business/ejb/DashboardManagerHome</jndi-name>

            -
            <ejb-name>Control</ejb-name>
            <jndi-name>ejb/com/smartstream/webconnect/business/ejb/ControlLocalHome</jndi-name>

            -
            <ejb-name>Schema</ejb-name>
            <jndi-name>ejb/com/smartstream/webconnect/business/ejb/SchemaLocalHome</jndi-name>

            -
            <ejb-name>Item</ejb-name>
            <jndi-name>ejb/com/smartstream/webconnect/business/ejb/ItemLocalHome</jndi-name>

            </enterprise-beans>


            Thanks for any help Tony

            • 3. Re: Don?t understand the following LocalTxConnectionManager
              David Jencks Master

              The warning is a red herring and can be ignored. You should only use the *-ds.xml files, not the *-service.xml files (at least if you want to remain sane:-)

              Check in jndiview in the jmx console to see exactly what the datasource is getting bound under. Perhaps you are looking up jdbc/webconnect rather than java:/jdbc/webconnect? Datasources are only available in the jvm in which they are deployed.