已經(jīng)一個(gè)多月沒(méi)有寫(xiě)東西了，不過(guò)最近確實(shí)很忙。前兩天在線(xiàn)上碰到一個(gè)C3P0的鏈接死鎖的異常，話(huà)說(shuō)這個(gè)上古神物 ,我已經(jīng)是很久不碰了。先貼異常

"apparent deadlocks"：名詞解釋是說(shuō)c3p0拿到鏈接之后，最終使用之后沒(méi)有返回到pool,導(dǎo)致死鏈檢測(cè)失敗。經(jīng)過(guò)在stack Overflow檢索,https://stackoverflow.com/questions/3730844/c3p0-apparent-deadlock-when-the-threads-are-all-empty.發(fā)現(xiàn)增加一個(gè)statementCacheNumDeferredCloseThreads該參數(shù)的定義，就可以避免這個(gè)問(wèn)題。

經(jīng)過(guò)查看官方文檔：http://www.mchange.com/projects/c3p0/#statementCacheNumDeferredCloseThreads

解釋?zhuān)喝绻言撝翟O(shè)為超過(guò)1，statement的緩存就會(huì)自動(dòng)跟蹤當(dāng)前可用的connections,如果沒(méi)有再用，就會(huì)自動(dòng)銷(xiāo)毀掉。如果需要另外的線(xiàn)程來(lái)專(zhuān)門(mén)銷(xiāo)毀緩存的statement,則還需要設(shè)置maxStatements與maxStatementsPerConnection。

再貼一個(gè)官方的說(shuō)明：

Configuring Statement Pooling

c3p0 implements transparent PreparedStatement pooling as defined by the JDBC spec. Under some circumstances, statement pooling can dramatically improve application performance. Under other circumstances, the overhead of statement pooling can slightly harm performance. Whether and how much statement pooling will help depends on how much parsing, planning, and optimizing of queries your databases does when the statements are prepared. Databases (and JDBC drivers) vary widely in this respect. It's a good idea to benchmark your application with and without statement pooling to see if and how much it helps.

You configure statement pooling in c3p0 via the following configuration parameters:

maxStatements

maxStatementsPerConnection

statementCacheNumDeferredCloseThreads

maxStatementsis JDBC's standard parameter for controlling statement pooling.maxStatementsdefines the total numberPreparedStatementsa DataSource will cache. The pool will destroy the least-recently-used PreparedStatement when it hits this limit. This sounds simple, but it's actually a strange approach, because cached statements conceptually belong to individual Connections; they are not global resources. To figure out a size formaxStatementsthat does not "churn" cached statements, you need to consider the number offrequently usedPreparedStatements in your application,and multiply that by the number of Connections you expect in the pool (maxPoolSizein a busy application).

maxStatementsPerConnectionis a non-standard configuration parameter that makes a bit more sense conceptually. It defines how many statements each pooled Connection is allowed to own. You can set this to a bit more than the number ofPreparedStatementsyour applicationfrequentlyuses, to avoid churning.

If either of these parameters are greater than zero, statement pooling will be enabled. If both parameters are greater than zero, both limits will be enforced. If only one is greater than zero, statement pooling will be enabled, but only one limit will be enforced.

大概意思就是這兩個(gè)，有一個(gè)值如果大于0，c3p0的statement pool就會(huì)發(fā)生作用。

以上所有的配置都是基于c3p0的最新版本。PS一下，還是2015年的JAR。

通過(guò)引入最新的C3P0包，另外增加了兩段配置，線(xiàn)上觀察兩天，問(wèn)題解決。

