Operation “add” failed – address: I am trying to move from JBoss 6 to JBoss 7 and am running into a few difficulties. Sign up using Email and Password. Is there anything that you see in the server. We have 2 possible case for jdbc driver:
|Date Added:||9 February 2012|
|File Size:||29.11 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
How to actually create a Datasource. Forums Downloads Projects Buzz. This is the kind of driver you can use with hot deploy because we are able to get autotically the Driver class name. I run jboss in standalone mode and have set my datasource in the standalone. I just goto the Datasource Page of jbos Admin Console and select “Add Datasource” and follow the step-by-step instructions displayed. Shirishkumar Bari 1, 18 The correct config in your case should be: I agree with you that in this case the error is misleading.
I managed to resolve the issue with this. How are you issuing that management operation?
I did this and it still does not work for me in JBoss 7. Connection from DataSource only allows “selects”!
Correct Answers – 4 points. Sign up or log in Sign up using Google. Omid 1 6 Required services that are not installed: Sign up using Email and Password. Happy you mxsql a workaround. Thank you for your insights. Do you have “Unable to find driver class name in I have found a work around at least for now.
Installing the JDBC Driver and Deploying the DataSource
Sign up using Facebook. I did try both of these options and continued to receive the same error message. It’s interesting that you had to specify the username and password as part of the connection URL and it indeed is what the documentation states here http: If I try to add “driver-name” it I get a parse error. TestDS is missing [jboss. Glad to know that you got it working.
However I am facing issues. BTW have you taken a look to http: The module file looks like this. I don’t know if that made any difference or msswl.
What does it look like? Email Required, but never shown. In a nutshell they have according mssqql jdbc 4 spec a file specifying the name of vendor class implementing Driver.
More properly you are using another driver which work out of the box msssl your setting since it is jdbc 4 compliant. Either way, the quickest way to test a connection in pool is to use the admin console to issue that request and let it manage what management operation needs to be invoked behind the scenes.