4 Replies Latest reply on Apr 13, 2004 3:25 PM by sesques

    Configuring jboss 3.2.3 for MS SQL2000. ** Help required **

    dvk78

      Hi,
      Am new to the j2ee world. Been trying to configure Jboss 3.2.3 to work with MS SQL2000 with no success. I followed the steps given in the book 'Getting Started with JBoss', but I get an error when I start up jboss after the changes. Im working on a Win2000 server machine with jdk 1.4.1_01. With the default Hypersonic DB no errors are reported when jboss is started.
      Any help would be greatly appreciated !
      Thanx.


      2004-04-13 17:07:37,801 ERROR [org.jboss.deployment.scanner.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: CONFIGURED
      I Depend On: jboss.mq:service=Invoker
      jboss.web:service=WebServer

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

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

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

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

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

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

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

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

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

      Depends On Me: , ObjectName: jboss.mq:service=Invoker
      state: CONFIGURED
      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: CONFIGURED
      I Depend On: jboss.mq:service=SecurityManager

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

      Depends On Me: 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:service=TracingInterceptor
      jboss.mq.destination:service=Queue,name=DLQ
      , ObjectName: jboss.mq.destination:service=Queue,name=DLQ
      state: CONFIGURED
      I Depend On: jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

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

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

      Depends On Me: 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
      jboss.mq:service=SecurityManager
      jboss.mq.destination:service=Queue,name=DLQ
      , ObjectName: jboss.mq:service=PersistenceManager
      state: CONFIGURED
      I Depend On: jboss.jca:service=LocalTxCM,name=MSSQLDS

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

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

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

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

      Depends On Me: ]
      2004-04-13 17:07:38,472 INFO [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL
      2004-04-13 17:07:38,552 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss-3.2.3/server/default/conf/jboss-service.xml
      2004-04-13 17:07:38,562 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445)] Started in 27s:320ms

        • 1. Re: Configuring jboss 3.2.3 for MS SQL2000. ** Help required
          sesques

          Hi,

          The less we can tell is that the message is not clear.
          How do you configure MSSQL 2000 ? Do you replace Hypersonic by MSSQL (bad solution) or add a mssql-ds.xml file descriptor (good solution) ?

          The log seems indicate that the default database is missing.

          Sorry, but no more idea at that time.

          • 2. Re: Configuring jboss 3.2.3 for MS SQL2000. ** Help required
            dvk78

            I deleted the hsqldb-ds.xml and replaced it with mssql-ds.xml in the deploy directory. Will deleting the former give error?
            I have also placed the 3 required jars to connect to the remote SQL2000 database in the default\lib directory(Am using the default jboss config).
            I had also replaced the hsqldb-jdbc2-service.xml in deploy\jms with the one for mssql.
            When I revert back to the default jboss setup configuration for hsqldb everthing is fine.
            Cant seem to figure out whats going wrong :-(
            Hope someone can sort it out to help me !

            -Vinod

            • 3. Re: Configuring jboss 3.2.3 for MS SQL2000. ** Help required
              dvk78

              I tried adding just the mssql-ds.xml to the deploy directory and this time i dont get any errors when jboss starts up! :-)
              I changed the standardjbosscmp-jdbc.xml to make the SQL2000 server as the default and again I dont get any errors when jboss starts up.
              I think the problem was with deleting the hssql-ds.xml and its related service .xml file

              -Vinod

              • 4. Re: Configuring jboss 3.2.3 for MS SQL2000. ** Help required
                sesques

                That's it !

                You cannot delete the hypersonic database because it is used by the persistence manager and other stuff... The mysteries of JBoss ;-)