So we need to convert the result of e.printStackTrace() to string:

private static String getStackTrace(Exception e) {
StringWriter stringWriter= new StringWriter();
PrintWriter printWriter = new PrintWriter(stringWriter);
e.printStackTrace(printWriter);
return stringWriter.toString();
}

server {
    listen        80;
    server_name   nginx.org  www.nginx.org;
    root          /data/www;

    location / {
        index     index.html  index.php;
    }

    location ~* \.(gif|jpg|png)$ {
        expires   30d;
    }

    location ~ \.php$ {
        fastcgi_pass   localhost:9000;
        fastcgi_param  SCRIPT_FILENAME
                       $document_root$fastcgi_script_name;
        include        fastcgi_params;
    }
}

nginx first searches for the most specific location given by literal strings regardless of the listed order. In the configuration above the only literal location is “/” and since it matches any request it will be used as a last resort. Then nginx checks locations given by regular expression in the order listed in the configuration file. The first matching expression stops the search and nginx will use this location. If no regular expression matches a request, then nginx uses the most specific literal location found earlier.

File excerpt: nginx.conf location directives

location / { }
location /images/ { }
location /blog/ { }
location /planet/ { }
location /planet/blog/ { }

location ~ IndexPage\.php$ { }
location ~ ^/BlogPlanet(/|/index\.php)$ { }

location ~* \.(pl|cgi|perl|prl)$ { }
location ~* \.(md|mdwn|txt|mkdn)$ { }

location ^~ /images/IndexPage/ { }
location ^~ /blog/BlogPlanet/ { }

location = / { }

The first five examples are “literal string” matches, and match the beginning part of the request following the host portion. In a hypothetical request for http://ducklington.org/, assuming that there is a server_name for ducklington.org, the “location /” directive will catch this request. Nginx will always fulfill a request with most specific match. A request for http://ducklington.org/planet/blog/ and http://ducklington.org/planet/blog/about/ will be fulfilled by the “location /planet/blog/” even though “location /planet/” also fills this request.

When a location directive is followed by a tilde (e.g. ~) as in the fourth group of examples, nginx performs a regular expression match. These matches are always case sensitive, so in the first example requests ending in IndexPage.php would match, but indexpage.php would not. In the second the regular expression ^/BlogPlanet(/|index\.php)$ will match requests for /BlogPlanet/ and /BlogPlanet/index.php, but not /BlogPlanet, /blogplanet/, or /blogplanet/index.php. Nginx uses Perl Compatible Regular Expressions (PCRE).

Using a tilde-asterisk (e.g. ~*) as an argument to a location directive, as in the third group of examples, removes case sensitivity from the matches. These examples all specify how nginx should process requests that end in a particular file extension. In the first example, any file ending in: .pl, .PL, .cgi, .CGI, .perl, .Perl, .prl, and .PrL (among others) will match the request.

In the next group of examples, the caret-tilde argument (e.g. ^~) to location functions like the literal string matches of the first group. However, when used, they force nginx to stop searching for more specific matches. So in these examples, the location directives for “^~ /images/IndexPage/” and “^~ /blog/BlogPlanet/” would be used even though the request matches another location directive. See below for more information about the order and priority of location directive processing.

Finally, using the equal sign (e.g. =) as an argument to location forces an exact match with the path requested and then stops searching for more specific matches. For instance, the final example will only match http://ducklington.org/ but not http://ducklington.org/index.html. Using exact matches can speed up request times slightly especially when some requests are particularly popular.

Directives are processed in the following manner:

• Exact string matches are processed first. If a match is found, nginx stops searching and fulfills the request.
• Remaining literal string directives are processed next. If the “^~” argument is used, then ngnix stops here and fulfills the request. Otherwise, nginx continues to process location directives.
• All location directives specified by regular expressions (with the ~ and ~* arguments) are processed. If a regular expression matches the request, nginx stops here and fulfills the request.
• When there are no regular expressions, or no regular expressions match, the most specific literal string match is used.

It is incumbent upon the administrator to ensure that possible location directives will match for every resource nginx is to provide for a given domain within the server block. Additionally, while nginx’s configuration parser is capable of reading nested location blocks, using location directives in this manner is not a supported behavior.

location / {
    root   html;
    index  index.html index.htm;
}

location / {
    root   /srv/www/ducklington.org/public_html;
    index  index.html index.htm;
}

location ~ \.pl$ {
    gzip off;
    include /etc/nginx/fastcgi_params;
    fastcgi_pass  127.0.0.1:8999;
    fastcgi_index index.pl;
    fastcgi_param  SCRIPT_FILENAME  /srv/www/ducklington.org/public_html$fastcgi_script_name;
}

