1 Reply Latest reply on Dec 5, 2001 2:12 PM by Paul Boucher

    HELP!!

    Paul Boucher Newbie

      JBoss 2.4.1 on windows 2000 server, jdk 1.3.1_01
      MS Sqlserver 2000 on the same machine with the Microsoft JDBC drivers for MSSQLSRV2000.
      I always get the same error, try after try:


      [DefaultDS] Pool DefaultDS [1/1/10] gave out pooled object: org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@6c585a
      [DefaultDS] Pool DefaultDS [0/1/10] returned object org.jboss.pool.jdbc.xa.wrapper.XAConnectionImpl@6c585a to the pool.
      [Hello] TRANSACTION ROLLBACK EXCEPTION:Load failed; nested exception is:
      java.sql.SQLException: Unable to create PreparedStatement!; nested exception is:
      java.rmi.ServerException: Load failed; nested exception is:
      java.sql.SQLException: Unable to create PreparedStatement!
      [Hello] java.rmi.ServerException: Load failed; nested exception is:
      [Hello] java.sql.SQLException: Unable to create PreparedStatement!
      [Hello] java.sql.SQLException: Unable to create PreparedStatement!

      3 rows in the table and 3 Collection returned (seem to be able to read the columns but not able to retrieve data from it)

      I can have an instance but I can't access the data.
      Here's a snippet of my code:
      Iterator i = home.findAll().iterator();
      Hello h = (Hello) i.next();
      //ok no problem there
      System.out.println("nom=="+(String)h.getNom());
      //bang!! PreparedStatement error!


      Now is there someone on earth that already did that before???
      I'd like to know what should be configured and added on the config files of Jboss (like jboss.jcml, standardjaws.xml, jaws.xml, etc) in order to get things working! I'm new to JBoss and it's been 4 days that I'm stuck there with a basic CMP HelloWorld bean!


      Thanks!

      <>

        • 1. Re: HELP!!
          Paul Boucher Newbie



          I found a solution that work for me:
          switch to mySQL and things started to work all by themself; like pure magic.

          I guess and I conclude that the MS SqlDriver JDBC typ4 from Microsoft wasn't working correctly.

          I will explore later the true explanation for the reason why the MS driver wasn't working correctly (cause maybe it's really nothing).

          <>