|Date Added:||10 April 2014|
|File Size:||6.15 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The configuration of a datasource may require two distinct steps: The remaining levels are taken from the package jds inside the driver’s JAR all the way to the sub-package where the JDBC driver class is defined.
See Question with no answers, but issue solved in the comments or extended in chat.
I corrected the connection string: Thank you for your advice. I finally got back to working on this.
I did try both of these options and continued to receive the same error message. That will help isolate the issue. Thank you all, Luca. Dolfiz 2 3 You have to deploy it as module and you have to specify driver-class in standalone.
Setup MSSQL datasource on Jboss AS 7 using jTDS
Throwable while attempting to get a new connection: This content has been marked as final. The driver name sybasejtds is jboes arbitrary and is basically what’s going to appear in the JBoss AEP administration GUI typically at port when one tries to create a new datasource.
Furthermore, in my particular case, the database I was trying to connect to was a Sybase ASE 15 or 16, am not sure at the moment so the exotic factor is high. Please enter a title. Correct Answers – 4 points.
Your connection settings appear okay from a quick glance. The JBoss server is a piece of excrement as attested by the fact that if you decided to comment out a section in the standalone. I was trying to configure a datasource in the application server to connect to database, using JTDS drivers. I tried changing the JDBC driver as you recommended, but discovered that it still does not work. More properly you are using another driver which work out of the box with your setting since it is jdbc 4 compliant.
Setup MSSQL datasource on Jboss AS 7 using jTDS | hs2n Blog
The element for the h2 driver was already there, I just added the one about the sybasejtds driver. You can not post a blank message. I don’t really understand why using SQL Server Mgmt Studio I do not need to specify db instance name, but only db server name, and in the datasource, on the contrary, the uboss instance name is the only one needed.
I don’t know if that made any difference or not.