-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: SQL Server JDBC warnings
PostPosted: Wed Mar 14, 2007 1:02 pm 
Newbie

Joined: Mon Dec 27, 2004 8:10 pm
Posts: 7
Location: Redwood City, CA
I'm getting the following entries in my log file on every hibernate invocation:

[3/14/07 11:42:06:890 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter SQL Warning: 0, SQLState:
[3/14/07 11:42:06:890 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter [Microsoft][SQLServer 2000 Driver for JDBC]Database changed to mydb
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter SQL Warning: 5701, SQLState: 01000
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Changed database context to 'mydb'.
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter SQL Warning: 0, SQLState:
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter [Microsoft][SQLServer 2000 Driver for JDBC]Language changed to us_english
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter SQL Warning: 5703, SQLState: 01000
[3/14/07 11:42:06:906 CDT] 5282d51e JDBCException W org.hibernate.util.JDBCExceptionReporter [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Changed language setting to us_english.



The logs seem harmless enough, but is this normal? Is there a way to disable this logging without eliminating all logs from JDBCExceptionReporter?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Mar 18, 2009 3:51 pm 
Newbie

Joined: Sun Sep 28, 2003 9:50 am
Posts: 1
This is a stupid Sybase/SQL Server trick. It happens regardless of whether the connection is made from hibernate. Solution is to get a real database. I don't have that choice but you might.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.