-->
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: how to turn off logging error when DB exception occured.
PostPosted: Wed Nov 17, 2004 2:35 pm 
Newbie

Joined: Sun Nov 07, 2004 9:58 pm
Posts: 6
Iam trying to aquire exclusive lock with refresh on request object and getting following exception which is logged to console. Iam catching exception in HibernateException catch block, Iam not logging in catch block, but Iam stll seeing the log error message on console. Is there anyway to turn off log message.

[b]Hibernate version:[/b]
2.1.7
[b]Mapping documents:[/b]

[b]Code between sessionFactory.openSession() and session.close():[/b]
try {
session.refresh(requestObject, Mode.UPGRADE_NOWAIT);
return true;
} catch (HibernateException e) {
}
[b]Full stack trace of any exception that occurs:[/b]
<Nov 17, 2004 10:13:47 AM PST> <Error> <MAS Logger> <000000> <net.sf.hibernate.util.JDBCExceptionReporter: could not load: [com.Request#78]
java.sql.SQLException: ORA-00054: resource busy and acquire with NOWAIT specified

at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:579)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1894)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:831)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2496)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2840)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:608)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:536)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:80)
at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:87)
at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:875)
at net.sf.hibernate.loader.Loader.doQuery(Loader.java:269)
at net.sf.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:133)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:911)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:931)
at net.sf.hibernate.loader.SimpleEntityLoader.load(SimpleEntityLoader.java:58)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:419)
at net.sf.hibernate.impl.SessionImpl.refresh(SessionImpl.java:2183)

[b]Name and version of the database you are using:[/b]
oracle9i

[b]The generated SQL (show_sql=true):[/b]

[b]Debug level Hibernate log excerpt:[/b]


Top
 Profile  
 
 Post subject: Any luck?
PostPosted: Wed Oct 26, 2005 12:36 pm 
Newbie

Joined: Wed Aug 10, 2005 11:14 am
Posts: 4
Hi,

Did you ever have any luck squashing this error? I'm facing the exact same problem - our logs are rich enough in data as it is without filling it with these traces!

Cheers

Nick Cotter


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.