Reference:

nginx.conf.zip

http://nginx.org/en/docs/http/request_processing.html

http://library.linode.com/web-servers/nginx/configuration/basic#location_configuration

http://articles.slicehost.com/2009/3/5/ubuntu-intrepid-nginx-configuration

http://blog.rackcorp.com/?p=31

It is due to a MyEclipse (I am using My Eclipse 5.5.0 GA) defect.

http://www.myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&t=21403&start=0&postdays=0&postorder=asc&highlight=

Workaround:  add them under the jar files under lib folder in the boot configuration of Resin in MyEclipse.

Also there is another MyEclipse ‘defect’. By default, the deploy folder will be used to deploy the Eclipse Project.  But we need to update the resin.conf file to set up the correct value for ‘<web-app-deploy path=”deploy”/>’ .

We came across java.lang.ArrayIndexOutOfBoundsException when using Resin 4.0.8.   The root cause is a defect from Resin 4.0.8.  (http://bugs.caucho.com/view.php?id=4104) . The solution is upgrade the Resin to version 4.0.9

But the problem is the most popular way to store RSA key is keeping them as DER format.

You can get some detailed info below:

http://www.cryptosys.net/pki/rsakeyformats.html

Also if you want the java code to generate the RSA key in DER format and encrypt data using such keys. Please contact me. (ukoom AT gmail.com)

commit -m “commit message.” files
RA layer request failed
svn: Commit failed (details follow):
svn: PROPFIND request failed on ‘/repo/path/!svn/vcc/default’
svn: PROPFIND of ‘/repo/path/!svn/vcc/default’: Could not read status line: connection was closed by server. (http://example.com)

How to fix?

Looking at my SVN configurations I could only find the JavaHL option, no SVNKit available.

1. Install the JDK and Tomcat and set the environment variable.
2. Configure JK
Download JK from http://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.14/isapi_redirect-1.2.14.exe
Setup the file. (It’s better that there isn’t blank space in the directory which you choose to install.)
After installing it, you could find the file “workers.properties.minimal” in \Apache Software Foundation\Jakarta Isapi Redirector, and change its name to “workers.properties”.
Open the Registry Editor; Open the “HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0]”
Change the value “workers.properties.minimal”of worker_file to “workers.properties”
The content of worker.properties and uriworkermap.properties is follow:
worker.properties:
worker.list=ajp13
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009
uriworkermap.properties:
# Mapping the URI /admin, /manager, /jsp-examples and /servlets-examples and
# everything under them to Tomcat
# /admin/*=ajp3
# /manager/*=ajp13
# /jsp-examples/*=ajp13
# /servlets-examples/*=ajp13

# Mapping all URI which end with a common suffix .jsp and .do to Tomcat
# /*.jsp=ajp13
# /*.do=ajp13

# Mapping all URI to Tomcat
/*=ajp13

3. Create a new website in IIS which point to your website (such as $CATALINA_HOME\ webapps\ROOT)
4. Configure the Tomcat ISAPI Filter
Rigth click your websitePropertiesISAPI FiltersAddset Filter name “jakarta” and Executable choose the path of “isapi_redirector.dll”OK
Note – If you check on its status, you may notice that the ISAPI filter hasn’t been successfully loaded at this stage, even if you have re-started IIS. This is expected behaviour and is documented in the IIS6 Operations Guide,
“In an effort to optimize resources in IIS 6.0, an ISAPI filter is not loaded until a request is made to a Web site that requires the ISAPI filter. Until this request is made, IIS Manager does not display the status of the ISAPI filter.”

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/93f23233-2a47-4104-b0b4-a7ec0d3116f3.mspx

However, once IIS has served a successful request to it you will see the status of the ISAPI filter change to ‘Loaded’.
5. Create a virtual directory for the Tomcat connector to use, create a new Web Service Extension in IIS and then enable that web service extension so that it can be used.
Rigth click your websiteNewVirtual Directoryset Alias: jakartaNextset Path: choose the path of “isapi_redirector.dll”.
6. Create and exable the tomcat Web Service Extension
Rigth click “Web Service Extension”  Add a new Web service extension Set name: Tomcat, set Required files:choose your “isapi_redirector.dll” click the “Set extension status to Allowed”OK
7. Add the “.jsp”
Rigth click your websitePropertiesHome DirectoryMappingsAddset Executable: choose your “isapi_redirector.dll”, set Extension: .jsp (Note: if there is blank space in your path, you need to make your path in Double quotes.)
8. Set index.jsp as default content page
Rigth click your websitePropertiesDocumentAdd–>index.jsp
10. Restart tomcat and IIS. You should now be ready to test your Tomcat installation by issuing a request to the sample applications. Visit http://localhost
If show the page as http://localhost:8080, you’re successful.

tomcat5.5 整合 iis6.0
环境：Windows 2003 R2 + IIS 6.0 + JDK 1.5+TOMCAT5.5
1. 安装tomcat

2. 下载jkhttp://archive.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.14/isapi_redirect-1.2.14.exe
安装的好处就是配置文件都有了。只需做少许修改：
安装目录可以随意（最好让目录不带空格），安装完成后在conf里就是它的配置文件，安装完后找到目录文件\Apache Software Foundation\Jakarta Isapi Redirector 这个可以根据你自己的改动，在conf文件里把workers.properties.minimal它改为
workers.properties，对应找到注册表里的
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0] 中的worker_file 点右键修改
同样去掉workers.properties.minimal 后的minimal。

3. 以下为两个文件的内容
uriworkermap.properties:

# Mapping the URI /admin, /manager, /jsp-examples and /servlets-examples and
# everything under them to Tomcat
# /admin/*=ajp3
# /manager/*=ajp13
# /jsp-examples/*=ajp13
# /servlets-examples/*=ajp13

# Mapping all URI which end with a common suffix .jsp and .do to Tomcat
# /*.jsp=ajp13
# /*.do=ajp13

# Mapping all URI to Tomcat
/*=ajp13

worker.properties:

worker.list=ajp13
worker.ajp13.type=ajp13
worker.ajp13.host=localhost
worker.ajp13.port=8009

4. 在iis里新建一个站点，指向网站所在的目录（比如$CATALINA_HOME\webapps\ROOT），然后在站点上点右键选“属性”，在弹出的页框里选择“ISAPI筛选器”，点“添加”，筛选器名称填jakarta,可执行文件中填入你的isapi_redirector.dll的绝对路径。“确定”后点“确定”关闭属性页。再在“默认网站”上右键，选择“新建”－>“虚拟目录”，别名填jakarta，下一步，路径选为你的isapi_redirector.dll存放的目录。

5. 在“Internet信息服务管理器”的“网站”中的“Web服务扩展”上点右键选择“添加一个新的Web服务扩展”，弹出的框中扩展名填Tomcat(其实无所谓的)，“要求的文件”选“添加”然后找到你的isapi_redirector.dll后“确定”。“设置扩展状态为允许”也打上勾，确定。

6. 如果要让iis能读取index.jsp这样的jsp默认首页，还需要在IIS6.0右键单击【默认网站】，选择【属性】，单击【主目录】选项卡中的【配置】，单击【映射】选项卡，单击【添加】，将isapi_redirector.dll的全路径写进去，扩展名要写.jsp（注意：如果你的路径包含空格，那么你需要将这个完整路径用英文的双引号括起来才能添加）。
到这里就配置完了

7. 重起tomcat 重启iis 去掉端口后看看能运行了吧

总结：
说到底，这就是两种服务的一种集成，使之外部看起来像一种服务，可以这么理解：
外部访问域名－－＞解析后到IP－－＞IIS查找相应站点－－＞发现jsp文件－－＞转至jk连接处理－－＞将相应文件解释转给Tomcat－－＞将页面返回给IIS－－＞展现给客户端。
那么哪出了问题，就查哪，一步一步来，一定能成功的，希望对大家有所帮助，另外多看官方手册，多想其中的原理，网上流传的各种文档不一定就是正确的，包括本文，只是尽量详尽的给一种引导。

Note: This procedure requires restarting the JBoss application server.

Steps

1. In the \server\default\deploy\jbossweb-tomcat50.sar directory, locate and open the server.xml file.
2. Locate the block listed under the <!– A HTTP/1.1 Connector on port 8080 –> heading.

   Note: The specific port number and other settings may vary.

   This block should look like this:

   <!-- A HTTP/1.1 Connector on port 8080 -->

   <Connector port="8080" address="${jboss.bind.address}"

   maxThreads="400" minSpareThreads="100" maxSpareThreads="75"

   enableLookups="false" redirectPort="8443" acceptCount="100"

   connectionTimeout="20000" disableUploadTimeout="true"/>

3. Add the following parameters:

   compression="on" 

   socketBuffer="1045576" />

4. Save and close the server.xml file.
5. Restart JBoss.

Generate the Java Code
1. Menu Operation
Tools , Generate Object-Oriented Model, Detail, O/R Mapping,
Enable Transformations, Extended Model Definitions, O/R Mapping,      Hibernate

To be continued.