2017-12-21

MAC上安裝node.js + jshint

在MAC上的sublime text 3需要裝sublimeLinter + jshint,因此需要裝nvm + node.js + jshint

1.安裝nvm (Node Version Manager)

先修改~/.bash_profile,加入下面二行(load nvm.sh才能找到nvm):
export NVM_DIR="$HOME/.nvm"
. "/usr/local/opt/nvm/nvm.sh"

建立.nvm目錄 (nvm會將node.js安裝在此)
mkdir ~/.nvm

brew install nvm

重載shell環境變數
source ~/.bash_profile

2.安裝node.js
nvm ls-remote #列出node所有版本,找LTS stable版
nvm install v8.9.3
nvm ls #列出預設使用版本
nvm use v8.9.3 #若nvm末正確設定預設版本,使用nvm use {version}

3.安裝jshint
修改~/.bash_profile,加入下面一行:
export PATH="$PATH:~/.nvm/versions/node/v8.9.3/bin"

重載shell環境變數
source ~/.bash_profile

npm install -g jshint



2017-11-08

Java中處理HTML Entity (HTML Special Char)

幫同事處理資料庫中有HTML Entity的字元,將其轉為對應的unicode字元,
(猜測是舊系統的網頁編碼為UTF-8,但送出表單時的charset為BIG5,因無法找到對應字元所造成的)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
String name = "王蘐老蘑先蘒生蘓王蘔老蘕先蘖生蘗王蘘老蘐先蘙生蘚";
Pattern regex = Pattern.compile("&#(\\d{5});");
StringBuffer sb = new StringBuffer();
long time1 = System.currentTimeMillis();
//使用HTMLDocument及HTMLEditorKit
HTMLDocument doc = new HTMLDocument();
new HTMLEditorKit().read(new StringReader(name), doc, 0);
System.out.println(doc.getText(0, doc.getLength()));
long time2 = System.currentTimeMillis();
System.out.println(time2 - time1); //60毫秒
//使用正則表示式
Matcher match = regex.matcher(name);
while(match.find()){
match.appendReplacement(sb, new String(Character.toChars(Integer.parseInt(match.group(1)))));
}
match.appendTail(sb);
System.out.println(sb);
long time3 = System.currentTimeMillis();
System.out.println(time3 - time2);//1毫秒

2017-10-24

MAC上更新 RUBY 、安裝JDK8+JDK9並指定JRE 版本

MAC內的ruby目前還停留在2.0.0版,以下是使用homebrew的方法來更新 ruby & gem:

brew install ruby

vi ~/.profile
加入
export PATH=/usr/local/bin:$PATH

source ~/.bash_profile
brew link --overwrite ruby
gem install bundler

JAVA也是差不多,不過由於目前正是要過渡到JDK 9,系統又想保留JDK 8,且預設JRE要指定為8,可以這麼做:

brew cask reinstall java8 //jdk8
brew cask install java //jdk9

#查看一下目前裝了哪些JVM版本
/usr/libexec/java_home -V

#指定JRE 1.8
vi ~/.profile
加入
export JAVA_HOME=`/usr/libexec/java_home -v 1.8`

source ~/.bash_profile

#檢查一下
java -version

但如果是.app的程式,可能就比較麻煩點了,如NetBeans.app,需要去修改netbeans.conf,直接指定jdk 8的路徑:
netbeans_jdkhome="/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/"
若有修改~/.profile加入JAVA_HOME的話,可直接改為
netbeans_jdkhome="${JAVA_HOME}"

如果使用NetBeans的話,千萬不要傻傻移除Java 8啊,畢竟NetBeans 8.1以後的版本還是基於JDK 8使用的,安裝JDK 9之後再從NetBeans新增Platform選項就可以了。

