Hello!We have a maintenance job on MSSQL server scheduled for the weekend.some times we arrive at the beginning of a week and see that a user lefthis screen open on a SQL record and the job is still waiting blocked bythat user. Please give me an idea how to overcome this.Thanks in advance*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
Hi;I went to the microsoft site to try to find a guide to the errormessages that the jdbc drivers give ( for sqlserver 2000 ).I had no luck.Does anyone know if there is such a guide?I got this mysterious error message below in my logs ( nothing visiblein user land ).Anyone know what it means?Thanks in advanceStevejava.sql.SQLException: [Microsoft][SQLServer 2000 Driver forJDBC][SQLServer]Transaction (Process ID 151) was deadlocked on lockresources with another process and has been chosen as the deadlockvictim. Rerun the transaction.
Hello,I am working with the driver JDBC and I have a strange error that I can't find in Google for example.Caused by: com.seeburger.smarti.util.SmartiEJBException: nested exception is: com.seeburger.smarti.dao.DAOSysException: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Must declare the variable '@P2GROUP'.I don't know what is this variable '@P2GROUP'.Does anybody know it ?Thanks
I have read similar posts to this, but I am still having problems.
I am trying to use connection pooling to connect to a local SQL Server 2005 database. I am running my application using MyEclipse Enterprise Workbench. I have verified that sqljdbc.jar resides in "WebRoot/WEB-INF/lib/"
I've got an import app written in Java. One table I'm importing from contains 22 million records. When I run the app in a 2000 environment, I have my max heap set at 512, and the table gets imported. When I run in a 2005 environment, I have to change the max heap to 1152 or it will error out with a similiar error:
com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:Java heap space. Result set size:854,269,999. JVM total memory size:1,065,484,288. (<--this is with max heap at 1024)
what is the difference between the 2000 and 2005 JDBC that I have to set max heap in one and not the other?
I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get: Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t rue; net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa me=AdventureWorks;integratedSecurity=true; at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1030) at net.windward.xmlreport.RunReport.main(RunReport.java:165) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe curity property value:true at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U nknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour ce) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1024) ... 1 more Exception in thread "main" net.windward.datasource.DataSourceException: net.wind ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true; at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1030) at net.windward.xmlreport.RunReport.main(RunReport.java:165) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe curity property value:true at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U nknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour ce) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1024) ... 1 more Any ideas? thanks - dave
Hello every one i had a design question.What would be the best way to approach a problem such as a perventing unsed and left open sql connections i have written a class called DataBase Manger but my question is should this class be static or none-static. right now the way i have is something like this private SqlConnection Get() { SqlConnection sqlCon = new SqlConnection(ConfigurationManager.ConnectionStrings["StringConnetionName"].ConnectionString); sqlCon.Open(); return sqlCon; } /// <summary> /// Closes a connection to the Database /// </summary> /// <param name="sqlCon"> Database connection to close</param> private void Let(SqlConnection sqlCon) { sqlCon.Close(); sqlCon = null; } then for example to run a store proc i have public int RunProc(string procName, params SqlParameter[] p) { SqlConnection con = Get(); try {
using (SqlCommand cmd = CreateCommand(con, procName, p)) { cmd.ExecuteNonQuery(); return (int)cmd.Parameters["ReturnValue"].Value; } } finally { Let(con); } } now every time in any class or method i need to create a new Database manager and call the run proc object. Would it be a better desing to make this class static? so it would be just DataBaseManger.RunProc(blah,blah) or is it a better OO design to have it the way i have it. is is more secure in a webapplication? can these connections be hijacked? thanks in adanvce, any help would greatly be apperiated. or any link to any related tutorials thanks,Amir
Hello All, kindly help me resolving following error. Earlier it was working fine with SQL server 2000, we want to migrate to sql server 2005. I am using websphere 6.0 with following jdbc_registry.properties contents. The driver file is copied under E:Program FilesIBMWebSphereAppServerlibext ***************************************************************************** driver.class=com.microsoft.sqlserver.jdbc.SQLServerDriver connection.url=jdbc: sqlserver://MyDBServer:1433;DatabaseName=abc;user=a; password=a user=a password=a ******************************************************************************
I am using sqljdbc_1.2.2828.100_enu drivers to connect to sql server 2005. following is the exception trace from my IDE.
************ Start Display Current Environment ************ WebSphere Platform 6.0 [BASE 6.0.2.13 cf130631.22] running with process name onschedule5Node01Cellonschedule5Node01server1 and process id 244 Host Operating System is Windows 2003, version 5.2 Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20050609 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM was.install.root = E:Program FilesIBMWebSphereAppServer user.install.root = E:Program FilesIBMWebSphereAppServer/profiles/default Java Home = E:Program FilesIBMWebSphereAppServerjavajre ws.ext.dirs = E:Program FilesIBMWebSphereAppServer/java/lib;E:Program FilesIBMWebSphereAppServer/profiles/default/classes;E:Program FilesIBMWebSphereAppServer/classes;E:Program FilesIBMWebSphereAppServer/lib;E:Program FilesIBMWebSphereAppServer/installedChannels;E:Program FilesIBMWebSphereAppServer/lib/ext;E:Program FilesIBMWebSphereAppServer/web/help;E:Program FilesIBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime Classpath = E:Program FilesIBMWebSphereAppServer/profiles/default/properties;E:Program FilesIBMWebSphereAppServer/properties;E:Program FilesIBMWebSphereAppServer/lib/bootstrap.jar;E:Program FilesIBMWebSphereAppServer/lib/j2ee.jar;E:Program FilesIBMWebSphereAppServer/lib/lmproxy.jar;E:Program FilesIBMWebSphereAppServer/lib/urlprotocols.jar Java Library path = E:Program FilesIBMWebSphereAppServerjavain;.;C:WINDOWSsystem32;C:WINDOWS;E:Program FilesIBMWebSphereAppServerin;E:Program FilesIBMWebSphereAppServerjavain;E:Program FilesIBMWebSphereAppServerjavajrein;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:Program FilesIBMWebSphereAppServerjavain ************* End Display Current Environment ************* [3/20/08 7:15:44:188 EST] 0000000a ManagerAdmin I TRAS0028I: The trace output is stored in the circular memory buffer, holding 8192 message objects. [3/20/08 7:15:44:531 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info. [3/20/08 7:15:44:531 EST] 0000000a ManagerAdmin A TRAS0007I: Logging to the service log is disabled [3/20/08 7:15:44:719 EST] 0000000a AdminInitiali A ADMN0015I: The administration service is initialized. [3/20/08 7:15:49:109 EST] 0000000a SystemOut O PLGC0057I: Plug-in configuration service is started successfully. [3/20/08 7:15:49:188 EST] 0000000a PMIImpl A PMON1001I: PMI is enabled [3/20/08 7:15:49:750 EST] 0000000a SibMessage I [:] CWSIU0000I: Release: WAS602.SIB Level: o0625.16 [3/20/08 7:15:49:766 EST] 0000000a SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true. [3/20/08 7:15:49:875 EST] 0000000a AuditServiceI A SECJ6004I: Security Auditing is disabled. [3/20/08 7:15:49:938 EST] 0000000a distSecurityC I SECJ0309I: Java 2 Security is disabled. [3/20/08 7:15:50:000 EST] 0000000a Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration. [3/20/08 7:15:50:016 EST] 0000000a distSecurityC I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class. [3/20/08 7:15:50:031 EST] 0000000a distSecurityC I SECJ0240I: Security service initialization completed successfully [3/20/08 7:15:50:297 EST] 0000000a ObjectPoolSer I OBPL0007I: Object Pool Manager service is disabled. [3/20/08 7:15:50:328 EST] 0000000a J2EEServiceMa I ASYN0059I: Work Manager service initialized successfully. [3/20/08 7:15:50:391 EST] 0000000a CScopeCompone I CSCP0002I: Compensation service is disabled. [3/20/08 7:15:50:531 EST] 0000000a SibMessage I [:] CWSID0006I: The SIB service was not enabled and will not be started. [3/20/08 7:15:50:531 EST] 0000000a ActivitySessi I WACS0045I: ActivitySession service is disabled. [3/20/08 7:15:50:562 EST] 0000000a SOAPContainer I WSWS1062I: SOAP Container Service has been initialized. [3/20/08 7:15:50:641 EST] 0000000a SchedulerServ I SCHD0036I: The Scheduler Service is initializing. [3/20/08 7:15:50:688 EST] 0000000a SchedulerServ I SCHD0037I: The Scheduler Service has been initialized. [3/20/08 7:15:50:875 EST] 0000000a StartUpServic I STUP0008I: The Startup Beans service is disabled. [3/20/08 7:15:50:891 EST] 0000000a I18nService I I18N0010I: The Internationalization service is created on server1. [3/20/08 7:15:50:891 EST] 0000000a I18nServiceSe I I18N0010I: The Internationalization service is disabled on server1. [3/20/08 7:15:51:406 EST] 0000000a SASRas A JSAS0001I: Security configuration initialized. [3/20/08 7:15:51:859 EST] 0000000a SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM [3/20/08 7:15:51:859 EST] 0000000a SASRas A JSAS0003I: Authentication mechanism: SWAM [3/20/08 7:15:51:875 EST] 0000000a SASRas A JSAS0004I: Principal name: OnProjectRealm/wsadmin [3/20/08 7:15:51:891 EST] 0000000a SASRas A JSAS0005I: SecurityCurrent registered. [3/20/08 7:15:52:047 EST] 0000000a SASRas A JSAS0006I: Security connection interceptor initialized. [3/20/08 7:15:52:078 EST] 0000000a SASRas A JSAS0007I: Client request interceptor registered. [3/20/08 7:15:52:156 EST] 0000000a SASRas A JSAS0008I: Server request interceptor registered. [3/20/08 7:15:52:172 EST] 0000000a SASRas A JSAS0009I: IOR interceptor registered. [3/20/08 7:15:53:031 EST] 0000000a CoordinatorIm I HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup. [3/20/08 7:15:53:062 EST] 0000000a DCSPluginSing I HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup. [3/20/08 7:15:53:344 EST] 0000000a NameServerImp A NMSV0018I: Name server available on bootstrap port 2809. [3/20/08 7:15:54:078 EST] 0000000a TreeBuilder W ODCF0002E: Exception: E:Program FilesIBMWebSphereAppServerprofilesdefaultconfigcellsonschedule5Node01Cellodeswebserver1_nodevariables.xml (The system cannot find the file specified). [3/20/08 7:15:54:203 EST] 0000000a UserRegistryI A SECJ0136I: Custom Registry:com.onproject.security.registry.JdbcRegistry has been initialized [3/20/08 7:15:54:344 EST] 0000000a distContextMa E SECJ0270E: Failed to get actual credentials. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:54:359 EST] 0000000a distSecurityC E SECJ0208E: An unexpected exception occurred when attempting to authenticate the server's id during security initialization. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:54:391 EST] 0000000a distSecurityC E SECJ0007E: Error during security initialization. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:59:406 EST] 0000000a SchedulerServ I SCHD0040I: The Scheduler Service is stopping. [3/20/08 7:15:59:422 EST] 0000000a SchedulerServ I SCHD0002I: The Scheduler Service has stopped. [3/20/08 7:15:59:438 EST] 0000000a AppProfileCom I ACIN0009I: The application profiling service is stopping. [3/20/08 7:15:59:438 EST] 0000000a ActivitySessi I WACS0049I: The ActivitySession service is stopping. [3/20/08 7:15:59:547 EST] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup META-INF/ws-server-components.xml [3/20/08 7:15:59:562 EST] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:194) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) Caused by: com.ibm.ws.exception.RuntimeError: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:322) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) ... 10 more Caused by: com.ibm.websphere.security.WSSecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2187) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) ... 17 more Caused by: com.ibm.websphere.security.auth.WSLoginFailedException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:435) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) ... 22 more Caused by: java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) ... 40 more
I have written a shell script that connects to a SQL Server 2005 database from Linux in order to monitor various areas of SQL.
One of the databases that are being monitored is mirrored, which is no problem in itself as I use the failoverPartner property in my connection string before I pass the TSQL. Unfortunately when the principal/mirror status changes, I get a constant stream of Failure Audit (Login failure) messages in the Mirror server Windows event log even though the failoverPartner property works and redirects to the partner, returning the correct information.
Here is a trace of the connection:
------
22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property : serverName Value:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:databaseNameValue:TESTDATABASE 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:failoverPartnerValue:SERVER2 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:integratedSecurityValue:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:loginTimeoutValue:3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: Calling securityManager.checkConnect(SERVER1,1433) 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: securityManager.checkConnect succeeded. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: Start time: 1172160120083 Time out time: 1172160123083 Timeout Unit Interval: 240 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER1 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120323 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 0 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER1 port: 1433 Timeout slice: 232 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerException logException FINE: *** SQLException:[Thread[main,5,main], IO:5571e, Dbc:a8327] com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "TESTDATABASE" requested by the login. The login failed. Msg 4060, Level 11, State 1, Cannot open database "TESTDATABASE" requested by the login. The login failed. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER2 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120369 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER2 port: 1433 Timeout slice: 237 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: adding new failover info server: SERVER1 instance: null database: TESTDATABASE server provided failover: SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverInfo failoverAdd FINE: Failover detected. failover partner=SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverMapSingleton putFailoverInfo FINE: Failover map add server: SERVER1; database:TESTDATABASE; Mirror:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: End of connect 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement <init> FINE: Statement properties ID:0 Connection:1 Result type:1003 (2003) Concurrency:1007 Fetchsize:128 bIsClosed:false tdsVersion:com.microsoft.sqlserver.jdbc.TDSVersion@15fea60 bCp1252:false useLastUpdateCount:true isServerSideCursor:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement doExecuteStatement FINE: Executing (not server cursor) USE TESTDATABASE SELECT "TESTCOLUMN" FROM TEST_TABLE ORDER BY DateTime 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection close FINE: Closing connection ID:1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property : serverName Value:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:databaseNameValue:TESTDATABASE 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:failoverPartnerValue:SERVER2 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:integratedSecurityValue:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:loginTimeoutValue:3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: Calling securityManager.checkConnect(SERVER1,1433) 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: securityManager.checkConnect succeeded. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: Start time: 1172160120736 Time out time: 1172160123736 Timeout Unit Interval: 240 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER1 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120976 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 0 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER1 port: 1433 Timeout slice: 233 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerException logException FINE: *** SQLException:[Thread[main,5,main], IO:5571e, Dbc:a8327] com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "TESTDATABASE" requested by the login. The login failed. Msg 4060, Level 11, State 1, Cannot open database "TESTDATABASE" requested by the login. The login failed. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER2 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160121031 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER2 port: 1433 Timeout slice: 236 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: adding new failover info server: SERVER1 instance: null database: TESTDATABASE server provided failover: SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverInfo failoverAdd FINE: Failover detected. failover partner=SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverMapSingleton putFailoverInfo FINE: Failover map add server: SERVER1; database:TESTDATABASE; Mirror:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: End of connect 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement <init> FINE: Statement properties ID:0 Connection:1 Result type:1003 (2003) Concurrency:1007 Fetchsize:128 bIsClosed:false tdsVersion:com.microsoft.sqlserver.jdbc.TDSVersion@15fea60 bCp1252:false useLastUpdateCount:true isServerSideCursor:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement doExecuteStatement FINE: Executing (not server cursor) USE TESTDATABASE SELECT DATEDIFF(SECOND, DATETIME, GETDATE()) FROM TEST_TABLE 22-Feb-2007 16:02:01 com.microsoft.sqlserver.jdbc.SQLServerConnection close FINE: Closing connection ID:1
I cant supply a native database in the connection string (i.e Master) and then switch to the mirrored database in TSQL because the failoverPartner property does not apply to the session, only to the initial connection.
I'm writing a java application that queries sqlserver 2005 (and 2000). In case the sql browser service is stopped I need to use the named pipe property or the port property, right? But how could the program know at runtime what is the port and what is the pipe name? And how should a connection string to sqlserver 2005 (and 2000) that includes named pipe, look like?
from time to time i get a Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) when i try to use the MS SQLServer 2005 JDBC Driver 1.1. with our RMI Server.
The connect String is jdbc:sqlserver://localhost:1433;databaseName=EXBBERLIN The SQL Server Version is 2000 SP 3. I am using java Version 1.5.0_08-b03.
I have tried to start our Server with the -Djava.security.manager switch, but this does not resolve the problem.
The stacktrace of the exception is
java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at de.eidon.logis.database.DBReadManager_Stub.base2treeAndEdit(Unknown Source) .... Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
On another comnputer with almost the same setup everything works fine. The SQLServer 2000 JDBC Driver seems to work fine as well. Does anonne of you has an idea how to resolve this issue ?
try { // Establish the connection. Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); con = DriverManager.getConnection(connectionUrl,"ifc2","password");
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171) at connectURL.main(connectURL.java:43)
I am using the code example that came from Microsoft for making a JDBC connection. I looked at my configuration of SQL Server and change to use a static port 1433. I shut off Windows firewall to make sure it was not blocking communication.
When I try to telnet to port 1433 it says
Connecting To 1433...Could not open connection to the host, on port 23: Connect failed
public static void main(String[] args) { new Main(); }
}
The first call is ok, but the second throws an exception at sproc_stmt.executeQuery(); which says:
com.microsoft.sqlserver.jdbc.SQLServerException: Server failed to resume the transaction, desc: 3600000001. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source) at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.getPrepExecResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedStatementExecutionRequest.executeStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source) at javaapplication2.Main.getID(Main.java:53) at javaapplication2.Main.<init>(Main.java:33) at javaapplication2.Main.main(Main.java:85)
Am I doing something wrong or is this a bug?
I'm running on Win2003 with SQL Server 2005 Developer edition.
Does anybody have a working Java code sample that connects to an SQLServer 2005 database on a remote host, via the default named pipe, from a client using the SQLServer 2005 JDBC driver? Could you post it, or a pointer to it?
I've gotten java.sql DriverManager.getConnection() to work fine with TCP/IP connections before. But I'm a newbie with named pipes, and unclear on how the connection string/properties are different. I've tried to piece it together from multiple docs and threads, but haven't found sample code that quite fits my situation. I think a simple working example would best clarify the syntax.
The server is not using SQL Express. Most SQLServer configuration options are defaults; the named pipes protocol is enabled.
We are migrating SQL2000 to SQL2005, we are using sql2005 jdbc driver 1.0.
I got this error "com.microsoft.sqlserver.jdbc.SQLServerException: Server failed to resume the transaction", when my application calls a stored procedure which is a transaction.
Does anyone know what could be the problem, how to fix it?
I'm trying to connect to a sql server 2005 express edition but have some trouble with it: i can connect to sql server through eclipse IDE but when I create a jar and try connecting to server, I get the following error.
Exception in thread "main" java.lang.SecurityException: invalid SHA1 signature f ile digest for com/microsoft/sqlserver/jdbc/SQLServerException.class at sun.security.util.SignatureFileVerifier.verifySection(Unknown Source)
at sun.security.util.SignatureFileVerifier.processImpl(Unknown Source) at sun.security.util.SignatureFileVerifier.process(Unknown Source) at java.util.jar.JarVerifier.processEntry(Unknown Source) at java.util.jar.JarVerifier.update(Unknown Source) at java.util.jar.JarFile.initializeVerifier(Unknown Source) at java.util.jar.JarFile.getInputStream(Unknown Source) at sun.misc.URLClassPath$JarLoader$2.getInputStream(Unknown Source) at sun.misc.Resource.cachedInputStream(Unknown Source) at sun.misc.Resource.getByteBuffer(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$000(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source)
I'm using : - os : winxp - jdk1.5.0_06 - drivers : sqljdbc_1.1.1501.101 / sqljdbc_1.2.2828.100
Hi,I have a problem to set a JDBC connection as READ UNCOMMITED.setTransactionIsolation(Connection.TRANSACTION_REA D_UNCOMMITTED)This is causing lots of blocking on tablesand update or insert doesn't work properly.Does anyone have any idea what I'm missing here?I asked i-net support and they suggested to callsetAutoCommit(false) after the above functionand it didn't work.also suggested impltrans = true, and I changed that option on SQLand it caused more blocking.Thanks in advance for any info.
I am new to this environment and was asked to ensure that the transaction log shipping for SQL 2005 on W2K3 boxes is working properly. I noticed the db's on the secondary server are show "Restoring..." I am not sure if these were set up in No Recover Mode or Standby Mode. I have no access to the secondary db's. I get an error message when trying to access them (error 927). Monitoring was not set up initially and as you may or may not know can't be turned on after the fact...unless you delete the job and start over.
My question is is "Restoring..." normal and what does it indicate?
I am trying to 'load' a copy of a SQLServer 2000 database to SQLServer 2005 Express (on another host). The copy was provided by someone else - it came to me as a MDF file only, no LDF file.
I have tried to Attach the database and it fails with a failure to load the LDF. Is there any way to bypass this issue without the LDF or do I have to have that?
The provider of the database says I can create a new database and just point to the MDF as the data source but I can't seem to find a way to do that? I am using SQL Server Management Studio Express.
I have some code that should execute multiple statements and then commit. I am using the Microsoft SQL Server 2005 JDBC Driver 1.1.
The statements only commit ifI close the connection to the SQL Server 2005 instance. I've looked at the example given at http://msdn2.microsoft.com/en-us/library/ms378931.aspx and it doesn't require closing the connection in order to commit.
Example:
public void doCall(Connection con) { try { /*Turn off AutoCommit.*/ con.setAutoCommit(false);
I have an app that uses a sqlserver 2000 jdbc driver to connect to a sqlserver 2000.
Is it possible to do a direct replacement of sqlserver 2000 with sqlserver 2005 express just by reconfiguring the app to point to the express? The app would still be using the sqlserver 2000 jdbc driver to try and make the connection.
If that is a possibility, what can be some differences in the configuration? Previously with 2000 the config information I entered is:
server name: "machinename"( or ip). I've also tried "machiname/SQLEXPRESS"
DB name: name of db instance
port: 1433(default)
user and pass.
My attempts so far results in
"java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket."
and
"java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unable to connect. Invalid URL."
ConnectionString is below. Dim objDb As New SqlConnection("Data Source='(local)';trusted_connection=true;Initial Catalog=classdb") This ConnectionString occurs DB-Open-Error. Why? Show me the Solution.
We have a service that inserts some rows into a parent table (P) and child table (C). This operation is atomic and performed within a transaction.
We also have a service that queries these tables such that rows are (should only be) returned from P where there are no children for that parent.
The SQL that performs this is simplified below:
SELECT P.SomeCol FROM P LEFT OUTER JOIN C ON P.PKofP_Value = C.PkofP_Value WHERE C.PkofPValue IS NULL AND P.SomeOtherCol=0
Our expectation is that the query service should only return rows from P where there are no rows in C.
However, this seems not to be the case, and occasionally we find that rows from P are returned where there are matching rows in C.
We are sure that the process that inserts rows into P and C does so within a single transaction.
We have traced this with SQLTrace and can see the txn stag and committing and all operations using the same transactionid within the transaction.
We are running the default isolation level committed.
In SQLTrace we can see the query process start, the inserter process start and complete and then the query process continue (after presumably being blocked).
So how can the query process "miss" the child rows and return the parent from the above query?
Is it possible that, in this isolation level, the inserter process can block the query process such that when the inserter process commits and when the query process continues it does not see the child rows inserted because they were inserted in the table/index "behind" where the query process has already read - some kind of phantom phenomenon?
We are trying to move our application from SQL2005 to SQL2005, we are using 2005 jdbc driver 1.1.
The problem we have is, when a date is retrieved from the database, only the year part got correctly, but the date is automatically set to January 1 of that year. The interesting thing is this problem doesn't occur on local development environment (developer's windows platform), it only happens when we deploy the application to production server (unix).
I am trying to configure distributed transaction and XA support using Microsoft SQL Server 2005 JDBC Driver. I have coppied SQLJDBC_XA.dll from XA directory and placed in my sql server binn directory and trying to run the script xa_install.sql from binn directory with command as below :
But I am getting error saying : [DBNETLIB]SQL Server does not exist or access denied. [DBNETLIB]ConnectionOpen (Connect()).
when I replaced local host with the machine name it gives error : [Shared Memory]SQL Server does not exist or access denied. [Shared Memory]ConnectionOpen (Connect()).
where in I am able to test connection from Websphere using the same connection.
Please help some one ....... I am in URGENT need.... I need to enable XA suport for my application to run........
I have database with unlimited growth in Data with 2MB growth and Log File with 1MB growth. The continuous data is inserted with min 20KB per minute. We struct with following error and Log file size is too large (85GB) than Data file(20GB). Now server is not allowing to take backup as diskspace is not available.
Msg 9002, Level 17, State 2, Procedure DumpData, Line 10 The transaction log for database '%DB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
Please help me to resolved the issue and let me know hints to shrink LOG file. Data inserted are using ADO applications that uses some insert/select stored procedures that does not have begin transaction-Commit Transaction block as appliction issues the Commit over connection object.
I am accessing SQL2005 with C# code using OleDbConnection.
A try and catch block catches the following error once a while between the Open() and Close() of the connection:
ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.
I do not even have any idea where to start to debug this. The ExecuteNonQuery() runs a delete SQL query. It works 99.9% of the time. I do not see anything wrong when this error happens.