java.sql.SQLWarning: [Microsoft][SQLServer 2000 Driver for JDBC]Database changed to X


I’m using Hibernate 3.2.1 and database SQLServer2000 while I’m try to insert some data using my dao, some warning occurred like this:

java.sql.SQLWarning: [Microsoft][SQLServer 2000 Driver for JDBC]Database changed to BTN_SPP_DB
    at com.microsoft.jdbc.base.BaseWarnings.createSQLWarning(Unknown Source)
    at com.microsoft.jdbc.base.BaseWarnings.get(Unknown Source)
    at com.microsoft.jdbc.base.BaseConnection.getWarnings(Unknown Source)
    at org.hibernate.util.JDBCExceptionReporter.logAndClearWarnings(JDBCExceptionReporter.java:22)
    at org.hibernate.jdbc.ConnectionManager.closeConnection(ConnectionManager.java:443)
    at org.hibernate.jdbc.ConnectionManager.aggressiveRelease(ConnectionManager.java:400)
    at org.hibernate.jdbc.ConnectionManager.afterTransaction(ConnectionManager.java:287)
    at org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:221)
    at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:119)
    at co.id.hanoman.btnmw.spp.dao.TagihanDao.save(TagihanDao.java:43)
    at co.id.hanoman.btnmw.spp.dao.TagihanDao.save(TagihanDao.java:1)
    at co.id.hanoman.btnmw.spp.dao.test.TagihanDaoTest.testSave(TagihanDaoTest.java:81)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
    at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
    at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
    at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
    at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
    at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
    at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
    at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
    at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
    at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
    at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
    at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

This is a normal message from the MS jdbc driver when the database that you are using for JM isn”t the default database for the sql server account you are using to access the database. Pretty much ignore it – it”s completely harmless.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s