ref:
https://docs.oracle.com/javase/8/docs/technotes/guides/install/mac_jdk.html#A1096903
https://www.java.com/en/download/help/mac_uninstall_java.xml
http://wiki.netbeans.org/JDK9Support#jdk9_runtime
https://stackoverflow.com/questions/21964709/how-to-set-or-change-the-default-java-jdk-version-on-os-x
https://stackoverflow.com/questions/38194032/how-to-update-ruby-version-2-0-0-to-the-latest-version-in-mac-osx-yosemite/42286604#42286604

2017-10-23

讓TOMCAT 8.5, TOMCAT 9 支援 SSL over HTTP/2

TOMCAT 8.5以上可支援HTTP/2,而HTTP/2+ALPN為目前瀏覽器支援的主流,
需要openssl的支援,而舊版本openssl只支援NPN,
若要支援ALPN,那麼openssl版本需 >= 1.0.2,
若未滿足上述條件,瀏覽器會自動降級為使用HTTP/1.1協定,
或瀏覽器本來就不支援HTTP/2,伺服器會改使用HTTP/1.1協定。

TOMCAT 8.5要支援HTTP/2需要使用APR(Tomcat Native library)
TOMCAT9.X要支援HTTP/2,可以使用APR,或使用Java >=9版本(建議)。

(UPDATE: TOMCAT 8.5 +JDK8使用APR有不太穩定的現象,建議升級為TOMCAT 9)
(UPDATE: TOMCAT 9 +JDK8使用APR運行了幾天後突然噴掉,查了 /tmp/hs_err_pid22617.log
,stack trace顯示錯誤為:
Stack: [0x00007f2eb16f8000,0x00007f2eb17f9000], sp=0x00007f2eb17f74a0, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libc.so.6+0x7c418] _int_free+0x2f8

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 7361 org.apache.tomcat.jni.Socket.destroy(J)V (0 bytes) @ 0x00007f2ec140ba81 [0x00007f2ec140ba40+0x41]

看起來是底層系統做記憶體回收時噴掉,網路上一查似乎很多人都有不定時噴掉的情形,
看來APR似乎是不太可靠…或者是libc.so要去更新才行,因此為了暫時解決此問題,
在tomcat.service加了crash後自動restart的機制:
[Service]
...
Restart=on-failure
RestartSec=5
TimeoutStartSec=60
TimeoutStopSec=60

1.先確定OPENSSL >= 1.0.2,若不是請先升級
openssl version
==> OpenSSL 1.0.2k-fips  26 Jan 2017

2.安裝gcc、OpenSSL libraries及APR library,等下編譯 tc-native需用到
apt-get install gcc libapr1.0-dev libssl-dev

yum install apr-devel openssl-devel
/usr/bin/apr-1-config --version
==> 1.4.8


注意最後訊息所顯示的apr安裝位置,譬如CentOS用yum是安裝在/usr/bin/apr-1-config

