2 Replies Latest reply on Oct 22, 2008 2:12 PM by Nes Yarug

    Replacing Hypersonic with MSSQL 2005

    Nes Yarug Newbie

      Hello all,

      First post, so please be gentle :)

      This is JBoss 4.0.5GA. I need to use this version as an enterprise application we are using is only qualified on this version of JBoss.

      I'm trying to replace Hypersonic with MSSQL. I have got it working for a server instance that is a copy of "default". However, when I try exactly the same process on an instance that is a copy of "all" I run into an error message:

      2008-10-22 16:52:24,146 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

      --- Incompletely deployed packages ---
      org.jboss.deployment.DeploymentInfo@7d090637 { url=file:/opt/jboss-4.0.5.GA/server/ps1/deploy/jms/hsqldb-jdbc-state-service.xml }
      deployer: org.jboss.deployment.SARDeployer@9cb0f4
      status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.mq:service=StateManager
      state: FAILED
      watch: file:/opt/jboss-4.0.5.GA/server/ps1/deploy/jms/hsqldb-jdbc-state-service.xml
      altDD: null
      lastDeployed: 1224690696016
      lastModified: 1224690696000
      mbeans:

      org.jboss.deployment.DeploymentInfo@af9cbd21 { url=file:/opt/jboss-4.0.5.GA/server/ps1/deploy/jms/mssql-jdbc2-service.xml }
      deployer: org.jboss.deployment.SARDeployer@9cb0f4
      status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.mq:service=DestinationManager
      state: FAILED
      watch: file:/opt/jboss-4.0.5.GA/server/ps1/deploy/jms/mssql-jdbc2-service.xml
      altDD: null
      lastDeployed: 1224690696025
      lastModified: 1224690696000
      mbeans:

      org.jboss.deployment.DeploymentInfo@2e1a665a { url=file:/opt/jboss-4.0.5.GA/server/ps1/deploy/atg-sqlserver-dw-ds.xml }
      deployer: org.jboss.deployment.XSLSubDeployer@1da366c
      status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=ATGDWDS
      state: FAILED
      watch: file:/opt/jboss-4.0.5.GA/server/ps1/deploy/atg-sqlserver-dw-ds.xml
      altDD: null
      lastDeployed: 1224690697448
      lastModified: 1224690697000
      mbeans:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.mq:service=PersistenceManager
      State: FAILED
      Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (com.microsoft.
      sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.)
      I Depend On:
      jboss.jca:service=DataSourceBinding,name=DefaultDS
      Depends On Me:
      jboss.mq:service=DestinationManager

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.mq:service=PersistenceManager
      State: FAILED
      Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (com.microsoft.
      sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.)
      I Depend On:
      jboss.jca:service=DataSourceBinding,name=DefaultDS
      Depends On Me:
      jboss.mq:service=DestinationManager

      The steps I took were:

      1) Installed the correct JDBC driver
      2) Deploy a new datasource descriptor (<jndi-name>DefaultDS</jndi-name>)
      3) Removed deploy/hsqldb-ds.xml
      4) Removed hsqldb.jar and hsqldb-plugin.jar from the server's lib directory
      5) Copied /docs/examples/jms/mssql-jdbc2-service.xml to each server instance's deploy/jms directory. Then changed the DataSourceBinding name to DefaultDS:
      ...
      <depends optional-attribute-
      name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS
      ...

      Anyone know why the process above works for "default", but not "all"? Also, is there a solution for this error?

      Why is the contents of the "default/deploy/jms" different then "all/deploy/jms"?

      ls -al /opt/jboss-4.0.5.GA/server/default/deploy/jms/
      total 113
      drwxr-xr-x 3 jboss jboss 400 2006-10-23 18:00 .
      drwxr-xr-x 11 jboss jboss 1136 2006-10-23 18:00 ..
      -rw-r--r-- 1 jboss jboss 5449 2006-10-23 18:00 hsqldb-jdbc2-service.xml
      -rw-r--r-- 1 jboss jboss 3680 2006-10-23 18:00 hsqldb-jdbc-state-service.xml
      -rw-r--r-- 1 jboss jboss 4113 2006-10-23 18:00 jbossmq-destinations-service.xml
      drwxr-xr-x 4 jboss jboss 112 2006-10-23 18:00 jbossmq-httpil.sar
      -rw-r--r-- 1 jboss jboss 3901 2006-10-23 18:00 jbossmq-service.xml
      -rw-r--r-- 1 jboss jboss 2416 2006-10-23 18:00 jms-ds.xml
      -rw-r--r-- 1 jboss jboss 76000 2006-10-23 18:00 jms-ra.rar
      -rw-r--r-- 1 jboss jboss 600 2006-10-23 18:00 jvm-il-service.xml
      -rw-r--r-- 1 jboss jboss 4096 2006-10-23 18:00 uil2-service.xml

      ls -al /opt/jboss-4.0.5.GA/server/all/deploy/jms/
      total 81
      drwxr-xr-x 2 jboss jboss 120 2006-10-23 17:59 .
      drwxr-xr-x 15 jboss jboss 1400 2006-10-23 18:00 ..
      -rw-r--r-- 1 jboss jboss 2684 2006-10-23 17:59 hajndi-jms-ds.xml
      -rw-r--r-- 1 jboss jboss 76000 2006-10-23 17:59 jms-ra.rar

      For what it is worth, I went through these steps with an Oracle database before and don't recall seeing these errors.

      Thanks in advance for any replies!

      Nes