Hi, all:
I'm using Spring (1.1 RC1) + Hibernate (2.1) + Oracle JDBC driver (8.1.7) + Bea Weblogic 6.1 SP3 + Oracle 8.1.7 db server .... though it seems I could CRUD objects using Hibernate successfully but found an annoying warning as stated below.
Is there anyway I could disable this message or is it a bug?... I tried to upgrade the Oracle driver to 9.2.0.3 but still get the same warning.....
Thanks..
Daniel.
2004-08-03 15:32:22,997 WARN jdbc.datasource.DataSourceUtils:200 -> Could not set JDBC connection read-only
java.sql.SQLException: setReadOnly: Read-only connections not supported
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:273)
at oracle.jdbc.driver.OracleConnection.setReadOnly(OracleConnection.java:997)
at weblogic.jdbc.pool.Connection.setReadOnly(Connection.java:171)
at weblogic.jdbc.rmi.internal.ConnectionImpl.setReadOnly(ConnectionImpl.java:244)
at weblogic.jdbc.rmi.SerialConnection.setReadOnly(SerialConnection.java:254)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnection ForTransaction(DataSourceUtils.java:196)
at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin (HibernateTransactionManager.java:300)
at org.springframework.transaction.support.AbstractPlatformTransactionMa
nager.getTransaction(AbstractPlatformTransactionManager.java:270)
at org.springframework.transaction.interceptor.TransactionAspectSupport.
createTransactionIfNecessary(TransactionAspectSupport.java:200)
at org.springframework.transaction.interceptor.TransactionInterceptor.in
voke(TransactionInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:140)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-08-03
Hi, all:
I'm using Spring (1.1 RC1) + Hibernate (2.1) + Oracle JDBC driver (8.1.7) + Bea Weblogic 6.1 SP3 + Oracle 8.1.7 db server .... though it seems I could CRUD objects using Hibernate successfully but found an annoying warning as stated below.
Is there anyway I could disable this message or is it a bug?... I tried to upgrade the Oracle driver to 9.2.0.3 but still get the same warning.....
Thanks..
Daniel.
2004-08-03 15:32:22,997 WARN jdbc.datasource.DataSourceUtils:200 -> Could not set JDBC connection read-only
java.sql.SQLException: setReadOnly: Read-only connections not supported
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:273)
at oracle.jdbc.driver.OracleConnection.setReadOnly(OracleConnection.java:997)
at weblogic.jdbc.pool.Connection.setReadOnly(Connection.java:171)
at weblogic.jdbc.rmi.internal.ConnectionImpl.setReadOnly(ConnectionImpl.java:244)
at weblogic.jdbc.rmi.SerialConnection.setReadOnly(SerialConnection.java:254)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnection ForTransaction(DataSourceUtils.java:196)
at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin (HibernateTransactionManager.java:300)
at org.springframework.transaction.support.AbstractPlatformTransactionMa
nager.getTransaction(AbstractPlatformTransactionManager.java:270)
at org.springframework.transaction.interceptor.TransactionAspectSupport.
createTransactionIfNecessary(TransactionAspectSupport.java:200)
at org.springframework.transaction.interceptor.TransactionInterceptor.in
voke(TransactionInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:140)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, it's just a warning: Some JDBC drivers simply ignore a setReadOnly call if they can't specifically handle it, some others throw an exception (like in your case). Still, this should not cause any issues.
We should probably deemphasize that log message, maybe logging it at INFO (or even DEBUG) rather than at WARN, as it can really almost always be ignored.
Juergen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, all:
I'm using Spring (1.1 RC1) + Hibernate (2.1) + Oracle JDBC driver (8.1.7) + Bea Weblogic 6.1 SP3 + Oracle 8.1.7 db server .... though it seems I could CRUD objects using Hibernate successfully but found an annoying warning as stated below.
Is there anyway I could disable this message or is it a bug?... I tried to upgrade the Oracle driver to 9.2.0.3 but still get the same warning.....
Thanks..
Daniel.
2004-08-03 15:32:22,997 WARN jdbc.datasource.DataSourceUtils:200 -> Could not set JDBC connection read-only
java.sql.SQLException: setReadOnly: Read-only connections not supported
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:273)
at oracle.jdbc.driver.OracleConnection.setReadOnly(OracleConnection.java:997)
at weblogic.jdbc.pool.Connection.setReadOnly(Connection.java:171)
at weblogic.jdbc.rmi.internal.ConnectionImpl.setReadOnly(ConnectionImpl.java:244)
at weblogic.jdbc.rmi.SerialConnection.setReadOnly(SerialConnection.java:254)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnection ForTransaction(DataSourceUtils.java:196)
at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin (HibernateTransactionManager.java:300)
at org.springframework.transaction.support.AbstractPlatformTransactionMa
nager.getTransaction(AbstractPlatformTransactionManager.java:270)
at org.springframework.transaction.interceptor.TransactionAspectSupport.
createTransactionIfNecessary(TransactionAspectSupport.java:200)
at org.springframework.transaction.interceptor.TransactionInterceptor.in
voke(TransactionInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:140)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
Hi, all:
I'm using Spring (1.1 RC1) + Hibernate (2.1) + Oracle JDBC driver (8.1.7) + Bea Weblogic 6.1 SP3 + Oracle 8.1.7 db server .... though it seems I could CRUD objects using Hibernate successfully but found an annoying warning as stated below.
Is there anyway I could disable this message or is it a bug?... I tried to upgrade the Oracle driver to 9.2.0.3 but still get the same warning.....
Thanks..
Daniel.
2004-08-03 15:32:22,997 WARN jdbc.datasource.DataSourceUtils:200 -> Could not set JDBC connection read-only
java.sql.SQLException: setReadOnly: Read-only connections not supported
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:273)
at oracle.jdbc.driver.OracleConnection.setReadOnly(OracleConnection.java:997)
at weblogic.jdbc.pool.Connection.setReadOnly(Connection.java:171)
at weblogic.jdbc.rmi.internal.ConnectionImpl.setReadOnly(ConnectionImpl.java:244)
at weblogic.jdbc.rmi.SerialConnection.setReadOnly(SerialConnection.java:254)
at org.springframework.jdbc.datasource.DataSourceUtils.prepareConnection ForTransaction(DataSourceUtils.java:196)
at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin (HibernateTransactionManager.java:300)
at org.springframework.transaction.support.AbstractPlatformTransactionMa
nager.getTransaction(AbstractPlatformTransactionManager.java:270)
at org.springframework.transaction.interceptor.TransactionAspectSupport.
createTransactionIfNecessary(TransactionAspectSupport.java:200)
at org.springframework.transaction.interceptor.TransactionInterceptor.in
voke(TransactionInterceptor.java:50)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
ReflectiveMethodInvocation.java:140)
Well, it's just a warning: Some JDBC drivers simply ignore a setReadOnly call if they can't specifically handle it, some others throw an exception (like in your case). Still, this should not cause any issues.
We should probably deemphasize that log message, maybe logging it at INFO (or even DEBUG) rather than at WARN, as it can really almost always be ignored.
Juergen