0 Replies Latest reply on Mar 10, 2003 3:37 AM by WS Chia

    From JBoss 2.4.4 to JBoss 2.4.10

    WS Chia Newbie

      We have been using JBoss 2.4.4 for awhile and we are in the process of moving to 2.4.10. However, we are facing a problem on the Datasource configuration.

      After setting the appropropriate configuration on the 2.4.10, we were getting the "No Suitable Driver" for all the datasource defined in the JBoss.JCML. Our setting are as follows:
      a. Platform : window 2000
      b. Processor : Pentium IV 1.8G
      c. Memory :256 MB
      d. SQL Database : SQL 2000 with SP3
      e. SQL JDBC Driver : MS JDBC Driver Dated 21 Nov 2002.
      f. JDK/JRE Version : 1.4.0_3

      Any suggestion is appreciated. Thanks in advance.

      Regards,

      WSCHIA

      jboss.jcml configuration

      DefaultDS
      org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl

      jdbc:microsoft:sqlserver://10.10.1.19;Databasename=jmlms;SelectMethod=cursor
      1200000
      test
      test
      50
      true
      false
      false
      true
      120000
      1800000
      false
      false
      1.0
      0
      false
      false



      The error message is as follows:

      [INFO,DefaultDS] XA Connection pool DefaultDS bound to java:/DefaultDS
      [ERROR,XAConnectionFactory] Can't get an XAConnection
      java.sql.SQLException: No suitable driver
      at java.sql.DriverManager.getConnection(Unknown Source)
      at java.sql.DriverManager.getConnection(Unknown Source)
      at org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl.getXAConnection(XADat
      aSourceImpl.java:188)
      at org.jboss.pool.jdbc.xa.XAConnectionFactory.createObject(XAConnectionFactory.java:336)
      at org.jboss.pool.ObjectPool.createNewObject(ObjectPool.java:1023)
      at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:677)
      at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:252)
      at org.jboss.jdbc.XADataSourceLoader.startService(XADataSourceLoader.java:455)
      at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
      at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
      at $Proxy0.start(Unknown Source)
      at org.jboss.util.ServiceControl.start(ServiceControl.java:79)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
      23)
      at org.jboss.Main.(Main.java:209)
      at org.jboss.Main$1.run(Main.java:110)
      at java.security.AccessController.doPrivileged(Native Method)
      at org.jboss.Main.main(Main.java:106)