-->
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.  [ 1 post ] 
Author Message
 Post subject: Problem with set isolation level in transaction log
PostPosted: Wed Jan 30, 2013 11:36 am 
Newbie

Joined: Fri Jan 25, 2013 1:36 pm
Posts: 1
Hi.

My company has an application built on Spring and Hibernate + JPA. Because of a legacy application that uses the same db and tables, we globally set our isolation level to 0 in context.xml. What we are seeing is that every select statement from the hibernate app is producing entries in our database's transaction log. The result of this is a log file that grows too fast. Ideally we would like to turn off this logging completely, but have failed to find a way to do so.

Any suggestions?

Sample of the log

--CONNECT-1001-0014636195-csdbo-2012/nov/28 09:13
--BEGIN TRANSACTION-1001-0014636208
BEGIN TRANSACTION
go
--SQL-1001-0014636209
set option csdbo.Isolation_level = '0'
go
--COMMIT-1001-0014636259
COMMIT WORK
go
--BEGIN TRANSACTION-1001-0014636260
BEGIN TRANSACTION
go
--SQL-1001-0014636261
set option csdbo.Isolation_level = '0'
go
--COMMIT-1001-0014636311
COMMIT WORK
go


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

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.