greetings everyone,
i've encountered the same problem as dagger33 and bhavinpmehta. A lot of google
surfing and i noticed the connection string i was using was wrong: when using
the sqljdbc.jar and sqljdbc4.jar packages you have to use a connection string
starting with
jdbc:sqlserver://host:14
I've been having the same problem.
bhavinpmehta's advice solved the problem - so there must definitely be
something wrong with some of Microsoft's JDBC drivers somewhere as I'm sure all
the connection strings and things were right... *shrug*
This was with version 2.0.1008.2 of the Microsoft SQ
In case anyone can get anything useful, I have an ear file that works well and
very reliably (over 6 months) on my Linux server running JB 4.2.1.
This ear uses MS sql drivers and connects to MS SQL on mt 2003 SBS server.
When I move THE SAME distros of Java, JBoss, MS SQL drivers ear etc to the
Sorry My Bad.
I was not giving correct jdbc url. IO missed : after mysql in url
BAD jdbc:mysql//127.0.0.1:3306/Testworld
Correct jdbc:mysql://127.0.0.1:3306/Testworld
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117227#4117227
Reply to the post :
http://ww
Explain all the steps you have been doing , open a new thread I will address it
there .
Your post does not clearly indicate how you are deploying the datasource ,
explain things in DETAIL and *NEVER* bloat the existing forum thread as it
becomes difficult for people to indentify the current issu
I am getting this same error. My ear does'nt contain any jdbc.jar files.
Configuration is:jdk1.6.0_03, jboss-4.2.2.GA, MySQL version 5.0.45, MySQL driver
C:\jboss-4.2.2.GA\server\default\lib\mysql-connector-java-5.1.5-bin.jar
Though I am seeing
C:\jboss-4.2.2.GA\server\default\tmp\deploy\tmp29174
Not a problem :-)
Note, this is a bug in the DriverManager. Basically what is going on is some
heinous cacheing of classes that prevents the class from being loaded.
Supposedly this is addressed in JDBC 4.0. Also, the Class.forName("classname")
mess goes away. The DriverManager will be able to
Wow, that was a swift response! Turnaround time of 4 minutes - ought to be in
an ad for JBoss
Indeed, the jar file was being deployed in the WAR module. I removed it from
the WAR and put in in the config/lib directory as specified, and it now seems
to be working reliably.
Thank you very
I was having the same problem and also switched to jtds, but the problem
remains.
My connection is failing randomly with "Apparently wrong driver class
specified for URL" error.
The connection will fail this way over and over again, then will randomly
begin to work.It's maddening! Is a
How are you deploying your datasource? Are any of the JDBC jars contained in
the lib directory or your WAR? Do any of the JDBC jar files reside in an EAR?
Typically we see this error when a user tries to deploy the jars inside of an
application archive and not in the server/server-config/lib di
10 matches
Mail list logo