5 Replies Latest reply on Jan 20, 2005 9:04 PM by niccolas

    problem in configuring jboss3.2.3 with ms sqlserver2000

    atumma

      Hai guys,

      how can i configure MS SQL server 2000 in Jboss3.2.3. I tried with following changes....,but it is not working. Does anyone have idea

      1) i have copied mssql-ds.xml to defult/deploy/ directory and changed the URL,Class, Username,Password.

      2)and i have also changed standardjws.xml && standardjbosscmp-jdbc.xml with appropriate Jndi name ,type-mapping

      3)copied mssql-jdbc2.xml to defult/deploy/jms/ directory

      4) and copies mssqlserver.jar ,msutil.jar and mbase.jar to lib directory


      and then started the server i got the following errors........can anyone helpme.

      12:50:49,751 INFO [TxConnectionManager] Started jboss.jca:service=LocalTxCM,name=MSSQLDS

      12:51:09,493 ERROR [PersistenceManager] Starting failed
      org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]SELECT permission denied on object 'JMS_MESSAGES', database 'EDGE', owner 'atumma'.)


      here 'atumma' is the username that iahev provided in mssql-ds.xml and EDGE is the database that i have created in mssqlserver



      at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:336)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1356)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy14.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)


      and finally ...............



      12:52:18,343 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
      state: CREATED
      I Depend On: jboss.mq:service=Invoker
      jboss.web:service=WebServer

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=JVM
      state: CREATED
      I Depend On: jboss.mq:service=Invoker

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=OIL
      state: CREATED
      I Depend On: jboss.mq:service=Invoker

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=OIL2
      state: CREATED
      I Depend On: jboss.mq:service=Invoker

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=RMI
      state: CREATED
      I Depend On: jboss.mq:service=Invoker

      Depends On Me: , ObjectName: jboss.mq:service=Invoker
      state: CREATED
      I Depend On: jboss.mq:service=TracingInterceptor

      Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP
      jboss.mq:service=InvocationLayer,type=JVM
      jboss.mq:service=InvocationLayer,type=OIL
      jboss.mq:service=InvocationLayer,type=OIL2
      jboss.mq:service=InvocationLayer,type=RMI
      jboss.mq:service=InvocationLayer,type=UIL2
      , ObjectName: jboss.mq:service=TracingInterceptor
      state: CREATED
      I Depend On: jboss.mq:service=SecurityManager

      Depends On Me: jboss.mq:service=Invoker
      , ObjectName: jboss.mq:service=SecurityManager
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: jboss.mq:service=TracingInterceptor
      jboss.mq.destination:service=Queue,name=DLQ
      jboss.mq.destination:service=Topic,name=testTopic
      jboss.mq.destination:service=Topic,name=securedTopic
      jboss.mq.destination:service=Topic,name=testDurableTopic
      jboss.mq.destination:service=Queue,name=testQueue
      , ObjectName: jboss.mq.destination:service=Queue,name=DLQ
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Topic,name=testTopic
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=testQueue
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=A
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=B
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=C
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=D
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=ex
      state: CREATED
      I Depend On: jboss.mq:service=DestinationManager

      Depends On Me: , ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
      state: CREATED
      I Depend On: jboss.mq:service=Invoker

      Depends On Me: , ObjectName: jboss.mq:service=DestinationManager
      state: CREATED
      I Depend On: jboss.mq:service=MessageCache
      jboss.mq:service=PersistenceManager
      jboss.mq:service=StateManager

      Depends On Me: jboss.mq:service=SecurityManager
      jboss.mq.destination:service=Queue,name=DLQ
      jboss.mq.destination:service=Topic,name=testTopic
      jboss.mq.destination:service=Topic,name=securedTopic
      jboss.mq.destination:service=Topic,name=testDurableTopic
      jboss.mq.destination:service=Queue,name=testQueue
      jboss.mq.destination:service=Queue,name=A
      jboss.mq.destination:service=Queue,name=B
      jboss.mq.destination:service=Queue,name=C
      jboss.mq.destination:service=Queue,name=D
      jboss.mq.destination:service=Queue,name=ex
      , ObjectName: jboss.mq:service=PersistenceManager
      state: FAILED
      I Depend On: jboss.jca:service=LocalTxCM,name=MSSQLDS

      Depends On Me: jboss.mq:service=DestinationManager
      org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]SELECT permission denied on object 'JMS_MESSAGES', database 'EDGE', owner 'atumma'.)]
      12:52:18,366 INFO [URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL
      12:52:18,441 INFO [MainDeployer] Deployed package: file:/usr/apps/jboss-3.2.3/server/default/conf/jboss-service.xml
      12:52:18,444 INFO [Server] JBoss (MX MicroKernel) [3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)] Started in 2m:23s:759ms
      12:52:19,680 ERROR [DLQHandler] Initialization failed
      javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
      at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:674)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1173)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:686)
      12:52:19,682 INFO [JMSContainerInvoker] Reconnected to JMS provider
      12:52:19,682 WARN [JMSContainerInvoker] JMS provider failure detected:
      javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
      at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:169)
      at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:458)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:674)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1173)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:686)
      12:52:19,683 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider



      kindly help me my advance thanks to u all ,

      thanks and regards

        • 1. Re: problem in configuring jboss3.2.3 with ms sqlserver2000
          niccolas

          as you said,
          3)copied mssql-jdbc2.xml to defult/deploy/jms/ directory
          have you removed another file hsqldb-jdbc2-service.xml(in jboss4.0.1), just try it

          • 2. Re: problem in configuring jboss3.2.3 with ms sqlserver2000
            atumma

            Hi Nicholas ,

            Yeah I have removed hsql-jdbc2-service.xm file and tried but it did not worked
            any more suggestions pls

            • 3. Re: problem in configuring jboss3.2.3 with ms sqlserver2000
              darranl

              Have you tried connecting to the database as the user defined from the JBoss machine to double check that the user is configured as required.

              Also looking at your error message it appears that the JMS tables exist, did you create these or did JBoss create these?

              • 4. Re: problem in configuring jboss3.2.3 with ms sqlserver2000
                vjy

                Does ur mssql-ds.xml looks like this



                <local-tx-datasource>
                <jndi-name>name</jndi-name>
                <connection-url>jdbc:microsoft:sqlserver://xxxx:1433;DatabaseName=xxxx;SelectMethod=cursor</connection-url>
                <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
                <user-name>cc</user-name>
                <password>ccc</password>
                <min-pool-size>5</min-pool-size>
                <max-pool-size>10</max-pool-size>
                <blocking-timeout-millis>5000</blocking-timeout-millis>
                <idle-timeout-minutes>15</idle-timeout-minutes>
                <transaction-isolation>TRANSACTION_SERIALIZABLE</transaction-isolation>
                </local-tx-datasource>


                Did you add the driver class here.
                SInce this works good for me.

                Hope this helps

                • 5. Re: problem in configuring jboss3.2.3 with ms sqlserver2000
                  niccolas

                  (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]SELECT permission denied on object 'JMS_MESSAGES', database 'EDGE', owner 'atumma'.)]
                  it seems that your database user have not plivileges enough.
                  in sql prompt, try the sql statement as followed:
                  grant all plivileges on edge to atumma identified by 'password';
                  and then try again.