最后打個(gè)小廣告，JAVA世界最快的JDBC連接池，非HikariCP莫屬。已經(jīng)甩c3p0好幾個(gè)街角，有圖有真像。

     摘要: 在word的處理之中，文字，各種類(lèi)型的圖片，最復(fù)雜的公式，之前編寫(xiě)的API基本都覆蓋了。不過(guò)，昨天在做一個(gè)文檔測(cè)試時(shí)，發(fā)現(xiàn)表格沒(méi)有能很好的處理。  閱讀全文      摘要: 作為日常支付業(yè)務(wù)，微信的接入逐漸進(jìn)入了大家的視野。今天以PC端接入微信支付的基本流程來(lái)說(shuō)明。  閱讀全文      摘要: 在WORD里面編輯公式，目前是有兩種方法。  閱讀全文      摘要: 當(dāng)我們淡到RPC服務(wù)框架，放眼世界范圍，我目前知道的主流有thrift,fingle,grpc等。當(dāng)然大型互聯(lián)網(wǎng)公司都會(huì)有自己的RPC服務(wù)與治理框架。經(jīng)過(guò)一段時(shí)間的調(diào)研，本著簡(jiǎn)單，高效的原則,最終選擇thrift.具體原因，等接下來(lái)寫(xiě)到服務(wù)篇的時(shí)候再細(xì)說(shuō)。  閱讀全文      摘要: 目前公司業(yè)務(wù)上，有課程直播這一塊。為了增加用戶(hù)的互動(dòng)，需要增加聊天室功能。聊天室，對(duì)實(shí)時(shí)性有較嚴(yán)格的要求，所以考慮使用socketio來(lái)做。目前在服務(wù)端，有基于netty實(shí)現(xiàn)的websocketio的框架。https://github.com/mrniko/netty-socketio，這個(gè)作者還是挺厲害的（redisson的作者）。  閱讀全文      摘要: 對(duì)于后端的參數(shù)校驗(yàn)，我們一直在強(qiáng)調(diào)的驗(yàn)證規(guī)則，提示信息的重用。這不，springmvc通過(guò)集成Valid最大程序減少了我們的工作量。其實(shí)后端的參數(shù)過(guò)濾，是分幾種請(qǐng)求來(lái)源的。每種的處理都不太一樣，但是我們?nèi)绻苤赜抿?yàn)證規(guī)則，提示信息，那就很強(qiáng)大了。  閱讀全文

      已經(jīng)一個(gè)多月沒(méi)有寫(xiě)東西了，不過(guò)最近確實(shí)很忙。前兩天在線(xiàn)上碰到一個(gè)C3P0的鏈接死鎖的異常，話(huà)說(shuō)這個(gè)上古神物 ,我已經(jīng)是很久不碰了。先貼異常

"apparent deadlocks"：名詞解釋是說(shuō)c3p0拿到鏈接之后，最終使用之后沒(méi)有返回到pool,導(dǎo)致死鏈檢測(cè)失敗。經(jīng)過(guò)在stack Overflow檢索,https://stackoverflow.com/questions/3730844/c3p0-apparent-deadlock-when-the-threads-are-all-empty.發(fā)現(xiàn)增加一個(gè)statementCacheNumDeferredCloseThreads該參數(shù)的定義，就可以避免這個(gè)問(wèn)題。

經(jīng)過(guò)查看官方文檔：http://www.mchange.com/projects/c3p0/#statementCacheNumDeferredCloseThreads

解釋?zhuān)喝绻言撝翟O(shè)為超過(guò)1，statement的緩存就會(huì)自動(dòng)跟蹤當(dāng)前可用的connections,如果沒(méi)有再用，就會(huì)自動(dòng)銷(xiāo)毀掉。如果需要另外的線(xiàn)程來(lái)專(zhuān)門(mén)銷(xiāo)毀緩存的statement,則還需要設(shè)置maxStatements與maxStatementsPerConnection。

再貼一個(gè)官方的說(shuō)明：

Configuring Statement Pooling

c3p0 implements transparent PreparedStatement pooling as defined by the JDBC spec. Under some circumstances, statement pooling can dramatically improve application performance. Under other circumstances, the overhead of statement pooling can slightly harm performance. Whether and how much statement pooling will help depends on how much parsing, planning, and optimizing of queries your databases does when the statements are prepared. Databases (and JDBC drivers) vary widely in this respect. It's a good idea to benchmark your application with and without statement pooling to see if and how much it helps.

You configure statement pooling in c3p0 via the following configuration parameters:

maxStatements

maxStatementsPerConnection

statementCacheNumDeferredCloseThreads