3.下載Apache Tomcat Native Library,解壓縮,./configure,make,make install
(可直接使用tomcat/bin/tomcat-native.tar.gz)
(新版下載位置:http://tomcat.apache.org/download-native.cgi)
cd path/to/tomcat/bin/
tar zxvf ttomcat-native.tar.gz
cd tomcat-native-1.2.16-src/native

自動安裝到tomcat/lib:
./configure --prefix=$CATALINA_HOME
make
make install

或不make install,手動搬移library(建議):
./configure && make
mkdir -p path/to/tomcat/lib_tc
cp .libs/* path/to/tomcat/lib_tc
chown -R tomcat.tomcat path/to/tomcat/lib_tc
cd path/to/tomcat/lib_tc
ln -f -s libtcnative-1.so libtcnative-1.so.0.2.16
ln -f -s libtcnative-1.so.0 libtcnative-1.so.0.2.16

4.make install後,會在tomcat/lib多了
libtcnative-1.a
libtcnative-1.la
libtcnative-1.lai
libtcnative-1.so (link)
libtcnative-1.so.0 (link)
libtcnative-1.so.0.2.16
這些函式庫檔案跟目錄,記得檢查並chmod及chown一下。

5.之後我們需要把這些lib路徑加到環境變數LD_LIBRARY_PATH,
可以用編輯tomcat/bin/setenv.sh的方法(無此檔案請自行新增),加入:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CATALINA_HOME/lib_tc
export LD_LIBRARY_PATH

記得chmod +x setenv.sh

6.修改tomcat/conf/server.xml

檢查一下AprLifecycleListener是否有加入此行啟動監聽:
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />

修改Connector,注意憑證需轉換為PEM格式
<Connector port="8443" protocol="org.apache.coyote.http11.Http11AprProtocol"
            maxThreads="150" SSLEnabled="true" >
    <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
    <SSLHostConfig>
      <Certificate certificateKeyFile="conf/private_key.pkcs8"
                        certificateChainFile="conf/ca_chain.cer"
                        certificateFile="conf/ca.cer"/>
    </SSLHostConfig>
</Connector>

若無申請正式憑證,可先自行生成自簽憑證使用:
openssl genrsa -out private_key.pkcs8 2048
openssl rsa -in private_key.pkcs8 -out private_key.pkcs8
openssl req -new -x509 -key private_key.pkcs8 -out ca.crt -days 3650


7.重啟TOMCAT,
檢查catalina logs是否成功載入APR
INFO: Loaded APR based Apache Tomcat Native library [1.x.y]
["https-openssl-apr-8443"]
如有以上訊息代表成功。


上述做法我在tomcat 9是成功的,但tomcat 8.5.4似乎有掉資料的現象,所以建議升級至TOMCAT 9。

TOMCAT9的HTTP/2若不使用APR,需使用JDK >= 9,這樣Connector就直接使用NIO2就好而不需要用到APR。

ref:
http://tomcat.apache.org/whichversion.html
https://tomcat.apache.org/tomcat-9.0-doc/config/http2.html
https://linux.cn/article-7934-1.html
https://dzone.com/articles/configure-tomcat-9-forhttp2
https://stackoverflow.com/questions/30855281/tomcat-support-for-http-2-0/37889873#37889873
https://readlearncode.com/configure-tomcat-9-for-http2/
http://tomcat.apache.org/native-doc/
https://tomcat.apache.org/tomcat-8.5-doc/apr.html
http://jmchung.github.io/blog/2013/09/06/centos-installing-apache-portable-runtime-apr-for-tomcat/

2017-06-04

tomcat server的CPU突然飆高,連線遺失

今天發現在VM上面RUN的TOMCAT會隨機掉連線(400, 500都出現了),
密集REQUEST的時候就會發生問題,而且CPU TIME都超過100%了!
後來發現是 server.xml 中 connector 的問題,預設是用 org.apache.coyote.http11.Http11NioProtocol (NIO),
後來改為 org.apache.coyote.http11.Http11Nio2Protocol (NIO2),
然後就,好了,也不知道是不是舊 NIO 跟 VM 犯沖,改成效能比較好的NIO2似乎就沒事兒了。

2017-04-17

Java中HttpServer (HttpsServer) ,解決response會延遲或卡住的問題

第一次使用 com.sun.net.httpserver.HttpServer 跟 com.sun.net.httpserver.HttpsServer 做為http server時,
發現連續的request會使得response卡住:

1
2
3
OutputStream os = httpExchange.getResponseBody();
os.write(response.getBytes()); //卡住造成阻塞,過很久才會回應,
os.close();

解決之道,就是確保connection能close, 並使用multi-thread:
1
2
3
4
5
6
7
8
final Executor multi = Executors.newFixedThreadPool(10);
final HttpServer server = HttpServer.create(new InetSocketAddress(s_HTTP_PORT), 5);
//... do your REST bindings here
server.setExecutor(multi);
server.start();
//bindings中送出Connection = close 的 header
httpExchange.getResponseHeaders().add("Connection", "close");

ref:
http://stackoverflow.com/questions/15235075/1s-delay-in-httpserver-since-java-7

2017-03-31

TOMCAT的安全性header設定

TOMCAT有內建一些關於CORS及SECURITY的HEADER, 可以的話建議打開,以利用瀏覽器所提供的安全性功能,以下是個人常用的預設設定:

修改 tomcat-home/conf/web.xml (對所有apps生效):
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
<filter>
<filter-name>HeaderSecurityFilter</filter-name>
<filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>
<init-param>
<param-name>hstsEnabled</param-name><param-value>true</param-value></init-param>
<init-param>
<param-name>hstsMaxAgeSeconds</param-name><param-value>15768000</param-value></init-param>
<init-param>
<param-name>hstsIncludeSubDomains</param-name><param-value>true</param-value></init-param>
<init-param>
<param-name>antiClickJackingEnabled</param-name><param-value>true</param-value></init-param>
<init-param>
<param-name>antiClickJackingOption</param-name><param-value>SAMEORIGIN</param-value></init-param>
<init-param>
<param-name>antiClickJackingUri</param-name><param-value></param-value></init-param>
<init-param>
<param-name>blockContentTypeSniffingEnabled</param-name><param-value>true</param-value></init-param>
<init-param>
<param-name>xssProtectionEnabled</param-name><param-value>true</param-value></init-param>
</filter>
<filter>
<filter-name>CorsFilter</filter-name>
<filter-class>org.apache.catalina.filters.CorsFilter</filter-class>
<init-param>
<param-name>cors.allowed.origins</param-name><param-value>https://your.domain.com</param-value></init-param>
<!--
<init-param>
<param-name>cors.allowed.methods</param-name><param-value>GET,POST,HEAD,OPTIONS,PUT</param-value></init-param>
<init-param>
<param-name>cors.allowed.headers</param-name><param-value>Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers</param-value></init-param>
<init-param>
<param-name>cors.exposed.headers</param-name><param-value>Access-Control-Allow-Origin,Access-Control-Allow-Credentials</param-value></init-param>
<init-param>
<param-name>cors.support.credentials</param-name><param-value>true</param-value></init-param>
<init-param>
<param-name>cors.preflight.maxage</param-name><param-value>10</param-value></init-param>
-->
</filter>
<filter-mapping>
<filter-name>HeaderSecurityFilter</filter-name>
<url-pattern>/*</url-pattern>
<!--<servlet-name>*</servlet-name>-->
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>ERROR</dispatcher>
<dispatcher>ASYNC</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>CorsFilter</filter-name>
<url-pattern>/*</url-pattern>
<!--<servlet-name>*</servlet-name>-->
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>ERROR</dispatcher>
<dispatcher>ASYNC</dispatcher>
</filter-mapping>

ref:
https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html#CORS_Filter
https://tomcat.apache.org/tomcat-8.5-doc/config/filter.html#HTTP_Header_Security_Filter
https://wiki.mozilla.org/Security/Guidelines/Web_Security#Content_Security_Policy
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
HTTP Headers 的資安議題 (1)
HTTP Headers 的資安議題 (2)
HTTP Headers 的資安議題 (3)

TOMCAT自訂共用library目錄

常常TOMCAT裡的apps都會共用一些library,而通常的做法是直接丟到${catalina.base}/lib裡面去,不過有時在搬移網站時,常常就會忘了哪些是自已新增的lib.jar了 XDD
因此可以另外建一個目錄來放自已的共用jar library。譬如先建一個common-lib專放自已共用的jar:

修改/conf/catalina.properties的shared.loader or common.loader屬性,新增路徑:
1
2
3
shared.loader="${catalina.base}/common-lib","${catalina.base}/common-lib/*.jar","${catalina.home}/common-lib","${catalina.home}/common-lib/*.jar"
...或
common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar"

2017-03-28

找出由大到小第N個項目

找出由大到小第N個項目,蠻有創意的SQL寫法

1
2
3
4
5
6
7
SELECT * FROM Employee Emp1
WHERE (N-1) =
(
SELECT COUNT(DISTINCT(Emp2.Salary))
FROM Employee Emp2
WHERE Emp2.Salary > Emp1.Salary
)

2017-03-27

讓TOMCAT能辨識URLEncode的中文檔名

TOMCAT預設是以ISO-8859-1來解讀經過URL Encode的URL的,因此要改為告訴TOMCAT所有URL經過URL Decode後要以UTF-8來解讀。

修改 bin/catalina.sh:
1
2
JAVA_OPTS="-Djavax.servlet.request.encoding=UTF-8 -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Duser.timezone=GMT+08 ${JAVA_OPTS}"
(-Dsun.jnu.encoding=UTF-8可有可無)

或修改 conf/web.xml (有修改catalina.sh就不用改web.xml)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
<!--A filter that sets character encoding that is used to decode-->
<!--parameters in a POST request-->
<filter>
<filter-name>setCharacterEncodingFilter</filter-name>
<filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class>
<init-param>
<param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param>
</filter>
<!--The mapping for the Set Character Encoding Filter-->
<filter-mapping>
<filter-name>setCharacterEncodingFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

修改 conf/server.xml:
1
2
3
4
5
<Connector port="80" protocol="HTTP/1.1"
...
URIEncoding="utf-8" useBodyEncodingForURI="true"
...
>

URIEncoding:對於URI,決定要以何種編碼來處理。
useBodyEncodingForURI:對於URI,決定是否要以request HEADER中的Content-Type中的編碼類型訊息、或request.setCharacterEncoding()方法中指定的編碼來處理,若為false則一律以URIEncoding所指定的編碼來處理。

而編寫網頁時,最好能自行將下載鏈結等先做URL Encode,而不是讓瀏覽器去幫你做,因為不是每個瀏覽器都會自動以URL Encode(UTF-8)來傳送的。 如果是有在寫jsp,那麼在web.xml加上:
1
2
3
4
5
6
<jsp-config>
<jsp-property-group>
<url-pattern>*.jsp</url-pattern>
<pageencoding>UTF-8</pageencoding>
</jsp-property-group>
</jsp-config>

2017-03-23

Netbeans 一直出現 duplicate class 的錯誤

明明你很確定同一個package的class名稱並沒有重複,
但Netbeans就是會告訴你有duplicate class name,並出現討厭的驚嘆號,
這時候不要懷疑,你的Netbeans壞掉了!

不過解決方法很簡單,不用重裝不用升級,只要把Netbeans的cache清除掉就可以了!

WINDOWS:
C:\Users\\AppData\Local\NetBeans\Cache\

LINUX:
~/.cache/netbeans/${netbeans_version}/index/

MAC:
~/Library/Caches/NetBeans/${netbeans_version}/

或著在Netbeans的選單「Help » About」裡面就可以找到Cache directory的路徑了。

2017-02-26

對遠端的tomcat除錯,且又有二個以上專案時

如果對遠端的tomcat用netbeans除錯,且伺服器又有二個以上的專案,

必須在netbeans的 Window/Debugging/Sources 視窗去調整 source 的順序,

因為預設是以在遠端找到的第一個專案來除錯,反正要除錯的專案就在source往前調整就是了,

不然就會陷入無限的鬼打牆,怎麼斷點都會跟你說無法submit到遠端伺服器。

2017-02-21

MySQL(MariaDB) 設定檢查、調整工具


可根據你提供的訊息,產生MySQL(MariaDB)設定檔:

https://tools.percona.com

(裡面還有query語句檢查工具)

MySQL的perl檢查工具,可找出目前有那些設定或安全性有問題:

https://github.com/major/MySQLTuner-perl