maven工程中hibernate的二級快取ehcache的配置
2017-06-05 21:32:54 45249 <DEBUG> Result row: EntityKey[com.cosw.entity.huaian.SysParam#1] <org.hibernate.loader.Loader:org.hibernate.loader.Loader.getRow(Loader.java:1486)(main)>
2017-06-05 21:32:54 45259 <DEBUG> Result set row: 1 <org.hibernate.loader.Loader:org.hibernate.loader.Loader.processResultSet(Loader.java:952)(main)>
2017-06-05 21:32:54 45260 <DEBUG> Result row: EntityKey[com.cosw.entity.huaian.SysParam#2] <org.hibernate.loader.Loader:org.hibernate.loader.Loader.getRow(Loader.java:1486)(main)>
2017-06-05 21:32:54 45261 <DEBUG> Result set row: 2 <org.hibernate.loader.Loader:org.hibernate.loader.Loader.processResultSet(Loader.java:952)(main)>
2017-06-05 21:32:54 45261 <DEBUG> Result row: EntityKey[com.cosw.entity.huaian.SysParam#17] <org.hibernate.loader.Loader:org.hibernate.loader.Loader.getRow(Loader.java:1486)(main)>
2017-06-05 21:32:54 45266 <DEBUG> Resolving associations for [com.cosw.entity.huaian.SysParam#1] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:160)(main)>
// 插敘出三條記錄,通過Adding entity to second-level cache 放入快取中
2017-06-05 21:32:54 45267 <DEBUG> Adding entity to second-level cache: [com.cosw.entity.huaian.SysParam#1] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:194)(main)>
2017-06-05 21:32:54 45281 <DEBUG> Done materializing entity [com.cosw.entity.huaian.SysParam#1] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:286)(main)>
2017-06-05 21:32:54 45282 <DEBUG> Resolving associations for [com.cosw.entity.huaian.SysParam#2] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:160)(main)>
2017-06-05 21:32:54 45283 <DEBUG> Adding entity to second-level cache: [com.cosw.entity.huaian.SysParam#2] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:194)(main)>
2017-06-05 21:32:54 45285 <DEBUG> Done materializing entity [com.cosw.entity.huaian.SysParam#2] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:286)(main)>
2017-06-05 21:32:54 45286 <DEBUG> Resolving associations for [com.cosw.entity.huaian.SysParam#17] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:160)(main)>
2017-06-05 21:32:54 45287 <DEBUG> Adding entity to second-level cache: [com.cosw.entity.huaian.SysParam#17] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:194)(main)>
2017-06-05 21:32:54 45289 <DEBUG> Done materializing entity [com.cosw.entity.huaian.SysParam#17] <org.hibernate.engine.internal.TwoPhaseLoad:org.hibernate.engine.internal.TwoPhaseLoad.doInitializeEntity(TwoPhaseLoad.java:286)(main)>
2017-06-05 21:32:54 45292 <DEBUG> HHH000117: HQL: [CRITERIA] select this_.id as id1_7_0_, this_.sys_code as sys_code2_7_0_, this_.sys_name as sys_name3_7_0_, this_.sys_value as sys_valu4_7_0_ from huaian_sys_param this_, time: 64ms, rows: 3 <org.hibernate.stat.internal.ConcurrentStatisticsImpl:org.hibernate.stat.internal.ConcurrentStatisticsImpl.queryExecuted(ConcurrentStatisticsImpl.java:412)(main)>
2017-06-05 21:32:54 45293 <DEBUG> Caching query results in region: org.hibernate.cache.internal.StandardQueryCache; timestamp=6130358578888704 <org.hibernate.cache.internal.StandardQueryCache:org.hibernate.cache.internal.StandardQueryCache.put(StandardQueryCache.java:130)(main)>
// 需要說名的是，快取中的存放形式是key-value,key為查詢的sql 語句
2017-06-05 21:32:54 45294 <DEBUG> key: sql: select this_.id as id1_7_0_, this_.sys_code as sys_code2_7_0_, this_.sys_name as sys_name3_7_0_, this_.sys_value as sys_valu4_7_0_ from huaian_sys_param this_; parameters: ; transformer:
2017-06-05 21:32:54 45296 <DEBUG> committing <org.hibernate.engine.transaction.spi.AbstractTransactionImpl:org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:175)(main)>
2017-06-05 21:32:54 45297 <DEBUG> committed JDBC Connection <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:113)(main)>
2017-06-05 21:32:54 45298 <DEBUG> re-enabling autocommit <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.releaseManagedConnection(JdbcTransaction.java:126)(main)>
2017-06-05 21:32:54 45303 <INFO > Session Metrics {
2386920 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
927015 nanoseconds spent preparing 1 JDBC statements;
1851156 nanoseconds spent executing 1 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
10317456 nanoseconds spent performing 4 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
5462738 nanoseconds spent performing 1 L2C misses;
0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities and 0 collections);
67741 nanoseconds spent executing 1 partial-flushes (flushing a total of 0 entities and 0 collections)
} <org.hibernate.engine.internal.StatisticalLoggingSessionEventListener:org.hibernate.engine.internal.StatisticalLoggingSessionEventListener.end(StatisticalLoggingSessionEventListener.java:275)(main)>
2017-06-05 21:32:54 45304 <DEBUG> Releasing JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.releaseConnection(LogicalConnectionImpl.java:246)(main)>
2017-06-05 21:32:54 45307 <DEBUG> Released JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.releaseConnection(LogicalConnectionImpl.java:264)(main)>
2017-06-05 21:32:59 50308 <DEBUG> Obtaining JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:226)(main)>
2017-06-05 21:32:59 50311 <DEBUG> Obtained JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:232)(main)>
2017-06-05 21:32:59 50313 <DEBUG> begin <org.hibernate.engine.transaction.spi.AbstractTransactionImpl:org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160)(main)>
2017-06-05 21:32:59 50313 <DEBUG> initial autocommit status: true <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:69)(main)>
2017-06-05 21:32:59 50314 <DEBUG> disabling autocommit <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:71)(main)>
2017-06-05 21:32:59 50316 <DEBUG> Checking cached query results in region: org.hibernate.cache.internal.StandardQueryCache <org.hibernate.cache.internal.StandardQueryCache:org.hibernate.cache.internal.StandardQueryCache.get(StandardQueryCache.java:166)(main)>
2017-06-05 21:32:59 50316 <DEBUG> key: sql: select this_.id as id1_7_0_, this_.sys_code as sys_code2_7_0_, this_.sys_name as sys_name3_7_0_, this_.sys_value as sys_valu4_7_0_ from huaian_sys_param this_; parameters: ; transformer:
2017-06-05 21:32:59 50317 <DEBUG> Checking query spaces are up-to-date: [huaian_sys_param] <org.hibernate.cache.internal.StandardQueryCache:org.hibernate.cache.internal.StandardQueryCache.isUpToDate(StandardQueryCache.java:248)(main)>
2017-06-05 21:32:59 50318 <DEBUG> key: huaian_sys_param <org.hibernate.cache.ehcache.internal.regions.EhcacheGeneralDataRegion:org.hibernate.cache.ehcache.internal.regions.EhcacheGeneralDataRegion.get(EhcacheGeneralDataRegion.java:74)(main)>
2017-06-05 21:32:59 50318 <DEBUG> [huaian_sys_param] last update timestamp: 6130358577954816, result set timestamp: 6130358578888704 <org.hibernate.cache.spi.UpdateTimestampsCache:org.hibernate.cache.spi.UpdateTimestampsCache.isUpToDate(UpdateTimestampsCache.java:187)(main)>
// 返回快取中的結果，此時並沒有像第一次一樣執行select的sql 語句，直接從快取返回結果
2017-06-05 21:32:59 50319 <DEBUG> Returning cached query results <org.hibernate.cache.internal.StandardQueryCache:org.hibernate.cache.internal.StandardQueryCache.get(StandardQueryCache.java:188)(main)>
2017-06-05 21:32:59 50329 <DEBUG> committing <org.hibernate.engine.transaction.spi.AbstractTransactionImpl:org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:175)(main)>
2017-06-05 21:32:59 50330 <DEBUG> committed JDBC Connection <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:113)(main)>
2017-06-05 21:32:59 50330 <DEBUG> re-enabling autocommit <org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction:org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.releaseManagedConnection(JdbcTransaction.java:126)(main)>
2017-06-05 21:32:59 50334 <INFO > Session Metrics {
2761749 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
0 nanoseconds spent preparing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
0 nanoseconds spent performing 0 L2C puts;
2794593 nanoseconds spent performing 5 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities and 0 collections);
10264 nanoseconds spent executing 1 partial-flushes (flushing a total of 0 entities and 0 collections)
} <org.hibernate.engine.internal.StatisticalLoggingSessionEventListener:org.hibernate.engine.internal.StatisticalLoggingSessionEventListener.end(StatisticalLoggingSessionEventListener.java:275)(main)>
2017-06-05 21:32:59 50334 <DEBUG> Releasing JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.releaseConnection(LogicalConnectionImpl.java:246)(main)>
2017-06-05 21:32:59 50337 <DEBUG> Released JDBC connection <org.hibernate.engine.jdbc.internal.LogicalConnectionImpl:org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.releaseConnection(LogicalConnectionImpl.java:264)(main)>
2017-06-05 21:33:00 50374 <INFO > ====OBJECT====0====[
sysName=單日最大交易限額
sysCode=20170605133623
sysValue=500
id=1
], [email protected][
sysName=單日最大交易限額
sysCode=20170605134605
sysValue=500
id=2
], [email protected][
sysName=單日最大交易限額
sysCode=20170605213253
sysValue=500
id=17
]] <com.cosw.cache.EhcacheTest:com.cosw.cache.EhcacheTest.ehcacheSave(EhcacheTest.java:42)(main)>
相關推薦
hibernate二級快取 Ehcache配置詳解
一、hibernate快取簡介 一級快取(session):內部快取 事務範圍：快取只能被當前事務訪問。快取的生命週期依賴於事務的生命週期，當事務結束時，快取也就結束生命週期。 二級快取(sessionFactory): 快取被應用範圍內的所有事務共享。 這些事務
maven工程中hibernate的二級快取ehcache的配置
2017-06-05 21:32:54 45242 <DEBUG> Result set row: 0 <org.hibernate.loader.Loader:org.hibernate.loader.Loader.processResultSet(Loader.java:952)(mai
Hibernate 二級快取-ehcache
1 新增依賴包 <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>
搭建Hibernate二級快取EHcache的環境
常見的快取元件 在預設情況下，hibernate會使用EHCache作為二級快取元件。但是，可以通過設定hibernate.cache.provider_class屬性，指定其他的快取策略，該快取策略必須實現org.hibernate.cache.Cach
maven工程中讀取resource目錄下配置檔案
在maven工程中，我們會將配置檔案放到src/main/resources下面，例如我們需要確認resource 下的檔案編譯之後存放的位置。它編譯的路徑直接位於classes下面，這個路徑其實就是classPath的路徑，所以，在resources 根目錄下的配置檔案其實
Hibernate二級快取以及ehcache的搭建配置
前言 這次主要複習Hibernate的二級快取的相關知識，配置以及使用。二級快取主要採用第三方的ehcache，也將介紹ehcache快取的相關配置屬性以及在專案中的搭建，具體的專案檢視下一篇的 Maven搭建SpringMVC+Hibernate專案詳解
spring boot整合ehcache 2.x 用於hibernate二級快取
spring boot整合ehcache 2x 用於hibernate二級快取 專案依賴 Ehcache簡介 hibernate二級快取配置 ehcache配置檔案 ehcache事件監聽 註解方式使用二級快取 完整程式碼 本文將介紹如何在spring boot中整合ehcache作為hiberna
Hibernate二級快取實現的方式(在類中，在方法上實現的思路)
資料庫快取 - 幕布 資料庫快取兩種處理方式一種處理model，只查詢快取，不更新快取參考列子 使用者表的敏感詞列表思路專案pom檔案匯入hibernate-encache快取檔案建立
Eclipse maven工程中如何配置slf4j+junit
Author: kagula Last Update Date: 2016-9-7 環境： [1]Eclipse Mars.2 [2]JDK 1.7 [3]slf4j-log4j12 1.7.2 [4]junit 4.11 Introduction 這裡記下免得每
Maven工程中自動拷貝資原始檔的 pom檔案配置方法
<plugin> <groupId>org.apache.maven.plugins</groupId>
hibernate中的二級快取如何搭建
1.右鍵單擊專案下的Hibernate 4.1.4 Libraries選擇properties會彈出如下框 如上圖選中 在Enable project。。。前的框，然後再單擊上面Extra Libraries選項的三角形會彈出下面類容 只選擇
詳解Hibernate中的二級快取
1.前言 這篇部落格再前幾篇部落格的基礎上來講解一下，Hibernate中的二級快取，二級快取是屬於SessionFactory級別的快取機制。第一級別的快取是Session級別的快取，是屬於事
Hibernate中使用分散式快取ehcache-core-1.3.0
前言 廢話不多說，來這看的，不管你是會ehcache或者從來沒接觸過的，保證看過之後，都能構建一個自己的ehcache專案。因為我在寫這篇部落格的時候，是一邊在配置一邊在記錄過程中遇到的問題，等於是在手把手教學。下面直入正題。 一、下載相關jar包 網上下載ehcache-
maven工程web層的web.xml配置文檔內容
ati exp expose param 過期 for work utf-8 xmlns 下面是web層，web.xml配置文檔裏面需要配置的東西： 1、lo4j配置 2、讀取spring文件配置 3、設計路徑變量值 4、spring字符集過濾器 5、登陸過濾器 6、spr
eclipse maven工程中src/main/resources目錄下創建的文件夾是包圖標的解決方法
-s art ont box ext 創建 == dig views 如圖:在src/main/resources目錄下創建的文件夾卻以包的圖標顯示 修改方法: 入下圖,按順序1 ,2,3,4操作,把3處remove,在4處添加** 修改後如下: 然後點擊完成後,
在maven工程中搭建SSM框架的錯誤總結
clip build etime 代碼 class ati timezone 項目 mysql 第一次搭建Maven工程走了很多彎路，現在總算把項目搭起來並且能正常運行了。故總結一下教訓 1.在建立Maven工程前，先確定成功下載安裝了Maven。 命令行用 mvn -v
maven工程中警告[WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platform dependent!
文件 prop 源文件 使用 end 默認 .so utf-8 source [WARNING] Using platform encoding (GBK actually) to copy filtered resources, i.e. build is platfor
入門案例 - maven工程中ssm的整合
我們可以通過一個簡單的功能需求: 在頁面輸入一個 id , 頁面跳轉並返回該 id 對應的 item 明細 來實現 maven 工程中 ssm 的整合. 首先,要做的是配置相關環境(資料庫模板匯入 maven工程的建立等) 一. 資料庫模板匯入 1. 開啟資料庫(我將使
Hibernate 二級快取和查詢快取
一級快取: 1,在session上面有一個一級快取;一級快取的生命週期和session相同,一級快取最大生命週期就是一個執行緒;在web環境下面,session的最大生命週期就是一次請求; 2,一級快取可以用來幹嘛? &nb
Hibernate 二級快取的作用
使用快取，是需要對應用系統進行效能優化而常採用的一種重要手段。合理地運用快取，可以極大的提高應用系統的執行效率。 Hibernate中應用快取：因為應用程式訪問資料庫，讀寫資料的代價非常高，而利用持久層的快取可以減少應用程式與資料庫之間的互動，即把訪問過的資料儲存到快取中，應用程式再次訪問已經訪