maxStatementsis JDBC's standard parameter for controlling statement pooling.maxStatementsdefines the total numberPreparedStatementsa DataSource will cache. The pool will destroy the least-recently-used PreparedStatement when it hits this limit. This sounds simple, but it's actually a strange approach, because cached statements conceptually belong to individual Connections; they are not global resources. To figure out a size formaxStatementsthat does not "churn" cached statements, you need to consider the number offrequently usedPreparedStatements in your application,and multiply that by the number of Connections you expect in the pool (maxPoolSizein a busy application).

maxStatementsPerConnectionis a non-standard configuration parameter that makes a bit more sense conceptually. It defines how many statements each pooled Connection is allowed to own. You can set this to a bit more than the number ofPreparedStatementsyour applicationfrequentlyuses, to avoid churning.

If either of these parameters are greater than zero, statement pooling will be enabled. If both parameters are greater than zero, both limits will be enforced. If only one is greater than zero, statement pooling will be enabled, but only one limit will be enforced.

大概意思就是這兩個(gè)，有一個(gè)值如果大于0，c3p0的statement pool就會(huì)發(fā)生作用。

以上所有的配置都是基于c3p0的最新版本。PS一下，還是2015年的JAR。

通過(guò)引入最新的C3P0包，另外增加了兩段配置，線(xiàn)上觀察兩天，問(wèn)題解決。

最后打個(gè)小廣告，JAVA世界最快的JDBC連接池，非HikariCP莫屬。已經(jīng)甩c3p0好幾個(gè)街角，有圖有真像。

     摘要: 在word的處理之中，文字，各種類(lèi)型的圖片，最復(fù)雜的公式，之前編寫(xiě)的API基本都覆蓋了。不過(guò)，昨天在做一個(gè)文檔測(cè)試時(shí)，發(fā)現(xiàn)表格沒(méi)有能很好的處理。  閱讀全文

     摘要: HDFS和MapReduce是Hadoop的兩大核心，除此之外Hbase、Hive這兩個(gè)核心工具也隨著Hadoop發(fā)展變得越來(lái)越重要。今天我們只初步的看看HDFS.  閱讀全文

     摘要: 使用thrift已經(jīng)有段時(shí)間了，目前基本是clien+server的方式，負(fù)載是通過(guò)nginx來(lái)處理。這種處理方式有兩個(gè)比較大的弊端：  閱讀全文

    www.taggerin.com，主要處理日常文檔的在線(xiàn)編輯，以及與Markdown,PDF,html等格式的雙向轉(zhuǎn)換.聽(tīng)說(shuō)內(nèi)測(cè)版本已經(jīng)發(fā)布。真正的文檔在線(xiàn)編輯與預(yù)覽。?

     摘要: 一般的業(yè)務(wù)開(kāi)發(fā)，不會(huì)涉及到多種數(shù)據(jù)庫(kù)類(lèi)型的操作。因?yàn)?，無(wú)論是對(duì)于開(kāi)發(fā)，還是運(yùn)維，成本都是非常高的。如果是ORACLE數(shù)據(jù)庫(kù)到MYSQL的數(shù)據(jù)備份，目前我所了解的開(kāi)源解決方案有2種：  閱讀全文

     摘要: 作為日常支付業(yè)務(wù)，微信的接入逐漸進(jìn)入了大家的視野。今天以PC端接入微信支付的基本流程來(lái)說(shuō)明。  閱讀全文

     摘要: 在WORD里面編輯公式，目前是有兩種方法。  閱讀全文

     摘要: 最近在弄項(xiàng)目的壓測(cè)，首先想到把應(yīng)用服務(wù)器TOMCAT的相關(guān)配置升級(jí)，網(wǎng)上看了很多關(guān)于TOMCAT升級(jí)的案例，于是結(jié)合自己的實(shí)際情況，做了筆記。  閱讀全文

     摘要: 當(dāng)我們淡到RPC服務(wù)框架，放眼世界范圍，我目前知道的主流有thrift,fingle,grpc等。當(dāng)然大型互聯(lián)網(wǎng)公司都會(huì)有自己的RPC服務(wù)與治理框架。經(jīng)過(guò)一段時(shí)間的調(diào)研，本著簡(jiǎn)單，高效的原則,最終選擇thrift.具體原因，等接下來(lái)寫(xiě)到服務(wù)篇的時(shí)候再細(xì)說(shuō)。  閱讀全文